7.4
Table Of Contents
- Upgrading from vRealize Automation 6.2.5 to 7.4
- Contents
- Upgrading vRealize Automation 6.2.5 to 7.4
- Prerequisites for Upgrading vRealize Automation
- Considerations About Upgrading to This vRealize Automation Version
- Upgrade and Identity Appliance Specifications
- Upgrade and Licensing
- Understanding How Roles Are Upgraded
- Understanding How Blueprints Are Upgraded
- Upgrade and vApp Blueprints, vCloud Endpoints, and vCloud Reservations
- Understanding How Multi-Machine Blueprints Are Upgraded
- Upgrade and Physical Endpoints, Reservations, and Blueprints
- Upgrade and Network Profile Settings
- Upgrade and Entitled Actions
- Upgrade and Custom Properties
- Upgrade and Application Services
- Upgrade and Advanced Service Design
- Upgrade and Blueprint Price Information
- Upgrade and Catalog Items
- Checklist for Upgrading vRealize Automation
- vRealize Automation Environment User Interfaces
- Upgrading VMware Products Integrated with vRealize Automation
- Preparing to Upgrade vRealize Automation
- Updating the vRealize Automation Appliance
- Upgrading the IaaS Server Components After Upgrading vRealize Automation
- Upgrading vRealize Orchestrator After Upgrading vRealize Automation
- Add Users or Groups to an Active Directory Connection
- Enable Your Load Balancers
- Post-Upgrade Tasks for Upgrading vRealize Automation
- Port Configuration for High-Availability Deployments
- Reconfigure Built-In vRealize Orchestrator for High Availability
- Enabling the Connect to Remote Console Action for Consumers
- Restore External Workflow Timeout Files
- Verify That vRealize Orchestrator Service Is Available
- Reconfigure Embedded vRealize Orchestrator Endpoint
- Restore Changes to Logging in the app.config File
- Enable Automatic Manager Service Failover After Upgrade
- Run Test Connection and Verify Upgraded Endpoints
- Troubleshooting the vRealize Automation Upgrade
- 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
- Catalog Items Appear in the Service Catalog After Upgrade But Are Not Available to Request
- PostgreSQL External Database Merge Is Unsuccessful
- Join Cluster Command Appears to Fail After Upgrading a High-Availability Environment
- Upgrade Is Unsuccessful if Root Partition Does Not Provide Sufficient Free Space
- Backup Copies of .xml Files Cause the System to Time Out
- Delete Orphaned Nodes on vRealize Automation
- Unable to Create New Directory in vRealize Automation
- Some Virtual Machines Do Not Have a Deployment Created During Upgrade
- Certificate Not Trusted Error
- Installing or Upgrading to vRealize Automation Fails
- 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
Require
d Value Description Credential Format Example Value
agent_pa
ssword
Password for an agent such as a vSphere
agent. Required for each node where an
agent component is installed.
Password
pa$$w0rd!
vidm_ad
min_pass
word
The VIDM administrator password.
Required only when you upgrade from
vRealize Automation 6.2.5.
vIDM_password
pa$$w0rd!
For security reasons, the upgrade.properties file is removed when you run the upgrade shell
script. The properties in the file are defined using the information for each IaaS component that
comes through the IaaS Management Agents. It is important that all IaaS Management Agents are
upgraded and healthy before running the ./generate_properies or ./upgrade_from_62x shell
scripts. If any IaaS Management Agent has a problem when you run the upgrade shell script, see
Update Fails to Upgrade the Management Agent. To recreate the upgrade.properties file, repeat
steps 2 and 3.
5 Run the upgrade script.
a At the command prompt, enter ./upgrade_from_62x.
b Press Enter.
The script displays each IaaS node and all the components installed on it. The script validates each
component before installing the upgrade. If there are incorrect values in the upgrade.properties
file, the script fails.
The first IaaS server component can take 30 minutes or longer to finish. During the upgrade, you see
a message similar to Upgrading server components for node web1-vra.mycompany.com.
If the upgrade shell script is unsuccessful, review the upgrade.log file.
You can run the upgrade script again after you fix a problem. Before you run the upgrade script again,
recreate the upgrade.properties file, open it, and enter all the required values.
6 (Optional) Enable automatic Manager Service failover. See Enable Automatic Manager Service
Failover After Upgrade.
What to do next
Restore Access to Built-In vRealize Orchestrator Control Center.
Upgrading IaaS Components Using the IaaS Installer
You can use this alternative method to upgrade IaaS components after upgrading vRealize Automation
from 6.2.5 to 7.4.
Download the IaaS Installer to Upgrade IaaS Components
After upgrading from vRealize Automation 6.2.5 to 7.4, download the IaaS installer to the virtual machine
where the IaaS components to be upgraded are installed.
Upgrading from vRealize Automation 6.2.5 to 7.4
VMware, Inc. 48