Hello All,
I am experimenting with the new vCenter appliance from VMware, but ran into an issue with vRanger. I have disconnected a host from our existing vCenter installation and added it successfully to the new VCSA. I have also added the new VCSA to the vRanger configuration. vRanger sees the new vCenter, along with the ESXi host on the new vCenter.
The problem I see is that the jobs now fail for the VMs on the moved host. I can see the jobs in the My Jobs tab, but when I try to run one of them, it fails almost instantly:
The inventory node <VM name> [vm-11529] is on a disconnected VC: <old vCenter server>
The job no longer shows up in the My Inventory tab, under the VM in question (I have individual jobs for each VM). Is there any way to "retarget" the new vCenter without having to set up new jobs for every VM after the migration? My concerns are the time to set up 30+ new jobs, the possibility of having to do a full backup out of sequence, and our dedupe device (ExaGrid) seeing this new backup as a new backup source, causing the backup chain to break and forcing the use of double the hard drive space on our ExaGrids until our retention period fully recycles (3-4 months).
Any ideas?
Thanks,
Quinn Judge