approach to add the vCenter in fresh vSAN setup

[suhag79]

Hi,

We are installing 4 node vSAN cluster at remote site. To install the vCenter at remote site within vSAN, we are planning on below approach.

- install bare metal ESXi 6.5 on all 4 vSAN node

-deploy the vCenter 6.5 appliance (TempvCenter) @ already existing central VMware site

- take all remote 4 vSAN node under this temp vCenter built on central site

-create the vSAN disk group

- Now, in any one of the disk group, deploy the production vCenter appliance

- disconnect one by one ESXi node from central and connect it to local vCenter node

-configure the cluster

is anyone seeing any challenge on the above approach or can anyone suggest better method for this ?

[daphnissov · Accepted solution]

No need to do any of that (other than get at least one node online). With vSAN 6.6 and vCSA 6.5, you can now bootstrap the vCSA to a vSAN datastore. This blog has the information on that process.

Bootstrap the VCSA onto vSAN 6.6 with Easy Install - Virtual Blocks

[TheBobkin]

Hello Suhag79

Bootstrapping vCenter is the easiest option for set-up and integrated into vCSA install - however, I would advise against managing any vSAN cluster from a vCenter stored on the vsandatstore as issues affecting Object availability could cause vCenter to not be accessible and this makes troubleshooting and resolving issues a lot more difficult.

If moving vSAN hosts from one vCenter to another there is actually no need to disconnect it will do this automatically when it joins another - the only thing to consider is do one host first and then can do all the rest at once.

Bob

[GreatWhiteTec]

When replacing vCenter it is important to have some steps in mind, like making sure the new vCenter state is the authoritative for your vSAN cluster.

Please refer to this blog for more information

Replacing a vCenter server for existing vSAN hosts - Virtual Blocks