Migration of VMs to new cluster with Hyper-V replica, how to preserve existing backup chain?

[gman42]

So we're currently in the middle of upgrading our Hyper-V SAN cluster with newer hardware (new servers and SAN currently installed alongside the old one). The method we're using to migrate the VMs is via Hyper-V Replica, doing a planned failover to cut the VMs over a few at a time to the new cluster.

My question is, is there any easy way in Veeam to tell my backup job to simply look to the new cluster to find the newly migrated VM, and just continue the existing backup chain? With Hyper-V Replica, the "new" VM should have the same exact ID as the old one, so in theory this should work, if there were a way to re-point the backup job to it.

So far, simply deleting the old instances of the VMs from the job and adding the new ones is working fine, but of course when doing this, Veeam needs to create a new full backup from scratch. This is not a big deal for our smaller VMs, but we have some multi-terabyte ones that will be painful to do this with when we eventually migrate them over (our backup repository isn't particularly fast).

[Dynamic]

Hi gman42, not really an answer to your question - but maybe an easier way for you: what about a VM Storage Migration of your whole VMs to the new SAN?
This can be done online, you won't have a downtime and don't have to struggle with your Replicas.

[gman42]

Thanks for the suggestion, but we actually plan on keeping the old cluster around as an additional failsafe, so doing replica and then just failing over/reversing the replication makes the most sense for what we want to accomplish (and downtime is fairly minimal for each VM when doing the planned failover anyway).

And as you mentioned, the method of migrating the VMs doesn't really address the Veeam issue.