Before you upgrade from vRealize Automation 7.1, 7.2, or 7.3.x to 7.4, shut down and take a snapshot of each vRealize Automation IaaS server on each Windows node and each vRealize Automation appliance on each Linux node. If an update is unsuccessful, use the snapshot to return to the last known good configuration and attempt another upgrade.

For information about starting vRealize Automation, see Start Up vRealize Automation.


  • Backup Prerequisites for Upgrading vRealize Automation 7.1, 7.2, or 7.3 to 7.4.

  • Beginning with vRealize Automation 7.0, the PostgreSQL database is always configured in high-availability mode. Log in to the vRealize Automation appliance management console and select vRA settings > Database to locate the current Master node. If the database configuration is listed as an external database, create a manual backup of this external database.

  • If the vRealize Automation Microsoft SQL database is not hosted on the IaaS server, create a database backup file.

  • Verify that you have completed the backup prerequisites for upgrading.

  • Verify that you have taken a snapshot of your system while it is shut down. This is the preferred method of taking a snapshot. See your vSphere 6.0 Documentation.


    When you back up the vRealize Automation appliance and the IaaS components, disable in-memory snapshots and quiesced snapshots.

  • If you modified the app.config file, make a backup of that file. See Restore Changes to Logging in the app.config File.

  • Make a backup of the external workflow configuration (xmldb) files. See Restore External Workflow Timeout Files.

  • Verify that you have a location outside your current folder where you can store your backup file. See Backup Copies of .xml Files Cause the System to Time Out.


  1. Log in to your vSphere client.
  2. Locate each vRealize Automation IaaS Windows machine, and each vRealize Automation appliance node.
  3. To preserve data integrity you must shut down in a specific order. If you are using vCenter Server to manage your virtual machines, use the guest shutdown command to shut down vRealize Automation. See Shut Down vRealize Automation and follow the specified order.
  4. Take a snapshot of each vRealize Automation machine.
  5. Use your preferred backup method to create a full backup of each appliance node.
  6. When you start vRealize Automation from the beginning, such as after a power outage, a controlled shutdown or after recovery, you must start the components in a specified order. For information, see Start Up vRealize Automation.
  7. Log in to each vRealize Automation appliance management console and verify that the system is fully functional.
    1. Click Services.
    2. Verify that each service is REGISTERED.

What to do next

Set the vRealize Automation PostgreSQL Replication Mode to Asynchronous.