VMs can become inaccessible after a single failure if storage policy is set to "No Data Redundancy"
search cancel

VMs can become inaccessible after a single failure if storage policy is set to "No Data Redundancy"

book

Article ID: 402909

calendar_today

Updated On:

Products

VMware vSAN

Issue/Introduction

VMs can become inaccessible if storage policy is set to no data redundancy (FTT=0) and there is a single point of failure such as the host/disk/diskgroup. 

Environment

  • VMware vSAN 7.x
  • VMware vSAN 8.x
  • VMware vSAN 9.x

Cause

If no data redundancy (FTT=0) is used as a storage policy on any of the VMs on the vSAN environment where either a single host, disk or disk group failure occurs, there is a risk of data becoming unavailable. 

Resolution

If a vSAN host/disk/diskgroup is down where FTT=0 (no data redundancy) objects reside on, try get the host/disk/diskgroup back online and this should bring the VMs back online. If this fails, a restore of VMs from the backups will need to be performed. 

It's not recommended to use FTT=0  (No data redundancy) storage policy on production VMs, as any failure can potentially cause some VMs to become inaccessible. 

It is recommended to use a Storage Policy with RAID 1, 5, or 6 for production level VMs, so a single failure can be withstood without an impact to production.

 

 

Additional Information