v.: 2020-09-04
Copyright of the European Union is effective (Copyright EU) (c) 2019 GENEREX Systems GmbH, Hamburg, Germany, All rights reserved
TEL +49(40)22692910 - EMAIL generex@generex.de - WEB www.generex.de (This and all other product datasheets are available for download.)
48
Part 3: Selecting “Host are also vSAN nodes” at vSAN Safely decommission vSAN nodes
This setting enables several sub menus and a vSAN time out warning.
Keep an eye on this warning message!
A vSAN is a little bit tricky when running a shutdown routine and the vSAN has been terminated incorrectly. It is even possible
that a wrong configured shutdown routine leads into data corruption or even total data loss.
vSAN shutdown options
No data evacuation
This is the fastest way to ensure system shutdown. It shuts down the virtual machines, and then the vCenter synchronizes all
the hosts that are inside the vSAN. There will be no data migration or virtual machines to be moved to other hosts.
Evacuate all data to other hosts
In principle, it is the same function that triggers vMotion. A vSAN can also be spanned across different sites, so you can also
offload virtual machines to external hosts that are not in the vSAN cluster you are about to shut down. if you use vMotion, it will
be executed first. Due to this fact it is possible that your vSAN host has no virtual machines that need a migration. But you may
use it as "second try" to move machines away from your vSAN...
Ensure data accessibility
If larger vSAN systems provide enough capacities for redundancies, no data will be moved. Data migration will only be done for
data without redundancy.
Note
With vSAN extensions, RCCMD introduces solution to allow you performing an emergency shut down of the entire vSAN system
as fast as possible - virtual machines that have been previously migrated to another location via vMotion are not affected.
Due to the fact you want to stop and shut down the vSAN because there is an emergency, selecting "No data evacuation" is the
best choice.
vSAN Resync timeout in Seconds
This setting is the basic time window RCCMD grants the vCenter synchronize the databases between the hosts before starting
the next point in the shutdown sequence. This time window is a little bit tricky, because the resync time is a very relative value -
in principle you can say it lasts as long as it takes ... the vCenter does not tell you an estimated resync time, you need to test it
during a manual shut down. If your vCenter announces the job is done, you have the minimum time window for your emergency
shutdown. Please calculate some extra time for this time window because the measured time during a manual shutdown is just
a snapshot and not a general value.
To Next Page
Loading...
