Before you upgrade from vRealize Automation 7.1, 7.2, to 7.3 or 7.1, 7.2, 7.3 to 7.3.1, 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 the upgrade is unsuccessful, use the snapshot to return to the last known good configuration and attempt another upgrade.

About this task

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

Prerequisites

  • Backup Prerequisites for Upgrading vRealize Automation.

  • Beginning with vRealize Automation 7.0, the PostgreSQL database is always configured in high-availability mode. Log in to vRealize Automation Appliance Management and click 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.

    If you cannot shut down your system, take an in-memory snapshot of all the nodes. This is the non-preferred method and should only be used if you cannot take a snapshot while the system is shut down.

  • 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.

Procedure

  1. Log in to your vSphere client.
  2. Locate each vRealize Automation IaaS Windows machine, and each vRealize Automation appliance node.
  3. On each machine, click Shutdown guest in this order.
    1. IaaS Windows Server machines

    2. vRealize Automation appliance.

  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. Power on the system. See Start Up vRealize Automation in Managing vRealize Automation.

    If you have a high availability environment, complete these steps to power on your virtual appliances.

    1. Start the master vRealize Automation appliance.

    2. Log in to vRealize Automation Appliance Management, click Services, and wait until the licensing-service status is REGISTERED.

    3. Start the remaining vRealize Automation appliances at the same time.

    4. Start the primary Web node and wait for the startup to finish.

    5. Start the primary Manager Service machine and wait for 2 to 5 minutes.

      The actual time depends on your site configuration.

      Note:

      On secondary machines, do not start or run the Windows service unless you are configured for automatic Manager Service failover.

    6. Start the Distributed Execution Manager Orchestrator and Workers and all vRealize Automation proxy agents.

      Note:

      You can start these components in any order. You do not need to wait for a component to finish before you start another.

  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.