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
The private network profile type is not supported in vRealize Automation 7 and later. When the
vRealize Automation upgrade process finds a private network profile in the source deployment, it ignores
the network profile. Load balancers that reference those private networks are also ignored during
upgrade. The same upgrade conditions are true for a routed network profile with associated PLR edge
settings. Neither network profile configuration is upgraded.
If a reservation contains a private network profile, the private network profile setting is ignored during
upgrade. The reservation is upgraded as disabled in the target deployment.
If a reservation contains a routed network profile with associated PLR edge settings, the routed network
profile specification is ignored during upgrade. The reservation is upgraded as disabled in the target
deployment.
For information about upgrading a multi-machine blueprint that contains network settings, see
Understanding How Multi-Machine Blueprints Are Upgraded.
Upgrade and Entitled Actions
You cannot upgrade virtual machine actions.
The actions that you can perform on provisioned virtual machines, based on blueprint specifications, are
not upgraded. To recreate the actions you can perform on a virtual machine, customize the entitlements
for blueprints to enable only certain actions.
For related information, see Actions in Entitlements in Configuring 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 profiles that you created in the source deployment are upgraded as property groups. The
term build profile has been retired.
The term property set has been retired and CSV property set files are no longer available.
Case-sensitivity in Custom Property Names
Before 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. This ensures that property values do not override one another and that they match
property dictionary definitions. For example, a custom property hostname and another custom property
HOSTNAME are considered different custom properties by vRealize Automation 7.0 and later. The custom
property hostname and the custom property HOSTNAME do not override one another during upgrade.
Upgrading from vRealize Automation 6.2.5 to 7.4
VMware, Inc. 13