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.)
49
Seconds to wait before setting Maintenance Mode for vSAN
Once the resync is completed, the vCenter is the last surviving virtual machine that needs to be shut down. With this setting, you
define how long the vCenter has time to shut itself down before RCCMD starts the next step of the shutdown sequence.
Determine which VM is running the vCenter
Inside a vSAN, the vCenter is more:
The vCenter manages the complete data transfer within a vSAN and handles the complete post synchronization phase during a
vSAN shut down. This means:
If the vCenter runs inside a vSAN or runs on a host that will be shut down to fast, the complete vSAN hung up. If the vCenter is
located as a virtual machine within the vSAN, RCCMD needs to know the name of the virtual machine in order to exclude it from
virtual machine shutdown.
Note:
The vCenter that handles a vSAN is not always inside this cluster – it may be installed somewhere and handled separately. If
the virtual machine with the vCenter is not inside the list of the hosts to be shut down, you do not need to enter it at this point.
But you need to take an eye on it if when using different RCCMD appliances – Without it’s vCenter, a vSAN cannot shut down
as expected.
Advanced Settings
use Advanced Settings for additional settings to configure RCCMD. The menu is divided into three parts:
Event Logfile
In general, any RCCMD Signal affecting the client will be logged. Due to the fact server systems may provide limited memory
resources for log files, it may be necessary to limit the size of the log file to a maximum size to consume. In case the maximum
file size is reached, the oldest entry is replaced by a new entry.
To Next Page
Loading...
