Updating MORef-IDs without changing the vCenter

[Refruit]

Hello,

we are currently in the process of migrating our VMs from one vCloud Director to another. During that process the VMs are recreated/cloned as new objects but the vCenter in the back remains the same.
We want to continue the current Backup chain on the newly created VMs (which is exactly the same data as the old ones).

The question is, if the Veeam VM Migrator Utility is a possible way? Since this expects a migration or recreation of vCenter which isn't the case here.
https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13

Or is there a different supported procedure for my scenario?

[Andreas Neufert]

I think no one has tested this as a scenario.

The main point here is that the vmx file need to stay on the same path. Is this given?

[Refruit]

Hello Andreas,

no, since the VM is recreated/cloned, it resides within a new folder on a new datastore (which would also happen on a Storage vMotion right?).
So theoretically we "only" have a BIOS UUIDs misalignment of the VMs?