6.2

Table Of Contents
2 Confirm that you can log in to the vRealize Automation console by navigating to https://vcac-
hostname.domain.name/vcac, where vcac-hostname.domain.name is the address of the load
balancer.
3 After you have verified that the new vRealize Appliance is accessible by using the load balancer, re-
enable the other nodes.
Test Appliance Database Failover
Test failover functionality from the primary appliance database machine to the secondary machine.
For this test, the appliance database is failed over, and the replica database on the secondary appliance
becomes the master database.
Prerequisites
The appliance database is installed and configured on primary and secondary vRealize Appliances as
described in vRealize Automation Installation and Configuration.
Procedure
1 Log in to your primary, or master, appliance as root using SSH.
2 Stop the vpostgres service using the service vpostgres stop command.
A message similar to the following appears.
# service vpostgres stop
Stopping VMware vPostgres: Last login: Mon Apr 27 19:49:26 UTC 2015 on pts/0
ok
3 Log in to the secondary appliance as root using SSH.
4 Run the /opt/vmware/vpostgres/current/share/promote_replica_to_primary command as
the postgres user to promote the replica database to master.
su - postgres
/opt/vmware/vpostgres/current/share/promote_replica_to_primary
server promoting
Note After running this command, the replica database on the secondary appliance becomes the
master. The appliance database on the original primary appliance does not become an actual replica
until you run the run_as_replica command.
5 Log in to the targeted replica appliance machine as root using SSH.
6 Configure replication using the following command.
./run_as_replica -h master database appliance -b -W -U replicate
Replace the parameters with the following values.
Installation and Configuration
VMware, Inc. 81