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 />

Note that the VM Home Namespace does not implement the Stripe Width policy<br />

setting, thus we only see a single component in the RAID-1 mirror/replica; RAID-1 is<br />

used for implementing the Failures To Tolerate policy setting.<br />

There is also a single component called a Witness to help the object to remain<br />

accessible in the event of a failure. An object will remain accessible so long as:<br />

1. There is a full replica/mirror copy without any failing components available<br />

2. Greater than 50% of the components or votes within an object are available,<br />

which includes the witness.<br />

This is the VMDK object and its components as it appears in version 5.5 of the<br />

vSphere web client.<br />

The VMDK object shown here implements both the Failures to Tolerate and Stripe<br />

Width settings. The RAID-1 has got two mirrors once again, but now each side of the<br />

mirror is made up of a RAID-0 to represent the stripe. It should be noted that stripe<br />

width is a minimum value; there may be more stripes than what was placed in the<br />

VM Storage Policy.<br />

If the VMDK storage object is too big to fit onto the free space on a single hard disk,<br />

then Virtual SAN will automatically stripe it across multiple hard disks. Also note<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 / 91

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

Saved successfully!

Ooh no, something went wrong!