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
5 Upgrade the primary vRealize Orchestrator node.
a Power on the node you selected to be the vRealize Orchestrator primary node.
b Log in as root to the vRealize Orchestrator Appliance management console at
hps://orchestrator_server:5480.
c Select Update > .
d Choose your download method and click Save .
e Click Status.
f Click Check Updates.
g Click Install Updates.
h Accept the VMware End User License Agreement.
i When the update nishes, restart the vRealize Orchestrator appliance.
6 Verify that the vco service appears as registered in the vRealize Orchestrator Appliance management
console.
7 On the vRealize Orchestrator Control Center, click the Validate Conguration icon and verify that the
conguration is valid.
8 On the vRealize Orchestrator Control Center, upgrade the vRealize Automation default plugins, which
include the NSX plugin.
9 Log in as root to the vRealize Orchestrator Control Center on the primary vRealize Orchestrator node
at hps://your_orchestrator_server_IP_or_DNS_name:8283/vcocontrolcenter.
10 Click the Manage Plugins icon.
11 Select Browse > plug-in name > Install.
12 Deploy a new vRealize Orchestrator appliance for a new secondary vRealize Orchestrator node in this
cluster.
13 Set up the network conguration of the new secondary vRealize Orchestrator node to match the
secondary vRealize Orchestrator node in the old cluster.
14 Join the new secondary vRealize Orchestrator node to the primary vRealize Orchestrator node.
a Log in as root to the vRealize Orchestrator Control Center on the secondary vRealize Orchestrator
node at hps://your_orchestrator_server_IP_or_DNS_name:8283/vcocontrolcenter.
b Click the Orchestrator Cluster Management icon.
c Ensure that both vRealize Orchestrator servers are running.
d Click Join Node To Cluster and enter the primary vRealize Orchestrator node details.
e Click Join and wait for the new secondary vRealize Orchestrator node to complete the join cluster
operation.
f Verify that the new secondary vRealize Orchestrator node pending conguration ngerprint is the
same as the primary vRealize Orchestrator node.
g Restart the new secondary vRealize Orchestrator server service from Startup Options in the Control
Center.
h Verify that the new secondary vRealize Orchestrator node Applied Conguration Fingerprint is the
same as the primary vRealize Orchestrator node.
15 Repeat steps 13-15 for each secondary vRealize Orchestrator node in the old cluster.
Chapter 5 Updating vRealize Orchestrator After Upgrading from vRealize Automation 6.x to 7.2
VMware, Inc. 45