Feature Request: Preserve Backup Chain After Nutanix DR Cross-Cluster Migration

[petesteven]

When a VM is migrated to another Nutanix cluster via Nutanix DR (Cross-Cluster Failover/Migration. Used for migrations, updates,...), Veeam Backup for Nutanix AHV currently starts a new backup chain for the migrated VM instead of continuing the existing one. This results in unnecessary storage consumption, longer backup windows, retention missmatch,...

As documented in the Veeam Help Center:
"Veeam Backup for Nutanix AHV does not support the Migrate Across Clusters functionality. If a VM is migrated in this way, backup jobs that contain this VM will skip it. If the VM is included into a category, a backup job that protects this category will start a new backup chain for the migrated VM." https://helpcenter.veeam.com/rn/veeam_b ... notes.html
This means:
• A VM protected by a direct job will be silently skipped after a cross-cluster migration via Nutanix DR.
• A VM protected via category-based job will trigger a new full backup chain on the target cluster — losing all existing restore points and consuming additional storage. (backups are named backup_1, backup_2,..)

Both the source and target clusters are registered under the same Prism Central instance, meaning Veeam already has full visibility over the VM and its new location after migration. Since Veeam also tracks VMs by UUID — and similar behavior exists for VMware vMotion — detecting and handling this migration scenario should be technically feasible in my opinion.

Request: Veeam should detect cross-cluster migrations triggered by Nutanix DR and continue the existing backup chain on the target cluster rather than starting a new one.

Thanks!

[ronnmartin61]

@petesteven yes we are acutely aware of this current gap. We are working closely with Nutanix on a standardized Nutanix-endorsed approach to accommodate failover/failback scenarios which maintains VM identity in a manner we can easily map to existing chains. Not available today but is on our nearer-term radar.

[petesteven]

@ronnmartin61 great, nice!
But this should work automatically and not by a manual mapping. Backup Team didn't get an information if VM is moved.

[ronnmartin61]

@petesteven yes correct we anticipate it working seamlessly to track the VM w/o any manual intervention. Note that the preliminary approach Nutanix presented will require some non-trivial changes on our end but in the end would allow us to properly identify VMs as their core VMID shifts with DR operations...

[petesteven]

That sounds great! Thanks

Do you know an ETA?