cyberservices
asked on
Hyper-V replication problem
I have several 2012 R2 Hyper-V servers that replicate to another server and have done this for years. One server in particular I'm having trouble.
Noticed it yesterday that the replication health was critical and started to investigate. It showed that an avhdx file was on the hosted server and the hard drive in the settings had a long name in the drive settings. Normally when you shut down the server the avhdx will merge with its parent. This time it did not and I had to manually merge the file, delete the VM and recreate another one and reset up the replication. Everything went fine yesterday afternoon and replication was normal. This morning I came in and again it was back in the critical state. What can I do to fix this?
Noticed it yesterday that the replication health was critical and started to investigate. It showed that an avhdx file was on the hosted server and the hard drive in the settings had a long name in the drive settings. Normally when you shut down the server the avhdx will merge with its parent. This time it did not and I had to manually merge the file, delete the VM and recreate another one and reset up the replication. Everything went fine yesterday afternoon and replication was normal. This morning I came in and again it was back in the critical state. What can I do to fix this?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hello,
ok, let's wait until tomorrow to see if the problem does not arise again.
I remain attentive to your comments.
regards..
ok, let's wait until tomorrow to see if the problem does not arise again.
I remain attentive to your comments.
regards..
ASKER
I found on the Internet a solution that I tried. I shutdown the VM went to the folder where the VM is located and watched the merge and the avhdx file disappear. Then I restarted the VM again and noticed it did not create another avhdx. What was happening I was starting the VM to soon and not waiting until the VM to finish merging. Lesson learned.
ASKER