A six-node vSAN ESA cluster contains multiple Virtual Machines (VMs), and a vSAN storage policy with the rule ''Failures to tolerate'' set to ''1…

In VMware vSphere, Storage Policy Based Management (SPBM) governs how storage policies are applied to Virtual Machines. When a vSAN administrator manually modifies an existing, assigned VM storage policy (such as changing the "Failures to tolerate" rule from RAID-5 to RAID-6), the underlying storage objects are not automatically reconfigured by the mere act of saving the policy edit. Instead, the compliance status of the associated VMs immediately changes to "Out of Date." To instantiate the new RAID-6 configuration on the vSAN ESA datastore, the administrator must explicitly reapply the storage policy to the affected VMs. Once reapplied, vSAN evaluates the 6-node cluster's capacity and initiates the component resynchronization to meet the new FTT=2 requirements.

B: SPBM policies are vCenter-wide and not rejected during editing based on cluster size. The policy saves successfully, but VMs become non-compliant if requirements cannot be met.

C: When reapplied, vSAN processes object reconfigurations concurrently across the cluster, managed by resync throttling mechanisms, rather than strictly applying them serially to one VM at a time.

D: The 60-minute delay refers to the vSAN Object Repair Timer (CLOMRepairDelay), which is triggered by unexpected host or component failures, not by administrative storage policy changes.

1. VMware vSphere 8.0 Product Documentation

vSphere Storage Guide

Section: "Storage Policy Based Management" > "Edit or Clone a VM Storage Policy". (Specifically notes: "Until you reapply the policy

the compliance status of the virtual machine is Out of Date. You must reapply the policy to update the virtual machines.")

2. VMware vSAN 8.0 Administrator Guide

Section: "Managing Virtual Machine Storage Policies" > "Changing VM Storage Policies". (Details the requirement to trigger a reapply task to initiate object reconfiguration).

3. VMware vSAN 8.0 Monitoring and Troubleshooting Guide

Section: "vSAN Cluster Monitoring" > "Changing the Default Object Repair Timer". (Defines the default 60-minute delay for absent components

invalidating Option D).