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
Problem
If a virtual machine is in the missing state in the source environment during migration, a corresponding
deployment is not created in the target environment.
Solution
u
If a virtual machine goes out of the missing state after migration, you can import the virtual machine to
the target deployment using bulk import.
Load Balancer Configuration Causes Timeout for Long-
Running Operations
A load balancer can cause an unexpected connection termination.
Problem
Some load balancers have very short timeouts for keeping a connection alive during execution of an
HTTP/HTTPS request. This short timeout can result in unexpected connection termination when migration
performs long-running operations.
Solution
u
Increase the timeout on the load balancer or update the load balancer DNS record to point to the
appropriate active node for the duration of the migration. Once migration is complete, revert the load
balancer DNS record.
Migration Log Locations
You can troubleshoot validation or migration problems by viewing the logs that record the migration
process.
Table 6‑1. Source vRealize Automation Appliance
Log Location
Package creation log
/var/log/vmware/vcac/migration-package.log
Table 6‑2. Target vRealize Automation Appliance
Log Location
Migration log
/var/log/vmware/vcac/migrate.log
Migration execution log
/var/log/vmware/vcac/mseq.migration.log
Migration execution output log
/var/log/vmware/vcac/mseq.migration.out.log
Validation execution log
/var/log/vmware/vcac/mseq.validation.log
Validation execution output log /var/log/vmware/vcac/mseq.validation.out.log
Migrating vRealize Automation to 7.3 or 7.3.1
VMware, Inc. 62