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
Post-Migration Tasks 5
After you migrate vRealize Automation, perform the post-migration tasks that pertain to your situation.
Note After you migrate the identity stores, users of vRealize Code Stream must manually reassign
vRealize Code Stream roles.
This chapter includes the following topics:
n
Add Tenant and IaaS Administrators from the Source vRealize Automation 6.2.x Environment
n
Set the vRealize Automation PostgreSQL Replication Mode to Synchronous
n
Run Test Connection and Verify Migrated Endpoints
n
Run NSX Network and Security Inventory Data Collection in Your Target vRealize Automation 7.3
Environment
n
Reconfigure Load Balancers After Migration to a High-Availability Environment
n
Migrating an External vRealize Orchestrator Server to vRealize Automation 7.3
n
Migrate the Embedded vRealize Orchestrator Server from vRealize Automation 7.x to 7.3
n
Reconfigure the vRealize Automation Endpoint in the Target vRealize Orchestrator
n
Reconfigure the vRealize Automation Infrastructure Endpoint in the Target vRealize Orchestrator
n
Install vRealize Orchestrator Customization
n
Reconfigure Embedded vRealize Orchestrator Infrastructure Endpoint in the Target vRealize
Automation
n
Reconfigure the Azure Endpoint in the Target vRealize Automation Environment
n
Migrate vRealize Automation 6.2.x Automation Application Services to 7.3
n
Update Software Agent on Existing Virtual Machines
n
Delete Original Target vRealize Automation IaaS Microsoft SQL Database
n
Update Data Center Location Menu Contents After Migration
n
Validate the Target vRealize Automation 7.3 Environment
VMware, Inc.
32