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 following architect roles are used to support the blueprint definition in the design canvas:
n
Application architect. Assembles existing components and blueprints to create composite blueprints.
n
Infrastructure architect. Creates and manages virtual machine blueprints.
n
XaaS architect. Creates and manages XaaS blueprints.
n
Software architect. Creates and manages Software components.
In vRealize Automation 7, tenant administrators and business group managers cannot design blueprints
by default. Upgraded tenant administrators and business group managers are given the infrastructure
architect role.
Users who can reconfigure a virtual machine in the vRealize Automation 6.2.x source version can change
virtual machine ownership after you upgrade to the new version.
The following role assignments are made during the upgrade. Roles that are not listed in the table are
upgraded to the same role name in the target deployment.
Table 1‑1. Roles Assigned during Upgrade
Role in Source Deployment Role in Target Deployment
Tenant administrator Tenant administrator and Infrastructure architect
Business group manager Business group manager and Infrastructure architect
Service architect XaaS architect
Application architect Software architect
For more information about tenant roles, see Tenant Roles and Responsibilities in vRealize Automation in
Foundations and Concepts.
Understanding How Blueprints Are Upgraded
As a rule, published blueprints are upgraded as published blueprints.
However, there are exceptions to that rule. Multi-machine blueprints are upgraded as composite
blueprints that contain blueprint components. Multi-machine blueprints that contain unsupported settings
are upgraded as unpublished.
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.
For more information about upgrading blueprints, see Upgrade and vApp Blueprints, vCloud Endpoints,
and vCloud Reservations and Understanding How Multi-Machine Blueprints Are Upgraded.
Upgrade and vApp Blueprints, vCloud Endpoints, and vCloud
Reservations
You cannot upgrade a deployment that contains vApp (vCloud) endpoints. The presence of vApp (vCloud)
endpoints prevents upgrade to this vRealize Automation version.
Upgrading from vRealize Automation 6.2.5 to 7.4
VMware, Inc. 10