7.0

Table Of Contents
g Click vRA Settings > Database.
h Locate the former master node, and click Reset.
i After a successful reset, restart the former master node.
j With the former master powered on, verify that the following services are running.
haproxy
horizon-workspace
rabbitmq-server
vami-lighttp
vcac-server
vco-server
k Re-add the former master node to the external load balancer.
Note If a master node that was demoted to replica is still listed as master, you might need to
manually re-join it to the cluster to correct the problem.
Scenario: Perform a Maintenance Database Failover
As a vRealize Automation system administrator, you must perform an appliance database maintenance
failover operation.
This scenario assumes that the current master node is up and running normally. There are two database
failover maintenance steps: maintenance of the master and maintenance of a replica node. When a
master node has been replaced so that it becomes a replica, you should perform maintenance on it so
that it is suitable to become the master again should the need arise.
Prerequisites
n
vRealize Automation is installed and configured according to appropriate instructions in the Installing
vRealize Automation 7.0.
n
Log in to the vRealize Automation management console as root.
n
You have an appropriate embedded Postgres appliance database cluster installed and configured.
n
If your database uses synchronous replication mode, ensure that there are at least three active nodes
in the cluster.
Procedure
1 Ensure that the current master node is up and running in preparation for maintenance.
2 Select the most suitable replica node for promotion to the master, and click Promote.
The old master is demoted to replica status, and the new master is promoted.
3 Exclude the replica virtual appliance address from the external load balancer pool.
4 Perform the appropriate replica maintenance.
Managing vRealize Automation
VMware, Inc. 26