mattyfats
asked on
Hyper-V replication placed in a critical state after host reboot
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.
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.
Last Comment
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
I'm concerned about the risks associated with pausing VM's.
http://community.spiceworks.com/topic/144695-is-it-better-to-save-vm-state-or-shutdown-the-guest-os-when-restarting-the-host
It seems that many people shutdown their guests during a host reboot to prevent the possibility of database corruption. I have Exchange 2010 servers as well as numerous SQL servers.
Any thoughts on those risks?
http://community.spiceworks.com/topic/144695-is-it-better-to-save-vm-state-or-shutdown-the-guest-os-when-restarting-the-host
It seems that many people shutdown their guests during a host reboot to prevent the possibility of database corruption. I have Exchange 2010 servers as well as numerous SQL servers.
Any thoughts on those risks?
A lot of people think pausing a VM is just like a snapshot/checkpoint. And snapshottibg *does* pose risks. But a VM pause poses very little risk. I have a variety of apps and deployments out there, always use pause, and have never seen (or heard of) a corruption that was pause related.
Microsoft Server OS
The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.
59K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
ASKER