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
Reconfigure Load Balancers After Migration to a High-Availability Environment 39
Migrating an External vRealize Orchestrator Server to vRealize Automation 7.4 39
Reconfigure the vRealize Automation Endpoint in the Target vRealize Orchestrator 40
Reconfigure the vRealize Automation Infrastructure Endpoint in the Target vRealize Orchestrator 41
Install vRealize Orchestrator Customization 42
Reconfigure Embedded vRealize Orchestrator Infrastructure Endpoint in the Target
vRealize Automation 42
Reconfigure the Azure Endpoint in the Target vRealize Automation Environment 43
Migrate vRealize Automation 6.2.x Automation Application Services to 7.4 43
Delete Original Target vRealize Automation IaaS Microsoft SQL Database 44
Update Data Center Location Menu Contents After Migration 44
Upgrading Software Agents to TLS 1.2 44
Update Source Environment Virtual Machine Templates 44
Identify Virtual Machines that Need Software Agent Upgrade 45
Upgrade Software Agents on vSphere 47
Upgrade Software Agents on Amazon Web Service or Azure 49
Validate the Target vRealize Automation 7.4 Environment 52
7
Troubleshooting Migration 53
PostgreSQL Version Causes Error 53
Some Virtual Machines Do Not Have a Deployment Created during Migration 53
Migration Log Locations 54
Catalog Items Appear in the Service Catalog After Migration But Are Not Available to Request 54
Data Collection Radio buttons Disabled in vRealize Automation 55
Troubleshooting the Software Agent Upgrade 56
Migrating vRealize Automation to 7.4
VMware, Inc. 4