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
Prerequisites
n
Run NSX Network and Security Inventory Data Collection in the Source vRealize Automation
Environment .
n
Successfully migrate to vRealize Automation 7.4.
Procedure
u
Run NSX Network and Security Inventory data collection in your target vRealize Automation
environment before you migrate to vRealize Automation 7.4. See Start Endpoint Data Collection
Manually in Managing vRealize Automation.
Reconfigure Load Balancers After Migration to a High-
Availability Environment
When you migrate to a high-availability environment, you must perform these tasks for each load
balancer after you finish migration.
Prerequisites
Migrate vRealize Automation Source Data to a vRealize Automation 7.4 High-Availability Environment.
Procedure
1 Restore the original health check settings so replica nodes can accept incoming traffic by configuring
the load balancers for these items.
n
vRealize Automation appliance.
n
IaaS Web Server that hosts the Model Manager.
n
Manager Service.
2 Change the load balancer timeout settings back to the default.
Migrating an External vRealize Orchestrator Server to
vRealize Automation 7.4
You can migrate your existing external vRealize Orchestrator server to an instance of
vRealize Orchestrator embedded in vRealize Automation.
Prerequisites
Successful migration to vRealize Automation 7.4.
For information, see Migrating an External Orchestrator Server to vRealize Automation 7.4 in the
vRealize Orchestrator documentation.
Migrating vRealize Automation to 7.4
VMware, Inc. 39