Hyperv replication warning even though everything is working

Hi, I have 2 Windows 2016 hyper-v servers. First is master, second is only to receive replications, pretty basic. I have 9 VMs. If I look at the replication integrity, they are all working fine. Last successfull replication is always just a couple of minutes
old (replicating every 15 minutes). 

But for some, I have a warning which is; 

Time duration since the last successful application consistent checkpoint has exceeded the warning limit

Even if I reset the stats, the warning stays. You can see the problem discussed here;

How can I get rid of that warning? They are all 100% successfull replication.


Read full post . . . .

Can’t replicate VMs because replica server has less virtual cpus

Hi, I have 2 dedicated Windows 2k16 Hyper-V servers. 1 for production, the other only to receive replication through hyper-v replication (standard configuration). Just a note here, I have done multiple configurations like this.

So the replica server is brand new. I have 4 VMs, all Windows 2012 r2. So I have the same problem for all VMs. At the end of the initial replica, always around 95%, I get an error. Looking in the event viewer of the prod hyper-v, it says that at some point,
the replication server refused the connection (event 32552).

Looking at the replica server event viewer, I see that it cannot put the necessary cpu number because too big (hyper-v prod has 16 vcpus, all VMs configured with 16 vcpus, while the replica server has only 8 vcpu). Event 14420 (all in hyper-v-vmmsoperational).
Both server with Intel cpu.

My guess is to configure in each vm the cpu compatibility option but before announcing to the client that I have to stop all VMs to configure this, I wanted an opinion on my solution, or if other solution exist so that I don’t have to turn off the VMs.


Read full post . . . .

Hyper-v 2k16 cannot reboot – stays at shutting down hyper-v services

Hi, we have a brand new dedicated hyper-v server with 2k16 and created a brand new VM which is a Win2k16 server also. Very basic. When we reboot the physical hyper-v server, it stays at shutting down hyper-v services endlessly.

We found out that if we RDP in the VM and shutdown the VM, after that the hyper-v server reboots correctly so it looks like hyper-v is not capable of shutting down the VM. BTW the vm, in the shutdown config it is configured to shut down. In the event viewer
of the hyper-v server, I don’t see any error messages pointing me to a problem so I don’t know how to resolve this.

I understand that I could just shutdown the vm then reboot the hyper-v server but the IT guy on site asked me to resolve it. 

Any ideas where I could look to resolve this?


Read full post . . . .

Go Que Newsroom