7.2
Table Of Contents
- Upgrading from vRealize Automation 7.1 to 7.2
- Contents
- Updated Information
- vRealize Automation 7.1 Upgrade Prerequisites and Process
- Preparing to Upgrade vRealize Automation 7.1
- Updating the vRealize Automation 7.1 Appliance
- Upgrading the IaaS Server Components After Upgrading vRealize Automation 7.1 to 7.2
- Updating vRealize Orchestrator After Upgrading from vRealize Automation 7.1 to 7.2
- Add Users or Groups to an Active Directory Connection
- Enable Your Load Balancers
- Post-Upgrade Tasks for Upgrading vRealize Automation 7.1
- Troubleshooting the vRealize Automation 7.1 Upgrade
- Installation or Upgrade Fails with a Load Balancer Timeout Error
- Upgrade Fails for IaaS Website Component
- Manager Service Fails to Run Due to SSL Validation Errors During Runtime
- Log In Fails After Upgrade
- Unable to Upgrade Management Agent
- Delete Orphaned Nodes on vRealize Automation
- Join Cluster Command Appears to Fail After Upgrading a High-Availability Environment
- PostgreSQL Database Upgrade Merge Does Not Succeed
- Management Agent Upgrade is Unsuccessful
- Upgrade Fails to Upgrade the Management Agent or Certificate Not Installed on a IaaS Node
- Replica vRealize Automation Appliance Fails to Update
- Backup Copies of .xml Files Cause the System to Time Out
- Exclude Management Agents from Upgrade
- Unable to Create New Directory in vRealize Automation
- Index
If you are performing a manual external Microsoft SQL database upgrade, you must upgrade the
external SQL before you upgrade the Web node. You can upgrade the external SQL remotely from the
Web node.
2 Manager Services
Upgrade the active Manager Service before you upgrade the passive Manager Service.
If you do not have SSL encryption enabled in your SQL instance, uncheck the SSL encryption checkbox
in the Iaas Upgrade conguration dialog box next to the SQL denition.
3 DEM orchestrator and workers
Upgrade all DEM orchestrators and workers. Finish the upgrade on one server before you upgrade the
next server.
4 Agents
Finish the upgrade on one server before you upgrade the next server that is running an agent.
5 Management Agent
Is updated automatically as part of the upgrade process.
If you are using dierent services on one server, the upgrade updates the services in the proper order. For
example, if your site has Web site and manager services on the same server, select both for update. The
upgrade installer applies the updates in the proper order. You must complete the upgrade on one server
before you begin an upgrade on another.
N If your deployment uses a load balancer, the primary appliance must be connected to the load
balancer. All other instances of vRealize Automation appliance appliances must be disabled for load
balancer trac before you apply the upgrade to avoid caching errors.
Prerequisites
n
Back up your existing vRealize Automation environment.
n
If you reboot an IaaS server after you update all the vRealize Automation appliances but before you
upgrade the IaaS components , stop all of the IaaS windows services, except for the Management Agent
service, on the server.
n
“Download the IaaS Installer to Upgrade IaaS Components After Upgrading vRealize Automation 7.1
to 7.2,” on page 22.
n
Verify that your primary IaaS Website, Microsoft SQL database, and Model Manager node has JAVA SE
Runtime Environment 8, 64bits, update 91 or later installed. After you install Java, you must set the
environment variable, JAVA_HOME , to the new version on each server node.
n
Verify that the creation date is earlier than the modied date in the web.config le. If the creation date
for the web.config le is the same as or later than the modied date, perform the procedure in
“Upgrade Fails for IaaS Website Component,” on page 40.
n
If you have a Common Components Catalog component installed, you must uninstall the component
before you upgrade. For more information, see the Common Components Catalog Installation Guide or
follow the steps provided in Checklist for Upgrading from vRealize Automation.
Chapter 4 Upgrading the IaaS Server Components After Upgrading vRealize Automation 7.1 to 7.2
VMware, Inc. 23