Resolving vSAN Compliance Issues

C.

In the given scenario, a storage controller failure has caused two vSAN disk groups to become degraded, resulting in the components contained on the drives in those disk groups also being marked degraded. As a result, vSAN reports that some objects do not comply with their assigned storage policy.

To resolve the compliance issue, we need to ensure that the components are repaired and rebuilt to restore the desired storage policy compliance. We have the following options available to us:

A. Initiate a proactive rebalance to force component repairs: A proactive rebalance can be initiated to force vSAN to repair the degraded components. During the proactive rebalance, vSAN migrates the virtual machine data and components to new disks that are compliant with the storage policy. This can result in an increase in network and storage I/O, but it can also resolve the compliance issue.

B. Degraded components are repaired after CLOM Repair Delay Timer expires: vSAN has a CLOM (Component Limit Object Manager) Repair Delay Timer that determines the amount of time it waits before repairing degraded components. This timer is set to 60 minutes by default. If the timer expires, vSAN automatically repairs the degraded components. If the degraded components are not repaired within this timeframe, we can either wait for the timer to expire or initiate a proactive rebalance.

C. Rebuilding of the degraded components starts immediately: Depending on the vSAN configuration, the rebuilding of the degraded components may start immediately. This can happen if the vSAN cluster has a high number of available hosts, and the storage policy allows for data availability during the rebuild process. This option can be ideal when the failure of the storage controller has caused a significant impact on the vSAN cluster.

D. Storage policies must be reapplied to all affected objects: It is also possible that some objects in the vSAN cluster may not comply with the assigned storage policy, even after the degraded components have been repaired. In such cases, we need to reapply the storage policy to all the affected objects manually.

In summary, to resolve the compliance issue in the given scenario, we can initiate a proactive rebalance, wait for the CLOM Repair Delay Timer to expire, allow vSAN to rebuild the degraded components immediately, or manually reapply the storage policy to all affected objects. The choice of the approach depends on the specific circumstances of the vSAN cluster and the storage policy.