2

Should Hyper-V replication carry changes to underlying VM settings, such as increasing memory, adding a vCPU, or in this specific case, adding a NIC?

I'm running Server 2016 Datacenter edition and Hyper-V replication is via Failover Cluster Manager and a replication broker. I added a NIC to two VM's this morning, verified that replication is working, and the replica's do not have the new NIC after a half-hour and multiple successful replication cycles.

1
  • 1
    I've just confirmed same behaviour on a lab. I cannot give you a definite answer if there's a way to replicate VM settings. Looking back on the replication wizard, it mentions only Choose replication VHDs; it can be a hint that that's all replicated. – Krackout Oct 28 '20 at 11:37
2

I also verified this behaviour in lab.

The documentation about hyper-v replica says :

When you enable Hyper-V Replica for a specific virtual machine, initial replication creates an identical replica virtual machine on a secondary host server. After that happens, Hyper-V Replica change tracking creates and maintains a log file that captures changes on a virtual machine VHD.

In short, when the initial replication starts it will create a replica virtual machine with identical settings, but after that only the changes made on the virtual hard disk are replicated.

Furthermore, the only way i see to replicate the VM hardware changes like cpu, memory is to Remove Replication on the source hyper v host and delete the replica VM on the destination hyper v host, and then configure replication again.

Documentation about hyper-v replica : https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/set-up-hyper-v-replica

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.