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
n
Improves the operational efficiency.
Note Consider using the external vRealize Orchestrator in the following cases:
n
Multiple tenants in the vRealize Automation environment
n
Geographically dispersed environment
n
Workload handling
n
Use of specific plug-ins, such as older versions of the Site Recovery Manager plug-in
Control Center Dierences Between External and Embedded
Orchestrator
Some of the menu items that are available in Control Center of an external vRealize Orchestrator are not
included in the default Control Center view of an embedded Orchestrator instance.
In Control Center of the embedded Orchestrator server, a few options are hidden by default.
Menu Item Details
Licensing The embedded Orchestrator is preconfigured to use vRealize Automation as a license provider.
Export/Import Configuration The embedded Orchestrator configuration is included in the exported vRealize Automation
components.
Configure Database The embedded Orchestrator uses the database that is used by vRealize Automation.
Customer Experience
Improvement Program
You can join the Customer Experience Improvement Program (CEIP) from the
vRealize Automation appliance management interface.
See The Customer Experience Improvement Program in Managing vRealize Automation.
Another options that are hidden from the default Control Center view are the Host address text box and
the UNREGISTER button on the Configure Authentication Provider page.
Note To see the full set of Control Center options in vRealize Orchestrator that is built into
vRealize Automation, you must access the advanced Orchestrator Management page at https://vra-va-
hostname.domain.name_or_load_balancer_address:8283/vco-controlcenter/#/?advanced and click the
F5 button on the keyboard to refresh the page.
Migrate an External vRealize Orchestrator 7.x to
vRealize Automation 7.4
You can export the configuration from your existing external Orchestrator instance and import it to the
Orchestrator server that is built into vRealize Automation.
Note If you have multiple vRealize Automation appliance nodes, perform the migration procedure only
on the primary vRealize Automation node.
Upgrading from vRealize Automation 7.1 or Later to 7.4
VMware, Inc. 35