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
Post-Migration Tasks 6
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
Run Test Connection and Verify Migrated Endpoints
n
Run NSX Network and Security Inventory Data Collection in Your Target vRealize Automation 7.4
Environment
n
Reconfigure Load Balancers After Migration to a High-Availability Environment
n
Migrating an External vRealize Orchestrator Server to vRealize Automation 7.4
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.4
n
Delete Original Target vRealize Automation IaaS Microsoft SQL Database
n
Update Data Center Location Menu Contents After Migration
n
Upgrading Software Agents to TLS 1.2
n
Validate the Target vRealize Automation 7.4 Environment
Add Tenant and IaaS Administrators from the Source
vRealize Automation 6.2.x Environment
You must delete and restore the vRealize Automation 6.2.x tenant administrators in each tenant after
migration.
VMware, Inc.
36