VMware vSphere • Re: New vCenter Same Name

You're very welcome Zew.

This situation is part of what the Set-VBRVCenterName cmdlet is for -- if you are migrating but keeping the same vCenter name, the process will be:

1. Manual Configuration Backup (always best practice to have a backup "just in case")
2. Run both of the optional cmdlets Set-VBRVmBiosUuid and Set-VBRVCenterName
3. Confirm in UI that the current vCenter has "_old" appended to its name and proceed
4. Add the "new" vCenter -- normally Veeam would prevent adding "duplicates", but in this case it's allowed.
5. Follow the rest of the steps in the User Guide

The Set-VBRVCenterName cmdlet allows for the drop-in replacement scenario you're describing where new vCenter has same name/hostname as old vCenter. So temporarily you will have the vCenter twice in VBR, then you will run the cmdlets as prescribed. Once all looks good (jobs are working normally), remove the _old vCenter.

Statistics: Posted by david.domask — Jun 18, 2025 8:55 am

---