2 Posts
0
908
August 20th, 2021 02:00
How to rename a vCenter in NetWorker?
Hi!
I was approached by a customer, that they are planning to rename their vCenter server in the next few months. I did some tests with my lab VCSA (FQDN & CNAME pointing to same IP). But I didi not manage to keep the "old" backups that were taken with the old vCenter name. Save sets still there, but not visible in Restore wizard.
Here is what I did:
- configure vCenter with FQDN & create some vProxy backups.
- Remove the entire vCenter config (delete vProxy, VM group)
- Rename the vCenter client object. (create client with CNAME & clientID from FQDN)
- configure vCenter with CNAME
After this, I can successfully run backups & I see the Save Sets that were backed up using the FQDN now belong to the CNAME. That was expected.
But when I try to restore a backup using NMC restore wizard, I can only see the backups that were taken after the renaming of the vCenter. Each VM shows up 2 times (but same UUID) and no matter which one i choose, the old backups are not shown anymore.
Has anyone ever solved this?
Any help is highly appreciated.
Br,
Reinhard
crazyrov
4 Operator
•
1.3K Posts
1
August 22nd, 2021 23:00
Hello @quored ,
The procedure is actually outline in the NetWorker VMWare integration guide. You can refer to it here - https://dl.dell.com/content/docu104870_networker-19-5-vmware-integration-guide.pdf?language=en_us, page 29.
Here is the extract:
Perform the following steps to rename the vCenter to a different hostname:
1. Create a hypervisor resource in NetWorker server pointing to the new hostname of the vCenter.
NOTE: If you need the old backups, then retain both vCenter resources in NetWorker until
savesets of older vCenter expires.
2. Configure new vCenter groups and workflows and map to the required VMs in the new vCenter.
3. Reconfigure the existing vProxy resources in NetWorker to point to the new vCenter.
4. Use NWUI H5 interface to restore any of the older vCenter backups.
NOTE: Restore of vCenter backup using vCenter plug-in is not supported.
quored
2 Posts
0
August 23rd, 2021 00:00
Hello @crazyrov,
so it was there all the time. Shame on me, that I didn´t check the docs first.
But it´s not really renaming anything. It just gets added as a second hypervisor. Anyway, it should do the trick. Thank you, for pointing me in the right direction!