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
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.
Considerations About Upgrading to This
vRealize Automation Version
vRealize Automation 7 and later introduces various functional changes during and after the upgrade
process. You should review changes before you upgrade your vRealize Automation 6.2.5 deployment to
the new version.
Review these considerations before you upgrade.
Upgrade and Identity Appliance Speciļ¬cations
During the vRealize Automation upgrade process, you answer prompts to upgrade the identity appliance.
The target deployment uses the VMware Identity Manager.
Upgrade and Licensing
During the upgrade, your existing vRealize Automation 6.2.5 licenses, and any vCloud Suite 6.x licenses
that you have, are removed. You must reenter your licenses in the vRealize Automation 7.4
vRealize Automation appliance management console.
You now use vRealize Automation licensing for virtual appliances and IaaS by entering license key
information in the vRealize Automation appliance. Licensing information is no longer available in the IaaS
user interface and IaaS no longer performs licensing checks. Endpoints and quotas are enforced through
the end-user license agreements (EULAs).
Note Write down your vCloud Suite 6.x license key if you used it for vRealize Automation 6.2.5 before
the upgrade. Upon upgrade, existing license keys are removed from the database.
For more information about reentering your license information during or after upgrade, see Update the
License Key.
Understanding How Roles Are Upgraded
When you upgrade vRealize Automation, your organization's existing role assignments are maintained.
The upgrade also creates some role assignments to support additional blueprint architect roles.
Upgrading from vRealize Automation 6.2.5 to 7.4
VMware, Inc. 9