7.4
Table Of Contents
- Migrating vRealize Automation to 7.4
- Contents
- Migrating vRealize Automation
- vRealize Automation Environment User Interfaces
- Migration Prerequisites
- Pre-Migration Tasks
- Review Changes Introduced by Migration from vRealize Automation 6.2.x to 7.x
- Apply Software Agent Patch
- Change DoDeletes Setting on the vSphere Agent to False
- Check Templates in Your vRealize Automation 6.x Source Environment
- Prepare vRealize Automation Virtual Machines for Migration
- Gather Information Required for Migration
- Obtain the Encryption Key
- List Tenant and IaaS Administrators
- Add Each Tenant from the Source Environment
- Create an Administrator for Each Added Tenant
- Synchronize Users and Groups Before Migration to a Minimal Environment
- Synchronize Users and Groups Before Migration to a High-Availability Environment
- Run Data Collection in Source
- Manually Clone the Source Microsoft SQL Database
- Snapshot the Target Environment
- Migration Procedures
- Post-Migration Tasks
- Add Tenant and IaaS Administrators
- Run Test Connection and Verify Migrated Endpoints
- Run Data Collection on Target
- Reconfigure Load Balancers After Migration
- Migrate an External Orchestrator Server
- Reconfigure the vRealize Automation Endpoint
- Reconfigure the vRealize Automation Infrastructure Endpoint
- Install vRealize Orchestrator Customization
- Reconfigure Embedded vRealize Orchestrator Endpoint
- Reconfigure the Azure Endpoint
- Migrate Automation Application Services
- Delete Original Target vRealize Automation IaaS Microsoft SQL Database
- Update Data Center Location Menu Contents After Migration
- Upgrading Software Agents to TLS 1.2
- Validate the Target vRealize Automation 7.4 Environment
- Troubleshooting Migration
- PostgreSQL Version Causes Error
- Some Virtual Machines Do Not Have a Deployment Created during Migration
- Migration Log Locations
- Catalog Items Appear in the Service Catalog After Migration But Are Not Available to Request
- Data Collection Radio buttons Disabled in vRealize Automation
- Troubleshooting the Software Agent Upgrade
Troubleshooting Migration 7
Migration troubleshooting topics provide solutions to problems you might experience when you migrate
vRealize Automation.
This chapter includes the following topics:
n
PostgreSQL Version Causes Error
n
Some Virtual Machines Do Not Have a Deployment Created during Migration
n
Migration Log Locations
n
Catalog Items Appear in the Service Catalog After Migration But Are Not Available to Request
n
Data Collection Radio buttons Disabled in vRealize Automation
n
Troubleshooting the Software Agent Upgrade
PostgreSQL Version Causes Error
A source vRealize Automation 6.2.x environment containing an updated PostgreSQL database blocks
administrator access.
Problem
If an upgraded PostgreSQL database is used by vRealize Automation 6.2.x, an administrator must add an
entry to the pg_hba.conf file that provides access to this database from vRealize Automation.
Solution
1 Open the pg_hba.conf file.
2 To grant access to this database, add the following entry.
host all vcac-database-user vra-va-ip trust-method
Some Virtual Machines Do Not Have a Deployment
Created during Migration
Virtual machines in the missing state at the time of migration do not have a corresponding deployment
created in the target environment.
VMware, Inc.
53