In this blog, we will convert one of the existing ROBO site from its 2 node vSAN cluster to a 3 node configuration.
Blog Series
- Confgure vSAN in Single Site
- Create vSAN SSD Disks from HDD
- Remove an esx node from the vSAN cluster
- Scaling vSAN by adding a new esx node
- Two nodes vSAN7 Configuration
- Convert 2-Node vSAN to 3-node configuration
- VMware vSAN Stretched Cluster
Prerequisites
- Follow Steps 1-13 to prep a new ESX node ready
- Disable DRS and HA on the vSAN Robo Cluster
- Disable Stretched clustering
- Delete the fault domain in place
- Configure and add the 3rd host into the cluster
- Wait for the vSAN background operations to finish.
- Perform a VM creation and Network tests after new node joins In
- Shutdown the witness node
Procedure
1– Disable DRS and HA on vSAN Robo Cluster
2- I’ve completed Steps 1-13 and connected a new host to our vCenter Cluster
3– Under vASN Configuration- Disable Streched Cluster
4– Click Remove to remove witness host from our vSAN configuration
5-The vSAN configuration type now shows a single site instead of stretched.
6– We will now need to delete the Fault domains. Choose the Secondary and Delete
7– Confirm the deletion
9- After deleting the fault domains, we will now have our esx hosts listed under the Standalone hosts.
10- We will notice on the vSAN health configuration that our nodes are now operating under reduced redundancy as our witness is removed
11- Move the new host into the cluster
13- From here, we can create a new disk group or choose the option to claim unused disks. I’ll choose the option of Creating a new disk group
14- Pick the disk for capacity and cache tier.
15- The 3rd node will now become a part of our vSAN datastore configuration
16- Navigate to the Monitor > Skyline Health > vSAN object health > Repair objects immediately to kick off the objects repair immediately.
17- Monitor the object repair status and in a few moments your data will be spread across the new node.
18- Verify the status of vSAN disks
19- Our vSAN is now a 3 node cluster , we can now power off and delete the witness esx host
