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
Prerequisites
n
Verify the successful update of all vRealize Automation appliances.
n
If you reboot an IaaS server after you update all the vRealize Automation appliances, you must stop
the IaaS Windows services. Before you upgrade the IaaS components, stop all the IaaS Windows
services, except for the Management Agent service, on the server.
n
Before you run the upgrade shell script on the master or primary vRealize Automation appliance
node, verify that each service is REGISTERED.
a Go to the appliance management console for your virtual appliance by using its fully qualified
domain name: https://va-hostname.domain.name:5480.
b Log in with the user name root and the password you entered when the appliance was
deployed.
c Click Services.
d Verify that each service, except the iaas-service, is REGISTERED.
n
Upgrade the Management Agent on each vRealize Automation IaaS virtual machine.
a Open a browser and navigate to the VMware vRealize Automation IaaS Installation page on
thevRealize Automation appliance using the fully qualified domain name:
https://virtual_appliance_host:5480/installer.
b Click Management Agent Installer.
By default, the installer is downloaded to the Downloads folder.
c Log in to each vRealize Automation IaaS virtual machine, upgrade the Management Agent with
the Management Agent Installer file.
n
Verify that your primary IaaS Website node where the Model Manager data is installed has JAVA SE
Runtime Environment 8, 64 bits, update 161 or later installed. After you install Java, you must set the
environment variable, JAVA_HOME, to the new version.
n
Log in to each IaaS Website node and verify that the creation date is earlier than the modified date in
the web.config file. If the creation date for the web.config file is the same as or later than the
modified date, perform the procedure in Upgrade Fails for IaaS Website Component.
n
To verify that each IaaS node has an upgraded IaaS Management Agent, perform these steps on
each IaaS node.
a Log in to the vRealize Automation appliance management console.
b Select vRA Settings > Cluster.
c Expand the list of all installed components on each IaaS node, and locate the IaaS Management
Agent.
d Verify that the Management Agent version is current.
n
Verify that the IaaS Microsoft SQL Server database backup is accessible in case you must roll back.
Upgrading from vRealize Automation 6.2.5 to 7.4
VMware, Inc. 46