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
Table 4‑2. Target vRealize Automation Appliance (Continued)
Option Description Value
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.
Table 4‑3. Target IaaS Database
Option Description Value
Database server Location of Microsoft SQL Server instance where the
cloned database resides. If named instance and a
non-default port is used, specify in
SERVER,PORT\INSTANCE-NAME format.
Cloned database name Name of the source vRealize Automation6.2.x/7.x
IaaS Microsoft SQL database cloned for migration.
Authentication mode Select either Windows or SQL Server. If you select
SQL Server, you must enter a login name and
password.
Login name Login name for the SQL Server user who has the
db_owner role for the cloned IaaS Microsoft SQL
database.
Password Password for the SQL Server user.
Original encryption key Original encryption key that you retrieve from the
source environment. See Obtain the Encryption Key
from the Source vRealize Automation Environment.
New passphrase A series of words used to generate a new encryption
key. You use this passphrase each time you install a
new IaaS component in the target
vRealize Automation environment.
What to do next
Obtain the Encryption Key from the Source vRealize Automation Environment.
Obtain the Encryption Key from the Source
vRealize Automation Environment
You must enter the encryption key from the source vRealize Automation environment as part of the
migration procedure.
Prerequisites
Verify that you have administrator privileges on the active Manager Service host virtual machine in your
source environment.
Migrating vRealize Automation to 7.4
VMware, Inc. 21