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
Delete Original Target vRealize Automation IaaS
Microsoft SQL Database
You can delete the original IaaS database after migration is complete.
Prerequisites
Successful migration to the latest version of vRealize Automation.
Your migrated environment does not use the original vRealize Automation IaaS Microsoft SQL database
that you created when you installed the target vRealize Automation environment. You can safely delete
this original IaaS database from the Microsoft SQL Server after you complete migration.
Update Data Center Location Menu Contents After
Migration
After migration, you must add any missing custom data center locations to the Location drop-down
menu.
After migration to the latest version of vRealize Automation, the data center locations in the Location
drop-down menu on the Compute Resources page revert to the default list. Although custom data center
locations are missing, all compute resource configurations migrate successfully and the
Vrm.DataCenter.Location property is not affected. You can still add custom data center locations to the
Location menu.
Prerequisites
Migrate to the latest version of vRealize Automation.
Procedure
u
Add missing data center locations to the Location drop-down menu. See Scenario: Add Datacenter
Locations for Cross Region Deployments in Configuring vRealize Automation.
Upgrading Software Agents to TLS 1.2
After you migrate to vRealize Automation 7.1, 7.2, 7.3 or 7.3.1 to 7.4, you must perform several tasks to
upgrade the Software Agents from your source environment to Transport Layer Security (TLS) 1.2
Beginning with vRealize Automation 7.4, TLS 1.2 is the only supported TLS protocol for data
communication between vRealize Automation and your browser. After migration, you must upgrade
existing virtual machine templates from your vRealize Automation 7.1 or 7.3 source environment as well
as any existing virtual machines.
Update Source Environment Virtual Machine Templates
You must update existing vRealize Automation 7.1, 7.2, 7.3 or 7.3.1 templates after you complete
migration to 7.4 so that the Software Agents use the TLS 1.2 protocol.
Migrating vRealize Automation to 7.4
VMware, Inc. 44