7.1
Table Of Contents
- Upgrading from vRealize Automation 7.0 to 7.1
- Contents
- Updated Information
- Upgrading vRealize Automation
- Preparing to Upgrade vRealize Automation
- Updating the vRealize Automation Appliance
- Upgrading the IaaS Server Components
- Add Users or Groups to an Active Directory Connection
- Enable Your Load Balancers
- Post-Upgrade Tasks for vRealize Automation
- Troubleshooting the Upgrade
- Installation or Upgrade Fails with a Load Balancer Timeout Error
- Upgrade Fails for Website Component During IaaS Upgrade
- Manager Service Fails to Run Due to SSL Validation Errors During Runtime
- Log In Fails After Upgrade
- Catalog Items Appear in the Service Catalog But Are Not Available to Request
- Unable to Upgrade Management Agent
- IaaS Windows Services Fail to Stop
- PostgreSQL External Database Merge Is Unsuccessful
- Delete Orphaned Nodes on vRealize Automation 7.0
- Delete Orphaned Nodes on vRealize Automation 7.0.1
- Join Cluster Command Appears to Fail After Upgrading a High-Availability Environment
- Upgrade Is Unsuccessful if Root Partition Does Not Provide Sufficient Free Space
- Manual PostgreSQL Database Merge
- Management Agent Upgrade is Unsuccessful
- 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
Back Up Your Environment
Before you begin to upgrade, shut down and take a snapshot of the vRealize Automation IaaS Windows
Server, all Model Manager machines, and the identity virtual appliance machines. If the upgrade fails, you
can use the snapshot to return to the last known good conguration and aempt another upgrade.
Prerequisites
n
Beginning with vRealize Automation 7.0, the PostgreSQL database is always congured in high-
availability mode. Log in to the management console and select vRA > Database to locate the
current Master node. If the database table shows that the Master node is an external database, create a
manual backup of this external database. If the PostgreSQL database Master node is not external,
continue with the following procedure.
n
If the vRealize Automation Microsoft SQL database is not hosted on the IaaS server, create a database
backup le.
n
Verify that you have completed the backup prerequisites. See “Backing up and Saving Your Existing
Environment,” on page 11 .
n
Verify that you have taken a snapshot of your system while it is shut down. See the vSphere 6.0
Documentation.
If you cannot shut down your system, take an in-memory snapshot of all the nodes.
n
Verify that you have a backup of your entire system.
Procedure
1 Log in to vCenter Server.
2 Locate the vRealize Automation 7.0 IaaS Windows machines, and vRealize Automation appliance
nodes.
3 Select a machine and click Shutdown guest in the following order.
a IaaS Windows Server machines
b vRealize Automation appliance nodes
4 Take a snapshot of all the vRealize Automation 7.0 machines.
5 To create a full backup, clone each appliance node and perform the upgrade on the cloned machines.
Keep the original, in case system restore is required later on.
6 Power on the system.
For instructions, see the Start Up vRealize Automation topic at
hp://pubs.vmware.com/vrealize-
automation-71/topic/com.vmware.vrealize.automation.doc/GUID-4A4BD979-61EF-4590-
AEDF-6A9BA42426B6.html .
N If you have a high availability environment, use this procedure to power on your virtual
appliances.
a Power on the virtual appliance that you powered o last.
b Wait one minute.
c Power on the remaining virtual appliances.
7 Verify that the system is fully functional.
Upgrading from vRealize Automation 7.0 to 7.1
12 VMware, Inc.