Veeam Backup & Replication • Re: New *.vbk full backup instead of continuing backup chain ...

Hi Hypervisor

Then we activated the new backup job for the moved VM last evening, but unfortunately a new backup chain was created, because the VM was moved from the StandAlone ESXi host to the VMware cluster.

Can this be fixed somehow, so that no new backup chain is created?

This is expected behavior. Even if it's the same VM, the MoREF in the vCenter database compared to the standalone host does not match. ESXi and vCenter create their own unique MoRefID for each managed VM. And Veeam Backup & Replication tracks VM through the MoRefID. Therefore, a new backup chain is required.

We have our vCenter migration tool, but it doesn't support standalone host to vCenter migrations. There are unsupported workarounds with database edits, but we do not support them.

Best,
Fabian Kessler

Statistics: Posted by Mildur — Apr 17, 2025 8:28 am

---