Hyper-V replication placed in a critical state after host reboot
Posted on 2014-12-11
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.