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
n
Verify that Microsoft Distributed Transaction Coordinator (MSDTC) is enabled on all
vRealize Automation and associated SQL servers. For instructions, see Knowledge Base article
2089503.
n
Complete these steps if you are upgrading a distributed environment configured with an embedded
PostgreSQL database.
a Examine the files in the pgdata directory on the master host before you upgrade the replica
hosts.
b Navigate to the PostgreSQL data folder on the master host
at /var/vmware/vpostgres/current/pgdata/.
c Close any opened files in the pgdata directory and remove any files with a .swp suffix.
d Verify that all files in this directory have correct ownership: postgres:users.
In addition, verify that custom properties do not have spaces in their names. Before upgrading to this
release of vRealize Automation, remove any space characters from your custom property names, for
example replace the space with an underscore character, to allow the custom property to be recognized
in the upgraded vRealize Automation installation. vRealize Automation custom property names cannot
contain spaces. This issue can impact use of an upgraded vRealize Orchestrator installation that uses
custom properties that contained spaces in earlier releases of either vRealize Automation or vRealize
Orchestrator or both.
Checklist for Upgrading vRealize Automation
When you upgrade your vRealize Automation 7.1, 7.2 environment to 7.3 or your 7.1, 7.2, 7.3
environment to 7.3.1, you update all components in a specific order.
The order of upgrade varies depending on whether you are upgrading a minimal environment or a
distributed environment with multiple vRealize Automation appliances.
Use the checklists to track your work as you complete the upgrade. Finish the tasks in the order they are
given.
Table 1‑1. Checklist for Upgrading a vRealize Automation Minimal Environment
Task Instructions
Run NSX Network and Security Inventory Data Collection
Before You Upgrade from vRealize Automation 7.1 or 7.2 to
7.3.x. This is only required when vRealize Automation is
integrated with NSX.
See Run NSX Network and Security Inventory Data Collection
Before You Upgrade vRealize Automation.
Backup your current installation. This is a critical step.
For more information on how to back up and restore your
system, see Back Up Your Existing vRealize Automation
Environment.
For general information, see Configuring Backup and Restore by
Using Symantec Netbackup at
http://www.vmware.com/pdf/vrealize-backup-and-restore-
netbackup.pdf.
Upgrading from vRealize Automation 7.1, 7.2 to 7.3 or 7.1, 7.2, 7.3 to 7.3.1
VMware, Inc. 9