7.4
Table Of Contents
- Upgrading from vRealize Automation 7.1 or Later to 7.4
- Contents
- Upgrading vRealize Automation 7.1, 7.2, or 7.3.x to 7.4
- 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 for Upgrading vRealize Automation
- Upgrading Software Agents to TLS 1.2
- 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 from 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 to vRealize Automation Fails
- Unable to Update DEM and DEO Components
- Update Fails to Upgrade the Management Agent
- Management Agent Upgrade is Unsuccessful
- vRealize Automation Update Fails Because of Default Timeout Settings
- Upgrading IaaS in a High Availability Environment Fails
- Work Around Upgrade Problems
Troubleshooting the
vRealize Automation Upgrade 9
The upgrade troubleshooting topics provide solutions to problems that you might encounter when
upgrading vRealize Automation from 7.1, 7.2, or 7.3.x to 7.4.
This chapter includes the following topics:
n
Automatic Manager Service Failover Does Not Activate
n
Installation or Upgrade Fails with a Load Balancer Timeout Error
n
Upgrade Fails for IaaS Website Component
n
Manager Service Fails to Run Due to SSL Validation Errors During Runtime
n
Log In Fails After Upgrade
n
Delete Orphaned Nodes on vRealize Automation
n
Join Cluster Command Appears to Fail After Upgrading a High-Availability Environment
n
PostgreSQL Database Upgrade Merge Does Not Succeed
n
Replica vRealize Automation Appliance Fails to Update
n
Backup Copies of .xml Files Cause the System to Time Out
n
Exclude Management Agents from Upgrade
n
Unable to Create New Directory in vRealize Automation
n
vRealize Automation Replica Virtual Appliance Update Times Out
n
Some Virtual Machines Do Not Have a Deployment Created During Upgrade
n
Certificate Not Trusted Error
n
Installing or Upgrading to vRealize Automation Fails
n
Unable to Update DEM and DEO Components
n
Update Fails to Upgrade the Management Agent
n
Management Agent Upgrade is Unsuccessful
n
vRealize Automation Update Fails Because of Default Timeout Settings
n
Upgrading IaaS in a High Availability Environment Fails
VMware, Inc.
60