Got it; indeed I'm trying to imagine a bit on your setup as I didn't see the topic where you discussed it.
> 4) In Veeam, Infrastructure -> vCenter (right click context menu -> Properties) -> go through wizard accepting new certificate. (Veeam now see the vCenter just like it did orginally, but any job will fail as it doesn't know which VM is what, the MoREID problem).
Do you have a configuration backup (Veeam) from before you did this step? This is the step where you would start the migration process.
The VM Migrator cmdlets compare two vCenters added to a given VBR and then update the Veeam configuration database accordingly to do the "migration". This comparison is done with data already in the Veeam configuration database. So in your case, if you can restore Veeam's configuration database to before you made these changes, instead of your step 4 there, you will begin the migration procedure and use the Set-VBRVCenterName cmdlet on the existing vCenter in Veeam, re-add your newly rebuilt vCenter to Veeam, and then perform the migration.
> 4) In Veeam, Infrastructure -> vCenter (right click context menu -> Properties) -> go through wizard accepting new certificate. (Veeam now see the vCenter just like it did orginally, but any job will fail as it doesn't know which VM is what, the MoREID problem).
Do you have a configuration backup (Veeam) from before you did this step? This is the step where you would start the migration process.
The VM Migrator cmdlets compare two vCenters added to a given VBR and then update the Veeam configuration database accordingly to do the "migration". This comparison is done with data already in the Veeam configuration database. So in your case, if you can restore Veeam's configuration database to before you made these changes, instead of your step 4 there, you will begin the migration procedure and use the Set-VBRVCenterName cmdlet on the existing vCenter in Veeam, re-add your newly rebuilt vCenter to Veeam, and then perform the migration.
Statistics: Posted by david.domask — Jun 19, 2025 8:47 am
