question

Hi,
I did a test in my lab and found that only the chosen disks would create the HRL files (only the "test" vhd had HRL).

Please check if the extra HRL files belong to the excluded disks and provide the screenshot.
Also please check if the server is updated to the latest, if not, please update it and check if there's any third-party software running on the server, if yes, please uninstall them and start the VM again.

Thanks for your time!
Best Regards,
Mico Mi

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Only VHost-005c is replicated, VHost-005sc is NOT replicated, but if i copy some big size file on VHost-005sc disk, there will be growing HRL file, and it will be deleted after sync time:

All latest updates installed.
I have try to install a fresh new system - there is same problem (have place in different directories VHDX files):
VHost-001c - replicaed
VHost-001d - excluded
VHost-001e - excluded
All files with growing HRL files.

Maybe magic with Vhost*-*001c in name of VHDX? Can you try same instance with names:
VHost-001c - replicaed
VHost-001d - excluded
VHost-001e - excluded

And can you try copy some big size file on NOT replicated disks and see, does HRL file size is growing?

Hi,
Once the initial replication of a VM is completed, Hyper-V replica will start monitoring the change of each selected virtual hard disk. This is done by mirroring the changes to a HRL file.
You can try to use Resource Monitor and Process Monitor to find the problem area. Using Resource Monitor, you will be able to see which process is making writes to which file which can help you isolate any activity that is not normal. Since Hyper-V Replica tracks all writes, a large temporary file can cause a really large HRL file.
Here is the doc that may be helpful for you:
https://docs.microsoft.com/en-us/virtualization/community/team-blog/2014/20140202-hyper-v-replica-debugging-why-are-very-large-log-files-generated
Since the research that forum can do is limited, if you want to know the root cause, it is suggested to go to open a case in the following link so that a dedicated Support Professional can assist you in a more efficient manner.
https://support.microsoft.com/en-us/gp/customer-service-phone-numbers

Thanks for your time!
Best Regards,
Mico Mi

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

I see that you did not understand my question. I did not select disk (exclude it from replication), but hyper-v make mirroring the changes to a HRL file of excluded disk. On Windows Server 2012 R2 i did not seen that problem, it happens only on Windows Server 2019.
I have resolve this problem on WS2019 by connecting physical disk to VM, instead of excluded VHDX, and this resolve my issue with unnecessary HRL files for excluded disks.
But this is insane, to mirror write data for excluded VHDX in Hyper-V Replication.
More insane, that i can't change path for mirrored HRL files, for example - on RAID0 HDD, instead of double writes on SSD, that killing lifespan of SSD twicely and reduce overall speed by growing latency of SSD...