We help IT Professionals succeed at work.
Get Started

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

2,683 Views
Last Modified: 2014-12-28
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.
Comment
Watch Question
Network Administrator
CERTIFIED EXPERT
Commented:
This problem has been solved!
Unlock 2 Answers and 5 Comments.
See Answers
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE