7.3
Table Of Contents
- Migrating vRealize Automation to 7.3 or 7.3.1
- Contents
- Updated Information
- Migrating vRealize Automation
- Migration Prerequisites
- Pre-Migration Tasks
- Review Changes Introduced by Migration from vRealize Automation 6.2.x to 7.x
- Set the vRealize Automation PostgreSQL Replication Mode to Asynchronous
- Change DoDeletes Setting on the vSphere Agent to False
- 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
- Set the vRealize Automation PostgreSQL Replication Mode to Synchronous
- Run Test Connection and Verify Migrated Endpoints
- Run Data Collection on Target
- Reconfigure Load Balancers After Migration
- Migrating an External vRealize Orchestrator Server to vRealize Automation 7.3
- Control Center Differences Between External and Embedded Orchestrator
- Migrate an External vRealize Orchestrator 6.x on Windows to vRealize Automation 7.3
- Migrate an External vRealize Orchestrator 6.x Virtual Appliance to vRealize Automation 7.3
- Migrate an External vRealize Orchestrator 7.x to vRealize Automation 7.3
- Configure the Built-In vRealize Orchestrator Server
- Migrate the Embedded vRealize 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
- Update Software Agent on Existing Virtual Machines
- Delete Original Target vRealize Automation IaaS Microsoft SQL Database
- Update Data Center Location Menu Contents After Migration
- Validate the Target vRealize Automation 7.3 Environment
- Troubleshooting Migration
- PostgreSQL Version Causes Error
- Some Virtual Machines Do Not Have a Deployment Created during Migration
- Load Balancer Configuration Causes Timeout for Long-Running Operations
- Migration Log Locations
- Catalog Items Appear in the Service Catalog After Migration But Are Not Available to Request
- Empty Deployments Are Seen in vRealize Automation After Migration
- XaaS Resource Mapping Named Deployment Is Missing After Migration
Troubleshooting Migration 6
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
Load Balancer Configuration Causes Timeout for Long-Running Operations
n
Migration Log Locations
n
Catalog Items Appear in the Service Catalog After Migration But Are Not Available to Request
n
Empty Deployments Are Seen in vRealize Automation After Migration
n
XaaS Resource Mapping Named Deployment Is Missing After Migration
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.
61