HyperV Replica Critical States

[ITGURU]

Wondered if someone could shed some light on what I could possibly be doing wrong.

I have hyperv hosts and the VMs replicated to replica servers. Everything works fine, status shows as Normal etc etc

However, whenever I go to update the host or replica servers, I PAUSE the replication. I used to just reboot the servers but then found after a reboot, replica status would show as critical and thought its because I didnt pause it first, however is not the case.

Again this evening I paused the replication between primary and replica server, rebooted the replica server, and 3 of the 4 VMs when i selected resume replication show as critical status, only one of them has gone back to NORMAL.

What am i missing? Everytime i have to remove the replica, delete it and then do a full copy of the VM to the replica again, until next time i reboot!

[robyholmes]

I moved from Kerbros authentication for replication to certificate based. Solved the majority of my replication issues.

 

Moved to 2 node cluster now but replication is a good measure if you can't run a cluster.