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
n
Manually Clone the Source vRealize Automation IaaS Microsoft SQL Database.
n
Snapshot the Target vRealize Automation Environment.
n
Log in to the target vRealize Automation Appliance Management as root using the password you
entered when you deployed the target vRealize Automation appliance.
Procedure
1 Select vRA Settings > Migration.
2 Enter the information for the source vRealize Automation appliance.
Option Description
Host name The host name for the source vRealize Automation appliance.
Root username
root
Root password The root password that you entered when you deployed the source
vRealize Automation appliance.
3 Enter the information for the migration package location on the source vRealize Automation
appliance.
Option Description
Migration package location Path to an existing directory on the source vRealize Automation 6.2.x or 7.x
appliance where the migration package is created.
4 Enter the information for the target vRealize Automation appliance.
Option Description
Root username
root
Root password The root password that you entered when you deployed the target
vRealize Automation appliance.
Default tenant vsphere.local
Administrator username administrator
Administrator password Password for the administrator@vsphere.local user that you entered when you
deployed the target vRealize Automation environment.
5 Enter the information for the target IaaS database server.
Option Description
Database server The location of the Microsoft SQL Server instance where the restored vRealize
Automation IaaS Microsoft SQL database resides. If a named instance and a non-
default port are used, enter in SERVER,PORT\INSTANCE-NAME format. If you
configure the target Microsoft SQL Server to use the AlwaysOn Availability Group
(AAG) feature, the target SQL Server should be entered as the AAG listener
name, without a port or instance name.
Cloned database name Name of the source vRealize Automation 6.2.x or 7.x IaaS Microsoft SQL
database that you backed up on the source and restored on the target
environment.
Migrating vRealize Automation to 7.4
VMware, Inc. 34