- Knowledge Base Listing Page
- vCenter Migration Utility
vCenter Migration Utility
| KB ID: | 2136 |
| Product: | Veeam Backup & Replication | 9.5 | 10 | 11 |
| Published: | 2016-06-08 |
| Last Modified: | 2021-06-21 |
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Challenge
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.
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.
This tool cannot fix jobs targeting a Cloud Connect repository.
You must perform an Active Full backup.
Important! If you are migrating to a VCSA, VMware has a new migration utility, which is intended preserve existing VM MoRef IDs:
https://blogs.vmware.com/vsphere/2016/09/vcenter-server-migration-tool-vsphere-6-0-update-2m.html
https://blogs.vmware.com/vsphere/2017/01/vcenter-server-appliance-6-5-migration-walkthrough.html
Cause
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
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please try again later.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.