When attempting to perform a virtual machine (VM) backup or create a manual snapshot in a 5 node vSAN cluster, the task fails with one or more of the following errors in vCenter Server:
Additionally, the vmware.log for the affected VM may contain entries similar to:
vcpu-0 - OBJLIB-VSANOBJ: VsanObjCreateInt: Failed to create object: No space left on device (1835010).vcpu-0 - DISKLIB-LINK : DiskLinkCreate: Failed to create extent: Out of resourcesvcpu-0 - SNAPSHOT: SnapshotBranch failed: Out of resources (5).
During the time of the issue one host was in maintenance mode.
VMware vSAN (all versions)
To resolve this issue, ensure the vSAN cluster meets the minimum host requirements for the configured storage policy:
Refer below kb to see the minimum number of hosts required for each Raid policy with the FTT selected:
If a host must remain in maintenance mode for an extended period, you may temporarily change the VM's storage policy to a lower redundancy level (e.g., from FTT=2 to FTT=1) to allow snapshots to proceed.
Note: This will reduce the data redundancy for that VM until the original policy is reapplied.