1-800-691-1991 | 9am - 8pm ET
EN

vCenter Migration Utility

KB ID: 2136
Product: Veeam Backup & Replication 11, Veeam Backup & Replication 10a, Veeam Backup & Replication 9.5
Published: 2016-06-08
Last Modified: 2021-06-21

Challenge

If a Virtual Machine's MoRef is changed due to migration to new vCenter / inventory change in vCenter, you would 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 ID's 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.
Unsupported Workaround

This tool is provided as a courtesy and is not supported by Veeam Technical Support. Use it at your own risk.

If any issue occurs during this tool's usage, you are advised to restore from a configuration backup to revert the Veeam Backup & Replication server to the last known stable state.

Veeam Technical Support will not assist in the usage or troubleshooting of this tool.

Cloud Connect Jobs

This tool cannot fix jobs targeting a Cloud Connect repository.

You must perform an Active Full backup.

Cause

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.

Solution

The Migration Tool is available here.

Before using this tool, it is highly recommend to take a configuration backup of your VeeamBackup database.

Note:

  • The utility will work only with a source vCenter migration. If Replication target vCenter is changed, you will need to 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 remove and re-add VMs to jobs manually 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

More information

MD5 checksum for MigrationTool_9.5.zip: 1A6C690BEFE3481A49C13ABC17C8D6D6
KB ID: 2136
Product: Veeam Backup & Replication 11, Veeam Backup & Replication 10a, Veeam Backup & Replication 9.5
Published: 2016-06-08
Last Modified: 2021-06-21

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later
Knowledge base content request
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.