troubleshooting Question

Hyper-V replication placed in a critical state after host reboot

Avatar of mattyfats
mattyfats asked on
Hyper-VMicrosoft Server OSWindows Server 2012
5 Comments2 Solutions2687 ViewsLast Modified:
I have two Hyper-V Hosts, both running Server 2012 r2.    The hosts are connected to each other via 10GB links across a campus.   Configuring the initial replication and delta replication works flawlessly.  I just implemented WSUS and have the hosts scheduled for stagged reboots, one on Mondays and the other on Tuesdays.  

The problem is, after either one of the hosts reboots, hyper-v replication health stops and is in a critical state.  I must manually  resume replication.    The virual machines "automatic stop action" is to shut down the guest OS, and the "automatic start action" is to Always Start.  

I've read from others having this issue that the machine must be in a paused state for replication to automatically resume after a host reboot.  Since the VM's are also windows machines that need patches and reboots, how can this be an acceptable answer?  

Any thoughts or suggestions is greatly appreciated.
ASKER CERTIFIED SOLUTION
Don
Network Administrator

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 2 Answers and 5 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 2 Answers and 5 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros