You can monitor the status of virtual machine objects that are being resynchronized in the Virtual SAN cluster.
The following events trigger resynchronization in the cluster:
- Editing a virtual machine (VM) storage policy. When you change VM storage policy settings, Virtual SAN might initiate object recreation and subsequent resynchronization of the objects.
Certain policy changes might cause Virtual SAN to create another version of an object and synchronize it with the previous version. When the synchronization is complete, the original object is discarded.
Virtual SAN ensures that VMs continue to run and are not interrupted by this process. This process might require additional temporary capacity.
- Restarting a host after a failure.
- Recovering hosts from a permanent or long-term failure. If a host is unavailable for more than 60 minutes (by default), Virtual SAN creates copies of data to recover the full policy compliance.
- Evacuating data by using the Full data migration mode before you place a host in maintenance mode.
- Exceeding the utilization threshold of a capacity device. Resynchronization is triggered when capacity device utilization in the Virtual SAN cluster that approaches or exceeds the threshold level of 80 percent.
To evaluate the status of objects that are being resynchronized, you can monitor the resynchronization tasks that are currently in progress.
Verify that hosts in your Virtual SAN cluster are running ESXi 6.0 or later.
- Navigate to the Virtual SAN cluster in the vSphere Web Client.
- Select the Monitor tab and click Virtual SAN.
- Select Resyncing Components to track the progress of resynchronization of virtual machine objects and the number of bytes that are remaining before the resynchronization is complete.You can also view information about the number of objects that are currently being synchronized in the cluster, the estimated time to finish the resynchronization, the time remaining for the storage objects to fully comply with the assigned storage policy, and so on.If your cluster has connectivity issues, the data on the Resyncing Components page might not get refreshed as expected and the fields might reflect inaccurate information.