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
c Open server.xml.
d If necessary, edit the server.xml le entry jdbc:posgresql that points to the Postgres database and
point it to the external IP address of the master PostgreSQL node for external PostgreSQL or master
virtual appliance for embedded PostgreSQL.
For example, jdbc:postgresql://198.15.100.60:5432/vcac
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.
Procedure
1 Open the vRealize Automation appliance management console for the upgrade.
a Go to the management console for your virtual appliance by using its fully qualied domain name,
hps://va-hostname.domain.name:5480.
b Log in with the user name root and the password you specied when the appliance was deployed.
c Click the Update tab.
2 Click .
3 Select to download the updates from a VMware repository or CDROM in the Update Repository
section.
4 Click Status.
5 Click Check Updates to verify that an update is accessible.
6 Click Install Updates.
7 Click OK.
A message stating that the update is in progress appears.
8 (Optional) If you have not resized Disk 1 to 50 GB manually, perform the following steps.
a When the system prompts you to reboot the virtual appliance, click the System tab and click
Reboot.
During the reboot, the system adjusts the space required for the update.
b After the system reboots, log in again to the vRealize Automation appliance management console
and select Update > Status.
c Click Check Updates and Install Updates.
9 Open the log les to verify that upgrade is progressing successfully.
/opt/vmware/var/log/vami/vami.log and /var/log/vmware/horizon/horizon.log
If you log out during the upgrade process and log in, you can continue to follow the progress of the
update in the log le /opt/vmware/var/log/vami/updatecli.log.
The time it takes for the update to nish depends on your site environment.
10 When the update is nished, log out of the vRealize Automation appliance, clear the cache of your Web
browser, and log in to the vRealize Automation appliance management console.
11 Reboot the virtual appliance.
a Click System.
b Click Reboot and conrm your selection.
Upgrading from vRealize Automation 6.2.x to 7.1
VMware, Inc. 29