Hyper-V 2016 and 2019 Failover and Failback

[Manuel Monteiro]

Production environment:
Two WS 2016 Hyper-V hosts connected via iSCSI to a storage

Potencial DR environment:
One server with WS 2019 Hyper-V with local disks.

Production environment will use Veeam replica for VM replications to the new 2019 Hyper-V host.
Question: Will I find any trouble in failover to a new Windows Server with Hyper-V role and then failback to an older version (2016)?

[chris.childerhose]

Yes, you will with Failback. The target version will be lower than 2019 so it will not work. See this for info - https://helpcenter.veeam.com/docs/backu ... ml?ver=110

Note that the Target has to be of the same version or higher.

[Mildur]

Note that the failback will work. You can failback to the original vm without any issues after sorting out any issues you have with the production environment.

Failback to a new location is not possible for 2019 to 2016. That would mean to build a new replica relation ship, which needs the same or a higher hyperv version as the source host. That would be the case, if you have vms on your 2019er servers which needs to be replcated with a new job to the old 2016.

Chris posted a link with the correct answer:

You can fail back to an existing VM in original location from the target host of any version: 2008 R2-2019.