Before you run the upgrade, review the prerequisites.

System Configuration Requirements

Make sure the following system requirements are met before you begin an upgrade.

  • Verify that you are following a supported upgrade path. See the vRealize Automation release notes for a list of supported upgrade paths.

  • Verify that all appliances and servers that are part of your deployment meet the system requirements for the version you are upgrading to. See the vRealize Automation Support Matrix on the VMware Web site at https://www.vmware.com/support/pubs/vcac-pubs.html.

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

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

  • Record your vCloud Suite license key if you used it for your the vRealize Automation installation you are upgrading from. Upon upgrade, existing license keys are removed from the database.

Hardware Configuration Requirements

Make sure the following hardware requirements are met before you begin an upgrade.

  • You must create a disk with at least 50 GB of space and 18 GB of RAM space before you download the upgrade. See Increase vCenter Server Hardware Resources for Upgrade.

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

    If you have two disks in your vRealize Automation appliance, you must add a Disk 3 with 25 GB and a Disk 4 with 50 GB of space. The virtual appliance must have Disk 3 and Disk 4 for the upgrade process to succeed.

  • To avoid upgrade failures due to insufficient free space in future vRealize Automation upgrades, Disk 1 must be re-sized to 50 GB on all vRealize Automation appliances. See "Re-size Disk 1 for Upgrade" on page 19.

  • Your CPU must have four virtual sockets and one core. See Increase vCenter Server Hardware Resources for Upgrade.

  • Your IaaS Server nodes must have the Microsoft .NET Framework 4.5.2 version and at least 5 GB of free disk space.

  • You must have at least 7 GB of free disk space on each vRealize Automation appliance of the root partition to download and run the upgrade.

  • Check the /storage/log subfolder and remove any older archived zip files to cleanup space.

General Prerequisites

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

  • You have access to an Active Directory account that has a username@domain format with permissions to bind to the directory.

    Note:

    Identity Provider from OpenLDAP is not migrated when you upgrade from vRealize Automation 6.2.x versions.

  • You have access to an account that has a SAMaccountName format with sufficient privileges to join the system to the domain by creating a computer object dynamically or to merge into a pre-created object.

  • 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 have disabled any applications that query vRealize Automation.

  • You have followed the instructions in Shut Down vCloud Automation Center Services on Your IaaS Windows Server.

  • Verify that Microsoft Distributed Transaction Coordinator (MSDTC) is enabled on all vRealize Automation and associated SQL servers. For instructions, see the VMware Knowledge Base article Various tasks fail after upgrading or migrating to VMware vCloud Automation Center (vCAC) 6.1.x (2089503) at http://kb.vmware.com/kb/2089503.

  • If your site uses an external vRealize Orchestrator appliance, and your deployment uses an external vRealize Orchestrator appliance that is connected to the Identity Appliance, upgrade vRealize Orchestrator before you upgrade vRealize Automation.

  • If the Common Components Catalog is installed, you must uninstall it before you upgrade. For information about how to uninstall, install, and upgrade the Common Components Catalog, see the Common Components Catalog documentation.