Recommended procedure for vRealize Automaton (vRA) service or node restart in a 3 node cluster

 Usually, when dealing with a 3-node cluster, it doesn’t matter which node is the master one. In such cases reboot of the appliances should happen always one by one with making sure each appliance has fully loaded before initiating the next reboot. One should make sure there are always 2 (two) running appliances. This ensures quorum is met and environment is fully operational.
There are three main scenarios when doing a reboot of vRA:
  1.   Reboot only the master appliance
  1. Make the replication Async.
  2. Initiate reboot on the master node.
  3. Wait for the appliance to fully load up.
  4. Make the replication Sync again. 
  1. Reboot any of the secondary appliances
  1. Reboot the passive appliance.
  2. The potential appliance now becomes passive.
  3. Wait for the rebooted appliance to fully load up.
  4. The once passive appliance now becomes a potential one.
  5. Reboot the currently passive one.
  6. Once it’s rebooted it will be automatically switched to the potential role and all roles should remain the same
  1. Reboot all three appliances
  1. Turn the replication to Async mode.
  2. Reboot the master node.
  3. Wait about 30 to 60 seconds and then reboot the two other nodes.
  4. After all servers are fully loaded (all services appear as “Registered”) turn the replication to Sync mode again.


Popular posts from this blog

vCloud director 9.7 appliance deployment step by step guide

How to Install and Uninstall Guest agent for vRA Windows machines

VM console fails to connect - vCloud director 9.7