7.0

Table Of Contents
Procedure
1 Locate the secondary vRealize Automation appliance node in your 6.2.x environment.
2 Open a shell console and stop the vPostgres service.
execute: service vpostgres stop
3 Navigate to /storage/db/pgdata/postgresql.conf and backup the file.
4 Verify that the archive settings are accurate.
Note There may be multiple entries.
archive_mode = off and #archive_command = ''.
5 Navigate to the /etc/fstab file and remove lines starting with /dev/sdd, which contain the
Wal_Archive write ahead logs.
6 Navigate to /etc/vcac/server.xml and back up the file.
7 Verify that the jdbc:postgresql database connection points to the external IP address of the master
Postgres node.
8 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://198.15.100.60:5432/vcac
9 Shut down the vRealize Automation appliance.
10 Repeat steps 1-9 on each vRealize Automation appliance node in your 6.2.x environment.
11 Locate the master vRealize Automation appliance node and repeat steps 1-9.
12 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.
What to do next
Increase vCenter Server Hardware Resources for Upgrade
Increase vCenter Server Hardware Resources for Upgrade
Before you proceed with upgrade you must increase hardware resources for each vRealize Automation
appliance.
If you have taken snapshots of your vRealize Automation appliances, you must clone your appliances
and increase the hardware resources on the clones. Ensure that you have at least 60 GB of free space
for each appliance in your vCenter. After you clone your appliances, power down the original appliances
before you perform this procedure.
These steps are based on the Windows client.
Upgrading from vRealize Automation 6.2 to 7.0.1
VMware, Inc. 22