7.3
Table Of Contents
- Migrating vRealize Automation to 7.3 or 7.3.1
- Contents
- Updated Information
- Migrating vRealize Automation
- Migration Prerequisites
- Pre-Migration Tasks
- Review Changes Introduced by Migration from vRealize Automation 6.2.x to 7.x
- Set the vRealize Automation PostgreSQL Replication Mode to Asynchronous
- Change DoDeletes Setting on the vSphere Agent to False
- 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
- Set the vRealize Automation PostgreSQL Replication Mode to Synchronous
- Run Test Connection and Verify Migrated Endpoints
- Run Data Collection on Target
- Reconfigure Load Balancers After Migration
- Migrating an External vRealize Orchestrator Server to vRealize Automation 7.3
- Control Center Differences Between External and Embedded Orchestrator
- Migrate an External vRealize Orchestrator 6.x on Windows to vRealize Automation 7.3
- Migrate an External vRealize Orchestrator 6.x Virtual Appliance to vRealize Automation 7.3
- Migrate an External vRealize Orchestrator 7.x to vRealize Automation 7.3
- Configure the Built-In vRealize Orchestrator Server
- Migrate the Embedded vRealize 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
- Update Software Agent on Existing Virtual Machines
- Delete Original Target vRealize Automation IaaS Microsoft SQL Database
- Update Data Center Location Menu Contents After Migration
- Validate the Target vRealize Automation 7.3 Environment
- Troubleshooting Migration
- PostgreSQL Version Causes Error
- Some Virtual Machines Do Not Have a Deployment Created during Migration
- Load Balancer Configuration Causes Timeout for Long-Running Operations
- Migration Log Locations
- Catalog Items Appear in the Service Catalog After Migration But Are Not Available to Request
- Empty Deployments Are Seen in vRealize Automation After Migration
- XaaS Resource Mapping Named Deployment Is Missing After Migration
Table 3‑1. Source vRealize Automation Appliance
Option Description Value
Host name Log in to your source vRealize Automation appliance
management console. Find the host name on the
System tab. The host name must be a fully qualified
domain name (FQDN).
Root username root
Root password The root password that you entered when you
deployed your source vRealize Automation appliance.
Table 3‑2. Target vRealize Automation Appliance
Option Description Value
Root username root
Root password The root password that you entered when you
deployed your target vRealize Automation appliance.
Default tenant The default tenant you created when you configured
single sign-on in the vRealize Automation Installation
wizard, usually vsphere.local.
Administrator username Default tenant administrator user name that you
entered when you deployed the target
vRealize Automation environment, usually
administrator.
Administrator password Password for the default tenant administrator user that
you entered when you deployed the target
vRealize Automation environment.
Table 3‑3. Target IaaS Database
Option Description Value
Database server The location of the Microsoft SQL Server where the
restored vRealize Automation IaaS Microsoft SQL
database resides. If a named instance and non-default
port is used, enter in SERVER,PORT\INSTANCE-
NAME format.
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.
Login name Login name of a user with db_owner role for the
cloned IaaS Microsoft SQL database in the target
environment.
For Windows Authentication, the Windows account for
the vCloud Automation Center Management Agent
service must be db_owner for the cloned IaaS SQL
database.
Password Password for the SQL Server user who has the
db_owner role for the cloned IaaS Microsoft SQL
database.
Migrating vRealize Automation to 7.3 or 7.3.1
VMware, Inc. 16