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
Upgrade fails on the master virtual appliance if there is a vApp (vCloud) endpoint in the source
deployment. A message appears in the user interface and log. To determine if your source deployment
contains a vApp (vCloud) endpoint, log in to the vRealize Automation console as IaaS administrator user.
Select Infrastructure > Endponts. If the endpoints list contains vApp (vCloud) endpoints, you cannot
upgrade to this vRealize Automation version.
Managed vApps for vCloud Air or vCloud Director resources are not supported in the target
vRealize Automation environment.
Note The following approval policy types are deprecated. If they appear in the list of available approval
policy types after upgrade is finished, they are unusable.
n
Service Catalog - Catalog Item Request - vApp
n
Service Catalog - Catalog Item Request - vApp Component
You can create vCloud Air and vCloud Director endpoints and reservations in the target deployment. You
can also create blueprints with vCloud Air or vCloud Director virtual machine components.
Understanding How Multi-Machine Blueprints Are Upgraded
You can upgrade managed service, multi-machine blueprints from a supported vRealize Automation 6.2.x
version deployment.
When you upgrade a multi-machine blueprint, component blueprints are upgraded as separate single-
machine blueprints. The multi-machine blueprint is upgraded as a composite blueprint in which its
previous children blueprints are nested as separate blueprint components.
The upgrade creates a single composite blueprint in the target deployment that contains one virtual
machine component for each component blueprint in the source multi-machine blueprint. If a blueprint
has a setting that is not supported in the new version, the blueprint is upgraded and set to draft status.
For example, if the multi-machine blueprint contains a private network profile, upgrade ignores the profile
setting, and the blueprint is upgraded in a draft state. You can edit the draft blueprint to enter supported
network profile information and publish it.
Note If a published blueprint in the source deployment is upgraded to a draft status blueprint, the
blueprint is no longer part of a service or entitlement. After you update and publish the blueprint in the
upgraded vRealize Automation version, you must recreate its needed approval policies and entitlements.
Some multi-machine blueprint settings are not supported in the target vRealize Automation deployment,
including private network profiles and routed network profiles with associated PLR edge settings. If you
have used a custom property to specify PLR edge settings (VCNS.LoadBalancerEdgePool.Names), the
custom property is upgraded.
Upgrading from vRealize Automation 6.2.5 to 7.4
VMware, Inc. 11