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
Reconfigure the Target Embedded vRealize Orchestrator to
Support High Availability
For a high-availability deployment, you must manually rejoin each target replica vRealize Automation
appliance to the cluster to enable high-availability support for the embedded vRealize Orchestrator.
Prerequisites
Log in to the target replica vRealize Automation appliance management.
1 Start a browser and open the target replica vRealize Automation appliance management using the
fully qualified domain name (FQDN) of the target replica virtual appliance: https://vra-va-
hostname.domain.name:5480.
2 Log in with the user name root and the password that you entered when you deployed the target
replica vRealize Automation appliance.
Procedure
1 Select vRA Settings > Cluster.
2 In the Leading Cluster Node text box, enter the fully qualified domain name (FQDN) of the target
master vRealize Automation appliance.
3 Enter the root user password in the Password text box.
4 Click Join Cluster.
Continue past any certificate warnings. The system restarts services for the cluster.
5 Verify that the services are running.
a On the top tab bar, click Services.
b Click Refresh to monitor the progress of services startup.
What to do next
Restore the Configuration of the Source vRealize Automation Appliance
Restore the Configuration of the Source vRealize Automation
Appliance
Use this procedure to restore the configuration of the source vRealize Automation appliance.
Prerequisites
n
For a minimal deployment, log in using SSH to the source vRealize Automation appliance as root.
n
For a high-availability deployment, log in using SSH to the master source vRealize Automation
appliance as root.
Migrating vRealize Automation to 7.3 or 7.3.1
VMware, Inc. 52