Securing moving VMs from one DC to other DC

[Dattland]

Hello

We have a customer that has a Nutanix cluster in each of his two data centers. The customer may need to failover the VMs to the other cluster via sync due to maintenance work in one data center.
Veeam backs up the VMs via an AHV proxy. This AHV proxy only knows the VMs that are running on the cluster.
Now to my question:
Is there an automated process where you can continue to backup the moved VM on the other side without having to start a new chain?

Maybe for the future look, will there be a way to mitigate this issue?

Thanks

[ronnmartin61]

Currently "no" as the VM assumes a new identifier when it is migrated to the other cluster which necessitates a new chain. I cannot comment on any specific roadmap enhancements which might modify behavior in this scenario.

[flow90]

This is a strong limitation, +1 for this feature please !

[asm19]

I agree that this is a limitation and should be considered.

[HYF_JE]

Stirring the pot on this feature request - is the limitation in question ("assumes a new identifier") rooted in Veeam behavior or AHV/AOS behavior?

[ronnmartin61]

AHV/AOS assigns the workload a new VM ID when it is migrated or failed over to a new cluster