If a virtual machine uses Virtual SAN storage, its storage accessibility might change according to the type of failure in the Virtual SAN cluster.

Changes in the accessibility occur when the cluster experiences more failures than the policy for a virtual machine object tolerates.

As a result from a failure in the Virtual SAN cluster, a virtual machine object might become inaccessible. An object is inaccessible if a full replica of the object is not available because the failure affects all replicas, or when less than 50 percent of the object's votes are available.

According to the type of object that is inaccessible, virtual machines behave in the following ways:

Table 1. Inaccessibility of Virtual Machine Objects

Object Type

Virtual Machine State

Virtual Machine Symptoms

VM Home Namespace

  • Inaccessible

  • Orphaned if vCenter Server or the ESXi host cannot access the .vmx file of the virtual machine.

The virtual machine process might crash and the virtual machine might be powered off.

VMDK

Inaccessible

The virtual machine remains powered on but the I/O operations on the VMDK are not being executed. After a certain timeout passes, the guest operating system ends the operations.

Virtual machine inaccessibility is not a permanent state. After the underlying issue is resolved, and a full replica and more than 50 percent of the object's votes are restored, the virtual machine automatically becomes accessible again.