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
Upgrading the IaaS Server
Components After Upgrading
vRealize Automation 5
After you upgrade vRealize Automation from 6.2.5 to 7.4, a system administrator upgrades the IaaS
server components, including the Microsoft SQL Server database.
You have two options for upgrading the IaaS server components.
n
Use the automated IaaS upgrade shell script.
n
Use the vRealize Automation 7.4 IaaS installer executable file.
If you have a Common Components Catalog component installed, you must uninstall the component
before you upgrade. After you finish the upgrade, you can reinstall the component with the appropriate
version. For more information, see the Common Components Catalog Installation Guide. If this guide is
unavailable, use the alternative procedure in Checklist for Upgrading vRealize Automation.
This chapter includes the following topics:
n
Upgrade IaaS Components Using the Upgrade Shell Script
n
Upgrading IaaS Components Using the IaaS Installer
n
Restore Access to Built-In vRealize Orchestrator Control Center
Upgrade IaaS Components Using the Upgrade Shell Script
Use the upgrade shell script to upgrade the IaaS Components after you update each
vRealize Automation 6.2.5 appliance to 7.4.
The updated primary or master vRealize Automation appliance contains a shell script that you use to
upgrade each IaaS node and component.
You can run the upgrade script by using the vSphere console for the virtual machine or by using an SSH
console session. If you use the vSphere console, you avoid intermittent network connectivity problems
that can break the execution of the script.
If you stop the script while the script is upgrading a component, the script runs until the upgrade is
finished on the component. If any components on the node are not upgraded, you must run the script
again.
When the upgrade finishes, you can review the upgrade result by opening the upgrade log file
at /usr/lib/vcac/tools/upgrade/upgrade.log.
VMware, Inc.
45