We are running a VCD 10.4 single cell instance (round 1500 VMs) on a linux VM. Currently due to multiple issues (vcenter not connecting after upgrade to 10.4.1) as well as existing inconsistencies between vCD and vcenter, I would like to explore the option of redeploy vCD appliance and tsart from scratch. Since its the same single vcenter, would it possible to gracefully migrate (NO DOWNTIME to vcenter env, vCD portal offline is fine for a week time) to new instance?Couldnt find a Vmware KB for this migration..
I'd advise addressing the underlying source of the problem you're now experiencing. What assurances are there that the new VCD deployment will function properly? Any particular justification for using a single-cell instance? To address your question, you may use the same VC to support various VCD as long as each one uses a separate Cluster.
The inconsistencies should be able to be fixed if you know enough of the database and remove some tables. What exactly are the inconsistencies you are experiencing? I might be able to help.
As for the vCenter Server not connecting, what is the error you are seing at that part?
I was abl eto take care of vcenter connection by using a different account. Inconsistencies are for portgroups mainly. vCenter and vCD database have different portgroup for the same VM. So when a VM is powered off, it comes back online with information provided by vCD (which is not updated and incorrect)..There are around 50 workloads with problem..This happened because engineers used vCenter to provision workloads and not the vCD portal.
Hmm oke. Did you (you probably did) do a reconnect for the vCenter Server and a refresh? The reconnect actually empties the vCenter inventory tables in the VCD database, and the refresh re-populates them.
That should usually help in these kind of situations.