7.1
Table Of Contents
- Upgrading from vRealize Automation 6.2 to 7.1
- Contents
- Upgrading to vRealize Automation 7.1
- Updated Information
- Upgrading vRealize Automation
- Checklist for Upgrading vRealize Automation Components
- Considerations About Upgrading to This vRealize Automation Version
- Upgrade and Identity Appliance Specifications
- Upgrade and Licensing
- Understanding How Roles Are Upgraded
- Understanding How Blueprints Are Upgraded
- Upgrade and vApp Blueprints, vCloud Endpoints, and vCloud Reservations
- Understanding How Multi-Machine Blueprints Are Upgraded
- Upgrade and Physical Endpoints, Reservations, and Blueprints
- Upgrade and Network Profile Settings
- Upgrade and Entitled Actions
- Upgrade and Custom Properties
- Upgrade and Application Services
- Upgrade and Advanced Service Design
- Upgrade and Blueprint Cost Information
- Prerequisites for Upgrading vRealize Automation
- Preparing to Upgrade vRealize Automation
- Updating the vRealize Automation Appliance
- Upgrading the IaaS Server Components
- Upgrade Stand-Alone External vRealize Orchestrator for Use With vRealize Automation
- Upgrade External vRealize Orchestrator Appliance Clusters
- Add Users or Groups to an Active Directory Connection
- Enable Your Load Balancers
- Post-Upgrade Tasks for vRealize Automation
- Troubleshooting the Upgrade
- Migration of Identity Store Fails Because the Active Directory is...
- Migration of Identity Store Fails Because of Incorrect Credentials
- Migration of Identity Store Fails With a Timeout Error Message...
- Installation or Upgrade Fails with a Load Balancer Timeout Error...
- Upgrade Fails for Website Component During IaaS Upgrade
- Incorrect Tab Names Appear Intermittently
- Manager Service Fails to Run Due to SSL Validation Errors...
- Log In Fails After Upgrade
- Catalog Items Appear in the Service Catalog But Are Not...
- User Migration Batch Files Are Ineffective
- PostgreSQL External Database Merge is Unsuccessful
- Join Cluster Command Appears to Fail After Upgrading a High Availability Environment
- Increase Free Space on the Root Partition
- Manual PostgreSQL Database Merge
- Upgrade Fails to Upgrade the Management Agent or Certificate Not Installed on a IaaS Node
- Bad PostgreSQL Service State Stops Upgrade and Displays Error Message
- Backup Copies of .xml Files Cause the System to Time Out
- Index
n
Your CPU must have four virtual sockets and one core. See “Increase vCenter Server Hardware
Resources for Upgrade,” on page 17.
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 8,
update 91, 64 bit, jdk-8u91-windows-x64.exe, 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 that the following prerequisites are nished 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 Identity Provider from OpenLDAP is not migrated when you upgrade from
vRealize Automation 6.2.x versions.
n
You have access to an account with a SAMaccountName format and sucient 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 hp://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.
n
If you are upgrading a distributed environment congured with an embedded PostgreSQL database,
examine the les in the pgdata directory on the master host before you upgrade the replica hosts.
Navigate to the PostgreSQL data folder on the master host at /var/vmware/vpostgres/current/pgdata/.
Close any opened les in the pgdata directory and remove any les with a .swp sux.
n
If you installed a Common Components Catalog component, you must uninstall it before you upgrade.
For information about how to uninstall, install, and upgrade Common Components Catalog
components, see the Common Components Catalog Installation Guide.
Preparing to Upgrade vRealize Automation
You must perform various listed tasks and procedures in preparation for upgrading vRealize Automation.
Perform the tasks required for upgrade in the order in which they appear in the checklist. See “Checklist for
Upgrading vRealize Automation Components,” on page 7.
Upgrading from vRealize Automation 6.2.x to 7.1
VMware, Inc. 15