7.2
Table Of Contents
- Upgrading from vRealize Automation 6.2.4 or 6.2.5 to 7.2
- Contents
- Updated Information
- vRealize Automation 6.2.4 or 6.2.5 Prerequisites, Considerations, and Process
- Prerequisites for Upgrading from vRealize Automation 6.2.4 or 6.2.5
- 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
- Checklist for Upgrading vRealize Automation 6.2.4 or 6.2.5
- Preparing to Upgrade vRealize Automation 6.2.4 or 6.2.5
- Updating the vRealize Automation 6.2.4 or 6.2.5 Appliance
- Upgrading the IaaS Server Components After Upgrading vRealize Automation 6.x to 7.2
- Updating vRealize Orchestrator After Upgrading from vRealize Automation 6.x to 7.2
- Add Users or Groups to an Active Directory Connection
- Enable Your Load Balancers
- Post-Upgrade Tasks for Upgrading vRealize Automation 6.2.4 or 6.2.5
- Port Configuration for High-Availability Deployments
- Enabling the Connect to Remote Console Action for Consumers
- Restore External Workflow Timeout Files
- Verify That vRealize Orchestrator Service Is Available
- Restore Embedded vRealize Orchestrator Endpoint
- Restore Changes to Logging in the app.config File
- Troubleshooting the vRealize Automation 6.2.4 or 6.2.5 Upgrade
- Migration of Identity Store Fails Because the Active Directory is not Synchronized
- 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 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 But Are Not Available to Request
- User Migration Batch Files Are Ineffective
- 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
- Upgrade Fails to Upgrade the Management Agent or Certificate Not Installed on a IaaS Node
- Unable to Create New Directory in vRealize Automation
- Index
Upgrade and Physical Endpoints, Reservations, and Blueprints
You cannot upgrade a deployment that contains physical endpoints. The presence of endpoints of type
physical prevents the vRealize Automation upgrade process from completing.
When upgrade encounters a physical endpoint in the source deployment, upgrade fails on the master
virtual appliance and reports a message in the user interface and log. You can determine if your source
deployment contains physical endpoints by logging in to vRealize Automation with Iaas Administrator
privileges, selecting Infrastructure > Endponts and noting the platform type value in the endpoints list. If
the list contains endpoints of Platform Type Physical, upgrade is not supported.
Physical endpoints, reservations, and machine components in blueprints are not supported in the target
vRealize Automation deployment.
Upgrade and Network Profile Settings
Private network proles are not supported in the target deployment and are ignored during the upgrade.
Routed network proles with associated PLR edge seings are also not supported in the target deployment
and are also ignored during the upgrade.
The private network prole type is not supported in the target vRealize Automation deployment. When the
vRealize Automation upgrade executable encounters a private network prole in the source deployment, it
ignores the network prole. Load balancers that reference those private networks are also ignored during
upgrade. The same upgrade conditions are true for a routed network prole with associated PLR edge
seings. Neither network prole conguration is upgraded.
If a reservation contains a private network prole, the private network prole seing is ignored during
upgrade and the reservation is upgraded as disabled in the target deployment.
If a reservation contains a routed network prole with associated PLR edge seings, the routed network
prole specication is ignored during upgrade and the reservation is upgraded as disabled in the target
deployment.
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.
Upgrading from vRealize Automation 6.2.4 or 6.2.5 to 7.2
12 VMware, Inc.