7.2
Table Of Contents
- Upgrading from vRealize Automation 6.2.4 or 6.2.5 to 7.2
- Contents
- Updated Information
- vRealize Automation 6.2.4 or 6.2.5 Prerequisites, Considerations, and Process
- Prerequisites for Upgrading from vRealize Automation 6.2.4 or 6.2.5
- 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
- Checklist for Upgrading vRealize Automation 6.2.4 or 6.2.5
- Preparing to Upgrade vRealize Automation 6.2.4 or 6.2.5
- Updating the vRealize Automation 6.2.4 or 6.2.5 Appliance
- Upgrading the IaaS Server Components After Upgrading vRealize Automation 6.x to 7.2
- Updating vRealize Orchestrator After Upgrading from vRealize Automation 6.x to 7.2
- Add Users or Groups to an Active Directory Connection
- Enable Your Load Balancers
- Post-Upgrade Tasks for Upgrading vRealize Automation 6.2.4 or 6.2.5
- Port Configuration for High-Availability Deployments
- Enabling the Connect to Remote Console Action for Consumers
- Restore External Workflow Timeout Files
- Verify That vRealize Orchestrator Service Is Available
- Restore Embedded vRealize Orchestrator Endpoint
- Restore Changes to Logging in the app.config File
- Troubleshooting the vRealize Automation 6.2.4 or 6.2.5 Upgrade
- Migration of Identity Store Fails Because the Active Directory is not Synchronized
- 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 IaaS Website Component
- 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
- User Migration Batch Files Are Ineffective
- PostgreSQL External Database Merge Is Unsuccessful
- Join Cluster Command Appears to Fail After Upgrading a High-Availability Environment
- Upgrade Is Unsuccessful if Root Partition Does Not Provide Sufficient Free Space
- Backup Copies of .xml Files Cause the System to Time Out
- Delete Orphaned Nodes on vRealize Automation
- Upgrade Fails to Upgrade the Management Agent or Certificate Not Installed on a IaaS Node
- Unable to Create New Directory in vRealize Automation
- Index
Preparing to Upgrade
vRealize Automation 6.2.4 or 6.2.5 2
You must perform various tasks and procedures before you upgrade vRealize Automation.
Perform the tasks in the order they appear in the checklist. See “Checklist for Upgrading vRealize
Automation 6.2.4 or 6.2.5,” on page 13.
This chapter includes the following topics:
n
“Backup Prerequisites for Upgrading vRealize Automation 6.2.4 or 6.2.5,” on page 17
n
“Shut Down vCloud Automation Center Services on Your IaaS Windows Server,” on page 21
n
“Downloading vRealize Automation Appliance Updates,” on page 22
Backup Prerequisites for Upgrading vRealize Automation 6.2.4 or
6.2.5
Complete the backup prerequisites before you begin your upgrade.
Prerequisites
n
Verify that your source installation is fully installed and congured.
n
Log in to your vSphere Client and for each appliance in your source environment, backup all the
vRealize Automation appliance conguration les in the following directories .
n
/etc/vcac/
n
/etc/vco/
n
/etc/apache2/
n
/etc/rabbitmq/
n
Backup the vRealize Automation external workow conguration (xmldb) les on your system. Store
the backup les in a temporary directory. These les are located
at \VMware\vCA\Server\ExternalWorkflows\xmldb\. You restore the xmldb les on your new system
after migration. See “Restore External Workow Timeout Files,” on page 51.
For a related issue, see “Backup Copies of .xml Files Cause the System to Time Out,” on page 64.
n
Backup the vRealize Automation PostgreSQL database on the master vRealize Automation appliance.
a Log in to the master vRealize Automation appliance management console.
b Select vRA > Database.
c Note the vRealize Automation PostgreSQL database seings.
d Back up the PostgreSQL database. For information about PostgreSQL database backup, see
hps://www.postgresql.org/.
VMware, Inc.
17