If your high-availability deployment relies on a clustered PostgreSQL server, either embedded or external, you must configure each vRealize Automation appliance node for upgrade.
About this task
You must configure each vRealize Automation appliance node in your environment first and then configure the master virtual appliance Postgres node.
If you're unsure which node is the master node, see the following KB article for more information: http://kb.vmware.com/kb/2108923.
- Locate the secondary vRealize Automation appliance node in your 6.2.x environment.
- Open a shell console and stop the vPostgres service.
execute: service vpostgres stop
- Navigate to /storage/db/pgdata/postgresql.conf and backup the file.
- Verify that the archive settings are accurate.
There may be multiple entries.
archive_mode = offand
#archive_command = ''.
- Navigate to the /etc/fstab file and remove lines starting with /dev/sdd, which contain the Wal_Archive write ahead logs.
- Navigate to /etc/vcac/server.xml and back up the file.
- Verify that the jdbc:postgresql database connection points to the external IP address of the master Postgres node.
- If the connection is not set, edit the server.xml file entry jdbc:posgresql that points to the Postgres database and point it to the external IP address of the master Postgres node for external Postgres or master virtual appliance for embedded Postgres.
For example, jdbc:postgresql://18.104.22.168:5432/vcac
- Shut down the vRealize Automation appliance.
- Repeat steps 1-9 on each vRealize Automation appliance node in your 6.2.x environment.
- Locate the master vRealize Automation appliance node and repeat steps 1-9.
- If you are upgrading a 6.2.x high-availability setup with an embedded PostgreSQL database and there is an external Load Balancer pool configured especially for PostgreSQL database, remove the external LB pool for PostgreSQL.