Hello suhag79
"On 4 node vSAN cluster, if we put one node in MM, where can we check the component rebuilding on rest of the three vSAN host ?"
This depends on a number of factors:
- If you place the host in Maintenance Mode with 'Ensure Accessibility' it will not start rebuilding the data on another node until 60 minutes has passed (with default vsan.clomrepairdelay settings) or until the 'repair Objects immediately' button has been pressed via the vSAN Health page (under 'Data').
- If you place the host in Maintenance Mode with 'Full Data Evacuation' then it will start recreating the new copies of the data on the rest of the nodes in the cluster (how much and what on each depends on what components already reside there and the available space).
- If it is a 4-node cluster with RAID5 Storage Policy in use then it can't rebuild any data with only 3 nodes (as 4 Fault Domains are required).
Resync can be monitored as Joerg's comment above or alternatively via RVC:
> vsan.resync_dashboard <pathToCluster>
There also is the possibility of writing some funky scripts to pull this info from CMMDS directly on the host.
If you want to look at one specific Data Object and where it is reconfiguring/rebuilding then you can look at this Object from the Web Client (Virtual Disks tab and/or select VM in inventory) or via RVC:
> vsan.vm_object_info <pathToVM>
or
> vsan.object_info <pathToCluster> <ObjectUUID>
Bob