Before you upgrade, shut down and take a snapshot of your vRealize Automation 6.2.5 environment components.

Before you begin

  • Verify that the embedded PostgreSQL database is in high-availability mode. If it is, locate the current Master node. See the knowledge base article http://kb.vmware.com/kb/2105809.

  • If your environment has an external PostgreSQL database, create a database backup file.

  • If the vRealize Automation Microsoft SQL database is not hosted on the IaaS server, create a database backup file. For information, find article on the Microsoft Developer Network about creating a full SQL Server database backup.

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

About this task

Before you upgrade, take a snapshot of these components while your system is shut down.

  • vRealize Automation IaaS servers (Windows nodes)

  • vRealize Automation appliances (Linux nodes)

  • vRealize Automation (SSO) Identity node

If the upgrade fails, use the snapshot to return to the last known good configuration and attempt another upgrade.

Procedure

  1. Log in to your vCenter Server.
  2. Locate these vRealize Automation 6.2.5 components.
    • vRealize Automation IaaS servers (Windows nodes)

    • vRealize Automation appliances (Linux nodes)

    • vRealize Automation (SSO) Identity node

  3. For each of the following virtual machines, select the virtual machine, click Shutdown guest, and wait for the virtual machine to stop. Shut down these virtual machines in the following order.
    1. IaaS proxy agent virtual machines

    2. DEM Worker virtual machines

    3. DEM Orchestrator virtual machine

    4. Manager Service virtual machine

    5. Web Service virtual machines

    6. Secondary vRealize Automation virtual appliances

    7. Primary vRealize Automation virtual appliance

    8. Manager virtual machines (if any)

    9. Identity Appliance

  4. Take a snapshot of each vRealize Automation 6.2.5 virtual machine.
  5. Clone each vRealize Automation appliance node.

    You perform the upgrade on the cloned virtual machines.

  6. Power off each original vRealize Automation appliance virtual machine before you upgrade the cloned virtual machines.

    Keep the original virtual machines powered off and use them only if you must restore the system.

What to do next

Increase vCenter Server Hardware Resources for vRealize Automation 6.2.5.