09.03.2015 Views

VSAN-Troubleshooting-Reference-Manual

VSAN-Troubleshooting-Reference-Manual

VSAN-Troubleshooting-Reference-Manual

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Diagnostics and <strong>Troubleshooting</strong> <strong>Reference</strong> <strong>Manual</strong> – Virtual SAN<br />

Object operational state: healthy vs. unhealthy<br />

The operation state of an object can be healthy or unhealthy, depending on the type<br />

of failure and number of failures in the cluster. If a full mirror is still available, and<br />

more than 50% of the object’s components are available in Virtual SAN 5.5, (or 50%<br />

of the object’s votes are available in Virtual SAN 6.0), the object’s Operational State<br />

is said to be healthy. If no full mirror is available, or less than 50% of the<br />

components are available (possibly due to multiple failures in the cluster when the<br />

VM is configured to tolerate 1 failure only), then the object’s operational state is said<br />

to be unhealthy.<br />

If we take the example that there were two failures in the cluster, the Compliance<br />

Status remains at Not Compliant, the Operation Status changes to Unhealthy, and the<br />

reason for the unhealthy state is displayed. In this example, the reason for the<br />

“Unhealthy” Operations State is “disk unavailable” as shown below:<br />

V M W A R E S T O R A G E B U D O C U M E N T A T I O N / 59

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!