7.2

n
Verify that the vRealize Automation you are upgrading from is in stable working condition. Correct any
problems before upgrading.
n
If you are upgrading from vRealize Automation 6.2.x, record the vCloud Suite license key you used for
your current vRealize Automation environment. Upon upgrade, existing license keys are removed from
the database. You do not need to record the license if you are upgrading from vRealize Automation 7.x.
Hardware Configuration Requirements
Verify the following system requirements are met before you begin an upgrade.
n
You must congure your current hardware before you download the upgrade. See “Increase vCenter
Server Hardware Resources for vRealize Automation 6.2.4 or 6.2.5,” on page 19.
n
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 VMware vCloud
®
Networking and Security ™ 5.5.x (vCNS) ended in
September 2016, the VCNS custom properties continue to be valid for VMware NSX ™ purposes. See
the VMware Knowledge Base article End of Availability and End of General Support for VMware vCloud
Networking and Security 5.5.x (2144733) at hp://kb.vmware.com/kb/2144733 for more information.
n
Your primary IaaS Web site, Microsoft SQL database, and Model Manager node must have the
Microsoft .NET Framework 4.5.2 version and at least 5 GB of free disk space.
n
Your primary IaaS Web site, Microsoft SQL database, and Model Manager node must have JAVA SE
Runtime Environment 8, 64bits, update 91 or higher installed. After you install Java, you must set the
environment variable, JAVA_HOME, to the new version on each server node.
n
You must have at least 5.3 GB of free disk space on the root partition of each vRealize Automation
appliance to download and run the upgrade.
n
Check the /storage/log subfolder and remove any older archived ZIP les to clean up space.
General Prerequisites
Verify the following system requirements are met before you begin an upgrade.
n
You have access to an Active Directory account with a username@domain format and permissions to
bind to the directory.
n
You have access to an account with a SAMaccountName format and sucient privileges to join the
system to the domain by creating a computer object dynamically or to merge into a pre-created object.
n
You have access to all databases and all load balancers impacted by or participating in the
vRealize Automation upgrade.
n
You make the system unavailable to users while you perform the upgrade.
n
You disable any applications that query vRealize Automation.
n
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 hp://kb.vmware.com/kb/2089503.
n
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.
Upgrading from vRealize Automation 6.2.4 or 6.2.5 to 7.2
8 VMware, Inc.