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
3 Run this command.
vcac-config migrate-custom-groups
n
This message appears when migration completes: The migration of Custom Groups
completed successfully!
n
This message appears if no custom groups are in your source environment: No Custom Groups
were found in vRA database. Migration process will be skipped.
Note If custom group migration fails, view the log file at /var/log/vmware/vcac/vcac-
config.log for details.
Migrate Multiple Tenant and IaaS Administrators
For each vRealize Automation tenant with Tenant or IaaS administrators, you must delete and restore
each administrator manually.
Perform the following procedure for each tenant in the vRealize Automation console.
Prerequisites
Log in to the vRealize Automation console on the upgraded virtual appliance.
1 Open the vRealize Automation console on the upgraded virtual appliance using its fully qualified
domain name, https://va-hostname.domain_name/vcac.
For a distributed environment, open the console on the master virtual appliance.
2 Select the vsphere.local domain.
3 Log in with the user name administrator and the password that you entered when you deployed
the virtual appliance.
Procedure
1 Select Administration > Tenants.
2 Click a tenant name.
3 Click Administrators.
4 Make a list of each tenant and IaaS administrator name and user name.
5
Point to each administrator and click the delete icon ( ) until you delete all administrators.
6 Click Finish.
7 On the Tenants page, click the tenant name again.
8 Click Administrators.
9 Enter the name of each user that you deleted in the appropriate search box and press Enter.
Upgrading from vRealize Automation 6.2.5 to 7.4
VMware, Inc. 41