OPERATIONAL DEFECT DATABASE
...
...
BugZero found this defect 3052 days ago.
If a Virtual Machine's MoRef is changed due to migration to a new vCenter / inventory change in vCenter, you will receive the error "Object "vmname" is not found". Please see KB1299 for more details. This utility is designed to assist in re-mapping the MoRef IDs of the Virtual Machines you are backing up and/or replicating using Veeam Backup & Replication, so that backup incremental chains remain intact after an inventory change in VMware vSphere vCenter. Do not run any jobs before using the migration tool; otherwise, the migration process won't be possible.
Veeam Backup & Replication tracks Virtual Machines in its jobs by their Managed Object Reference ID (MoRef ID), which will change when a VM is moved to another vCenter, a new vCenter Database is used, or the VM is removed and re-added to vCenter inventory.
The Migration Tool is available here. Before using this tool, it is highly recommended to take a configuration backup of your VeeamBackup database. Note: The utility will work only with a source vCenter migration. If the Replication target vCenter is changed, you must manually map source VMs to their replicas. If, for some reason, you have already added the new vCenter or ran any jobs which will have added new Ref-IDs to the database, you can roll the Veeam Backup & Replication database back using the Configuration Restore function. If you use the VMware-provided VCSA Migration tool, you will need to manually remove and re-add VMs to jobs through the new VCSA after adding it to Veeam. VMware highly recommends migrating to a VCSA, as they are phasing out the Windows-based vCenter.https://blogs.vmware.com/vsphere/2017/08/farewell-vcenter-server-windows.html
MD5 checksum for MigrationTool_9.5.zip: 1A6C690BEFE3481A49C13ABC17C8D6D6
