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

Upgrade path when not enough resources in the cluster<br />

A common question is what is the recommended upgrade path for customers who<br />

have overcommitted and do not have enough free space to do a full evacuation, for<br />

example 3 node clusters?<br />

The vsan.v2_ondisk_upgrade has an option called allow-reduced-redundancy. It<br />

should be noted that there are risks associated with this approach but unfortunately<br />

there is no other way to do the upgrade. For a portion of the upgrade, virtual<br />

machines will be running without replica copies of the data, so any failure during<br />

the upgrade can lead to virtual machine downtime.<br />

When this option is used, the upgrade deletes and creating disk groups one at a time,<br />

on each host, and then allows the components rebuild once the on-disk format is at<br />

v2. When the operation has completed on the first host, it is repeat for the next host<br />

and so on until all hosts in the cluster are running on-disk format v2. However<br />

administrators need to be aware that their virtual machines could be running<br />

unprotected for a period during this upgrade.<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 / 1 7 8

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

Saved successfully!

Ooh no, something went wrong!