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
You can upgrade a multi-machine blueprint with vSphere endpoints and NSX network and security
settings. The upgraded blueprint contains NSX network and security components in the design canvas.
Note Routed gateway specifications for multi-machine blueprints, as defined in reservations, are
upgraded. However, the target vRealize Automation deployment does not support reservations for routed
profiles that contain associated PLR edge settings. If the source reservation contains a routed gateway
value for a PLR edge, the reservation is upgraded but the routed gateway setting is ignored. As a result,
the upgrade generates an error message in the log file and the reservation is disabled.
During upgrade, spaces and special characters are removed from referenced network and security
component names.
Note vRealize Automation 7.x takes a blueprint snapshot at deployment. If you encounter reconfigure
problems when updating machine properties such as CPU and RAM in a deployment, see Knowledge
Base article 2150829 vRA 7.x Blueprint Snapshotting.
Depending on the setting type, the network and security information is captured as several different
settings in the new blueprint.
n
Settings for the overall blueprint on its properties page. This information includes app isolation,
transport zone, and routed gateway or NSX edge reservation policy information.
n
Available settings for vSphere virtual machine components in NSX network and security components
in the design canvas.
n
Settings in the network and security tabs of individual vSphere virtual machine components in the
design canvas.
Upgrade and Physical Endpoints, Reservations, and Blueprints
You cannot upgrade a deployment that contains physical endpoints. If physical endpoints are present, the
vRealize Automation upgrade process fails.
Upgrade fails on the master virtual appliance when the vRealize Automation 6.2.x deployment has a
physical endpoint. A failure message appears in the migration interface and log. To determine if your
vRealize Automation 6.2.x deployment has a physical endpoint, log in to vRealize Automation as an IaaS
administrator user. Select Infrastructure > Endponts and review the endpoints list. If the list has a
Platform Type Physical endpoint, you cannot upgrade to vRealize Automation 7.0 and later.
Physical endpoints, reservations, and virtual machine components in blueprints are not supported in
vRealize Automation 7.0 and later.
Upgrade and Network Profile Settings
Private network profiles are not supported in vRealize Automation 7 and later. These profiles are ignored
during the upgrade. Routed network profiles with associated PLR edge settings are also not supported in
vRealize Automation 7 and later. These profiles are also ignored during the upgrade.
Upgrading from vRealize Automation 6.2.5 to 7.4
VMware, Inc. 12