7.3
Table Of Contents
- Upgrading from vRealize Automation 7.1, 7.2 to 7.3 or 7.1, 7.2, 7.3 to 7.3.1
- Contents
- Updated Information
- Upgrading vRealize Automation 7.1, 7.2 to 7.3 or 7.1, 7.2 ,7.3 to 7.3.1
- Upgrading VMware Products Integrated with vRealize Automation
- Preparing to Upgrade vRealize Automation
- Run NSX Network and Security Inventory Data Collection Before You Upgrade vRealize Automation
- Backup Prerequisites for Upgrading vRealize Automation
- Back Up Your Existing vRealize Automation Environment
- Set the vRealize Automation PostgreSQL Replication Mode to Asynchronous
- Downloading vRealize Automation Appliance Updates
- Updating the vRealize Automation Appliance and IaaS Components
- Upgrading the IaaS Server Components Separately If the Update Process Fails
- Upgrading vRealize Orchestrator After Upgrading vRealize Automation
- Enable Your Load Balancers
- Post-Upgrade Tasks
- Set the vRealize Automation PostgreSQL Replication Mode to Synchronous
- Run Test Connection and Verify Upgraded Endpoints
- Run NSX Network and Security Inventory Data Collection After You Upgrade vRealize Automation
- Join Replica Appliance to Cluster
- Port Configuration for High-Availability Deployments
- Reconfigure Built-In vRealize Orchestrator for High Availability
- Restore External Workflow Timeout Files
- Enabling the Connect to Remote Console Action for Consumers
- Restore Changes to Logging in the app.config File
- Enable Automatic Manager Service Failover After Upgrade
- Troubleshooting the vRealize Automation Upgrade
- Automatic Manager Service Failover Does Not Activate
- 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
- 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
- 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
- vRealize Automation Replica Virtual Appliance Update Times Out
- Some Virtual Machines Do Not Have a Deployment Created During Upgrade
- Certificate Not Trusted Error
- Installing or Upgrading vRealize Automation Fails
- Unable to Update DEM and DEO Components
- Update Fails to Upgrade the Management Agent
- Management Agent Upgrade is Unsuccessful
- Empty Deployments Are Seen in vRealize Automation After Upgrade
- After Rebooting the Virtual Appliance, Automatic IaaS Upgrade Fails and Displays Pending Reboot Error
- IaaS Repository Application Fails
- Upgrading IaaS in a High Availability Environment Fails
9 Select the vco services of the external Orchestrator server and click Unregister.
What to do next
n
Import any certificates that were trusted in the external Orchestrator server to the trust store of the
built-in Orchestrator.
n
Join the vRealize Automation replica nodes to the vRealize Automation cluster to synchronize the
Orchestrator configuration.
For more information, see Reconfigure the Target Embedded vRealize Orchestrator to Support High
Availability in Installing or Upgrading vRealize Automation.
Note The vRealize Orchestrator instances are automatically clustered and available for use.
n
Restart the vco-configurator service on all nodes in the cluster.
n
Update the vRealize Orchestrator endpoint to point to the migrated built-in Orchestrator server.
n
Add the vRealize Automation host and the IaaS host to the inventory of the vRealize Automation
plug-in, by running the Add a vRA host and Add the IaaS host of a vRA host workflows.
Upgrading a Stand-Alone vRealize Orchestrator
Appliance for vRealize Automation
If you maintain a stand-alone, external instance of vRealize Orchestrator for vRealize Automation, you
must upgrade vRealize Orchestrator when you upgrade vRealize Automation from 7.1, 7.2 to 7.3 or 7.1,
7.2, 7.3 to 7.3.1.
Embedded instances of vRealize Orchestrator are upgraded as part of the vRealize Automation appliance
upgrade. No additional action is required for an embedded instance.
If you are upgrading a vRealize Orchestrator appliance cluster, see Upgrade a vRealize Orchestrator
Appliance Cluster for Use with vRealize Automation 7.3.
Prerequisites
n
Install the Update on the vRealize Automation Appliance and IaaS Components.
n
Unmount all network file systems. See vSphere Virtual Machine Administration in the vSphere
documentation.
n
Increase the memory of the vSphere Orchestrator appliance to at least 6 GB. See vSphere Virtual
Machine Administration in the vSphere documentation.
n
Take a snapshot of the vSphere Orchestrator virtual machine. See vSphere Virtual Machine
Administration in the vSphere documentation.
n
If you use an external database, back up the database.
n
If you use the preconfigured PostgreSQL database in vSphere Orchestrator, back up the database by
using the Export Database menu in the vSphere Control Center.
Upgrading from vRealize Automation 7.1, 7.2 to 7.3 or 7.1, 7.2, 7.3 to 7.3.1
VMware, Inc. 38