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
Guest agent and agent bootstrap code must be updated in the templates from vRealize Automation 7.1,
7.2, 7.3 or 7.3.1. If you are using a linked clone option, you might need to remap the templates with the
newly created virtual machines and their snapshots.
To upgrade your templates, you complete these tasks.
1 Log in to vSphere.
2 Convert each template from vRealize Automation 7.1, 7.2, 7.3 or 7.3.1 to a virtual machine and power
on the machine.
3 Import the appropriate software installer and run the software installer on each virtual machine.
4 Convert each virtual machine back to a template.
Use this procedure to locate the software installer for Linux or Windows.
Prerequisites
Successful upgrade to vRealize Automation 7.4.
Procedure
1 Start a browser and open the vRealize Automation 7.4 appliance splash page using the fully qualified
domain name of the virtual appliance: https://vra-va-hostname.domain.name.
2 Click Guest and software agents page.
3 Follow the instructions for the Linux or Windows software installer.
What to do next
Identify Virtual Machines that Need Software Agent Upgrade.
Identify Virtual Machines that Need Software Agent Upgrade
You can use the Health Service in vRealize Automation to identify virtual machines that need a Software
Agent update to TLS 1.2.
You can use the Health Service to identify the virtual machines that need a Software Agent update to TLS
1.2. All Software Agents in the vRealize Automation 7.4 environment need to be updated so that you can
perform post-provisioning procedures, which require secure communication between your browser and
vRealize Automation.
Prerequisites
n
You have successfully upgraded to vRealize Automation 7.4.
n
You are logged in to vRealize Automation 7.4 on the primary virtual appliance as tenant administrator.
Procedure
1 Click Administration > Health.
2 Click New Configuration.
Upgrading from vRealize Automation 7.1 or Later to 7.4
VMware, Inc. 49