Veeam Backup Chain Breaks after Nutanix VM failover and back

[firebladez]

Hi

I’m new to Nutanix and we are using Prism Pro to move a VM from one 6.7 Vmware farm to another and back again. That works 100% but Veeam V11 can not see the VM once it is moved. It’s like the UUID is wrong but I have checked that and it is ok (same) Support are looking into this and are saying this is a unique case… surely this must be common? If there is no solution we will end up with the same VM added to the Veeam backup job, again and again… I have tried using TAGS and direct add to veeam… 

[PetrM]

Hello,

Could you please share a support case ID with us? It's not clear why is this case unique since Veeam tracks VMs by a Managed Object Reference ID (MoRef), which will be changed if an object is moved from one vCenter to another or re-added to inventory.

Thanks!

[firebladez]

hi, the case number is 04716845....

[PetrM]

Hello,

Thanks for providing the support case ID, let's wait for the conclusion of our support engineer after the remote session and debug logs analysis.

Thanks!