If a system failure occurs on the active Manager Service host, you can promote a passive Manager Service host to replace it. You can configure vRealize Automation to activate a secondary failover server when a system failure occurs on the Manager Service host.

Prerequisites

If you are using F5 Load Balancer, verify that active and passive Manager Service nodes are configured correctly with the load balancer. This configuration is required to avoid Proxy Agent ping failures.

  1. Log in to the F5 load balancer and select Local Traffic > Pools.

  2. Select the Manager Service pool.

  3. Click Advanced in the Configuration section.

  4. Select the Drop for the Action On Service Down option.

  5. Click OK and then Finished.

See Install the Active Manager Service for more information.

Procedure

  1. Change the startup type of the vCloud Automation Center Manager Service on the active Manager Service host to manual start up, if the system is available.
    1. Select Start > Administrative Tools > Services on the active server.
    2. Select Manual as the startup type of the vCloud Automation Center service.
    3. Stop the VMware vCloud Automation Center service.
  2. Make the passive Manager Service host the active host by changing the startup type of the vRealize Automation Manager Service to automatic start up and then start the service.
    1. Select Start > Administrative Tools > Services on the active server.
    2. Select Automatic as the startup type of the vRealize Automation service.
    3. Start the VMware vCloud Automation Center service.
  3. (Optional) : Open a new browser window and verify that you can navigate to the Manager Service health check URL, located at: https://MS_LB_FQDN/VMPSProvision, where MS_LB_FQDN is your Manager Service Load Balancer FQDN.