If a vSAN capacity device experiences a pattern of sustained high latency, how does vSAN attemp

t to remediate the issue?

A. vSAN attempts to evacuate the data from the storage device.

B. vSphere DRS migrates all virtual machines from the host containing the affected device

C. Virtual machines with components on the affected device are rebooted if v

Sphere Proactive HA is enabled

D. The host containing the storage device is automatically placed into maintenance mode and the -vSAN storage device failure- alarms is triggered.

Explanation:

In vSAN 6.1 we introduced Dying Disk Handling to ident

ify and remediate pro-actively disks that we detected high latency from.

When failure of a device is anticipated, vSAN evaluates the data on the device. If there are replicas of the data on other devices in the cluster, vSAN will mark these components as –

absent-. -Absent- components are not rebuilt immediately as it is possible the cause of the issue is temporary. vSAN waits for 60 minutes by default before starting the rebuilding process. This does not affect the availability of a virtual machine as the d

ata is still accessible using one or more other replicas in the cluster. If the only replica of data is located on a suspect device, vSAN will immediately start the evacuation of this data to other healthy storage devices.

References:https://storagehub.vm

ware.com/export_to_pdf/vmware-vsan-6-6-technical-overview-1