Before you run the upgrade your vRealize Automation 7.1, 7.2, or 7.3.x environment to 7.4, review these prerequisites.

System Configuration Requirements

Verify that the following prerequisites are finished before you begin an upgrade.

  • Verify that all appliances and servers that are part of your deployment meet the system requirements for the latest version. See the vRealize Automation Support Matrix at VMware vRealize Automation Documentation.

  • Consult the VMware Product Interoperability Matrix on the VMware website for information about compatibility with other VMware products.

  • Verify that the vRealize Automation you are upgrading from is in stable working condition. Correct any problems before upgrading.

  • Verify that you have changed the load balancer timeout settings from default to at least 10 minutes.

Hardware Configuration Requirements

Verify that the hardware in your environment is adequate for vRealize Automation 7.4.

See vRealize Automation Hardware Specifications and Capacity Maximums

Verify that the following prerequisites are finished before you begin an upgrade.

  • You must have at least 18 GB RAM, 4 CPUs, Disk1=50 GB, Disk3=25 GB, and Disk4=50 GB before you run the upgrade.

    If the virtual machine is on vCloud Networking and Security, you might need to allocate more RAM space.

    Although general support for vCloud Networking and Security has ended, the VCNS custom properties continue to be valid for NSX purposes. See the Knowledge Base article 2144733.

  • These nodes must have at least 5 GB of free disk space:

    • Primary IaaS Website

    • Microsoft SQL database

    • Model Manager

  • The primary IaaS Website node where the Model Manager data is installed must have JAVA SE Runtime Environment 8, 64 bits, update 161 or later installed. After you install Java, you must set the JAVA_HOME environment variable to the new version.

  • To download and run the upgrade, you must have the following resources:

    • At least 5 GB on the root partition

    • 5 GB on the /storage/db partition for the master vRealize Automation appliance

    • 5 GB on the root partition for each replica virtual appliance

  • Check the /storage/log subfolder and remove any older archived ZIP files to clean up space.

General Prerequisites

Verify that the following prerequisites are finished before you begin an upgrade.

  • You must install PowerShell 3.0 or above on your Windows IaaS systems before upgrading. The upgrade fails if PowerShell 3.0 or above is not installed.

  • Perform an IISRESET on your IaaS Web and Manager Service machines if Microsoft IIS is installed. Performing the IISRESET verifies that there is not an IIS dependant service disabled in startup mode.

  • If you use the DynamicTypes plugin, export the vRealize Orchestrator DynamicTypes plug-in configuration as a package.

    1. Log in to the Java Client as an administrator user.

    2. Select the Workflows tab.

    3. Select Library > Dynamic Types > Configuration.

    4. Select the Export Configuration as Package workflow and run it.

    5. Click Not Set > Insert value.

    6. Select the namespaces you want to export and click Add to add them to the package.

    7. Click Submit to export the package.

  • You have access to all databases and all load balancers impacted by or participating in the vRealize Automation upgrade.

  • You make the system unavailable to users while you perform the upgrade.

  • You disable any applications that query vRealize Automation.

  • Verify that Microsoft Distributed Transaction Coordinator (MSDTC) is enabled on all vRealize Automation and associated SQL servers. For instructions, see Knowledge Base article 2089503.

  • Complete these steps if you are upgrading a distributed environment configured with an embedded PostgreSQL database.

    1. Examine the files in the pgdata directory on the master host before you upgrade the replica hosts.

    2. Navigate to the PostgreSQL data folder on the master host at /var/vmware/vpostgres/current/pgdata/.

    3. Close any opened files in the pgdata directory and remove any files with a .swp suffix.

    4. Verify that all files in this directory have correct ownership: postgres:users.

In addition, verify that custom properties do not have spaces in their names. Before upgrading to this release of vRealize Automation, remove any space characters from your custom property names, for example replace the space with an underscore character, to allow the custom property to be recognized in the upgraded vRealize Automation installation. vRealize Automation custom property names cannot contain spaces. This issue can impact use of an upgraded vRealize Orchestrator installation that uses custom properties that contained spaces in earlier releases of either vRealize Automation or vRealize Orchestrator or both.