Replacing old vCenter with new vCenter with different vCenter name: vRA 6.2.2

[VirExprt]

Hello ,

we are planning to migrate workload from One vCenter (set for decommisoning) to New vCenter with new name but we are not sure how will vRA react to this change since we will be adding another vSphere endpoint?

will all the VMs appear 'Missing' in VM status?

do we have to manually change the reservation for around 5000 VMs ?

We have vRA 6.2.2 in Distrubuted Deployment model.

Please advice the best possible approach.

thanks in advance.

- MG

[AcuteSys]

running into the same problem. any help on this?

[VMSavvy]

That looks scary!!

We recently had an issue where one of our admins (who doesn't know vRA) renamed a couple of clusters in our vCenter. The data collection, reservations etc got updated later but it had a cascading affect and VM provisioning started to fail as the VC agent was still pointing to the old cluster during deployments. To overcome this problem I had to clear out all the traces of old cluster names from the SQL DB, reinstall both the VC agents (distributed setup) and then I had a clean deploy/destroy functionality back again. Just 2 cents before you really get into problems..

VMSavvy

[Czernobog]

I did exactly this some time ago, I'll just repost the method I posted in case someone is interested in this topic Migrating vRA7-managed VMs from one vCenter (vRA Endpoint) to another - actions required in vRA? :

In vRA 6 all you have to do is to:

- create a new vSphere Endpoint for your new vCenter - both vCenters have to have the same ID set <- important!

- check if the new Compute Ressource is recognized correctly in vRA

- move your hosts & vms to the new vCenter.

- edit reservations, so they point to the new compute resource. Check network profile - network path assignment.

I did this when I had to move all hosts and vm's to a new vCenter and it was done without downtime for clients owning vms in vRA. It was a bit of manual work, but nothing really demanding or risky.