Hyper-V Replica stopped working for one VM only

We have Hyper-V replica setup between two hosts across a VPN.  VMHOST001 is the primary where all of the machines run, and VMHOST101 is the secondary/DR site where the machines sit just in case.

Today, at 11:22, one of our four machines stopped replicating.  We received the following errors -

Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
Source:        Microsoft-Windows-Hyper-V-VMMS
Date:          2/14/2014 11:22:26 AM
Event ID:      32315
Task Category: None
Level:         Warning
Keywords:      
User:          SYSTEM
Computer:      VMHOST001
Description:
Hyper-V failed to replicate changes for virtual machine 'EXCH001' (Virtual Machine ID 23C80A90-07BE-4DB3-BC65-DA796692F60A). Hyper-V will retry replication after 1 minute(s).

Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
Source:        Microsoft-Windows-Hyper-V-VMMS
Date:          2/14/2014 11:22:26 AM
Event ID:      32022
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      VMHOST001
Description:
Hyper-V could not replicate changes for virtual machine 'EXCH001': The connection with the server was terminated abnormally (0x00002EFE). (Virtual Machine ID 23C80A90-07BE-4DB3-BC65-DA796692F60A)

All of our other machines on this host are replicating just fine.  We're doing replication using Kerberos as both hosts are on the same domain.  Machines are both Server 2012.

I noticed that the DR host has two temp hrl files - one empty, the other small.  As a test, I moved these to a temp directory and tried replication again.  No dice.  I then restarted the Hyper-V service on both servers and it started replicating and generating the temp hrl files again.  Failed again.

Any ideas?  At a loss on this one.  Nothing on Google, and makes no sense since the machines are communicating fine otherwise.
LVL 9
diperspAsked:
Who is Participating?
 
diperspConnect With a Mentor Author Commented:
And I guess sometimes, patience is a virtue.  No idea why, but after 5 hours, it just started working all by itself.  Nothing helpful in the logs.
0
 
Cliff GaliherCommented:
My initial thought is disk space on the host disk partition for that VM.
0
 
diperspAuthor Commented:
80 gigs free.  Only have ~2 gigs to write.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Cliff GaliherCommented:
Not for the target (so writing is not yet an issue) but on the source. Hyper-V replica still needs room to make the replica deltas.
0
 
diperspAuthor Commented:
68 gigs there.
0
 
Cliff GaliherCommented:
Any other partitions close to full when the VM in question is in a running state? System or log partitions could cause similar problems, although it is less common.
0
 
diperspAuthor Commented:
About 100 gigs free on the system partition of both hosts.  These are brand new boxes.  The other four VMs are still replicating just fine.
0
 
diperspAuthor Commented:
Resolved itself.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.