7.1
Table Of Contents
- Upgrading from vRealize Automation 6.2 to 7.1
- Contents
- Upgrading to vRealize Automation 7.1
- Updated Information
- Upgrading vRealize Automation
- Checklist for Upgrading vRealize Automation Components
- 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 Cost Information
- Prerequisites for Upgrading vRealize Automation
- Preparing to Upgrade vRealize Automation
- Updating the vRealize Automation Appliance
- Upgrading the IaaS Server Components
- Upgrade Stand-Alone External vRealize Orchestrator for Use With vRealize Automation
- Upgrade External vRealize Orchestrator Appliance Clusters
- Add Users or Groups to an Active Directory Connection
- Enable Your Load Balancers
- Post-Upgrade Tasks for vRealize Automation
- Troubleshooting the Upgrade
- Migration of Identity Store Fails Because the Active Directory is...
- Migration of Identity Store Fails Because of Incorrect Credentials
- Migration of Identity Store Fails With a Timeout Error Message...
- Installation or Upgrade Fails with a Load Balancer Timeout Error...
- Upgrade Fails for Website Component During IaaS Upgrade
- Incorrect Tab Names Appear Intermittently
- Manager Service Fails to Run Due to SSL Validation Errors...
- Log In Fails After Upgrade
- Catalog Items Appear in the Service Catalog But Are Not...
- User Migration Batch Files Are Ineffective
- PostgreSQL External Database Merge is Unsuccessful
- Join Cluster Command Appears to Fail After Upgrading a High Availability Environment
- Increase Free Space on the Root Partition
- Manual PostgreSQL Database Merge
- Upgrade Fails to Upgrade the Management Agent or Certificate Not Installed on a IaaS Node
- Bad PostgreSQL Service State Stops Upgrade and Displays Error Message
- Backup Copies of .xml Files Cause the System to Time Out
- Index
For information about upgrading a multi-machine blueprint that contains network seings, see
“Understanding How Multi-Machine Blueprints Are Upgraded,” on page 11.
Upgrade and Entitled Actions
You cannot upgrade machine actions.
The actions that you are entitled to perform on provisioned machines, based on blueprint specications, are
not upgraded. To recreate allowed machine actions, customize the entitlements for blueprints to enable only
certain actions.
For related information, see Conguring vRealize Automation.
Upgrade and Custom Properties
All the custom properties that vRealize Automation supplies are available in the upgraded deployment.
Custom properties and property groups are upgraded.
Terminology and Related Changes
All the build proles that you created in the source deployment are upgraded as property groups. The term
build prole has been retired.
The term property set has been retired and CSV property set les are no longer available.
Case-sensitivity in Custom Property Names
Prior to vRealize Automation 7.0, custom property names were case-insensitive. In vRealize Automation 7.0
and later, custom property names are case-sensitive. During upgrade, custom property names must be an
exact match, including their case, to ensure that property values do not override one another and that they
correctly match property dictionary denitions. For example, a custom property expressed as hostname and
another custom property expressed as HOSTNAME are considered dierent custom properties by
vRealize Automation 7.0 and later and do not override one another during upgrade.
Reserved Property Names
Several keywords are now reserved and some upgraded properties might be impacted. Some keywords are
used by the blueprint code that can be imported, for example by using vRealize CloudClient blueprint
import functions. These keywords are considered reserved and are not available for properties that are
being upgraded. The keywords include but are not limited to cpu, storage, and memory.
Upgrade and Application Services
Application Services upgrade is not currently supported in the target vRealize Automation deployment.
Upgrade and Advanced Service Design
When you upgrade to the target vRealize Automation deployment, your Advanced Service Design items are
upgraded to XaaS elements.
XaaS components are available for use in the blueprint design canvas.
Upgrading from vRealize Automation 6.2.x to 7.1
VMware, Inc. 13