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
4 Identify endpoints containing the fully qualified domain name (FQDN) of the source
vRealize Automation appliance host or if you migrated from a high-availability deployment, the load-
balanced host.
If you find endpoints containing the FQDN of the source
vRealize Automation appliance host or if you migrated
from a high-availability deployment, the load-balanced
host
If you do not find endpoints containing the FQDN of the
source vRealize Automation appliance host or if you
migrated from a high-availability deployment, the load-
balanced host
1 Click Workflows.
2 Click the expand button to select Library > vRealize
Automation > Configuration.
3 Run the Remove a vRA host workflow for every endpoint
containing the FQDN of the source vRealize Automation
appliance host .
1 Click Resources.
2 Click the update icon on the top toolbar.
3 Click the expand button to select Library > vCACCAFE >
Configuration.
4 Delete each resource that has a URL property containing
the FQDN of the source vRealize Automation appliance
host or if you migrated from a high-availability
deployment., the load-balanced host.
5 Click Workflows.
6 Click the expand button to select Library > vRealize Automation > Configuration.
7 To add the target vRealize Automation appliance host or if you migrated to a high-availability
deployment, the load-balanced host, run the Add a vRA host using component registry workflow.
Reconfigure the vRealize Automation Infrastructure
Endpoint in the Target vRealize Orchestrator
Use the following procedure to reconfigure the vRealize Automation infrastructure endpoint in the
embedded target vRealize Orchestrator.
Prerequisites
n
Successful migration to vRealize Automation 7.3.
n
Connect to the target vRealize Orchestrator using the vRealize Orchestrator client. For information,
see Using the VMware vRealize Orchestrator Client in the vRealize Orchestrator documentation.
Procedure
1 Select Design from the top drop-down menu.
2 Click Inventory.
3 Expand vRealize Automation Infrastructure.
Migrating vRealize Automation to 7.3 or 7.3.1
VMware, Inc. 54