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
6 Click Finish.
7 Repeat for each Azure endpoint.
Migrate vRealize Automation 6.2.x Automation
Application Services to 7.3
You can use the VMware vRealize Application Services Migration Tool to migrate your existing application
services blueprints and deployment profiles from VMware vRealize Application Services 6.2.x to
vRealize Automation 7.3.
Prerequisites
Successful migration to vRealize Automation 7.3.
Procedure
u
To download the VMware vRealize Application Services Migration Tool, complete these steps.
a Click Download VMware vRealize Automation.
b Select Drivers & Tools > VMware vRealize Application Services Migration Tool.
Update Software Agent on Existing Virtual Machines
After migration from vRealize Automation 7.2 to 7.3, the target vRealize Automation console cannot
manage software components on existing virtual machines. Before the target console can manage
software components on existing virtual machines, you must update the software agent on each virtual
machine.
You use the vRealize Orchestrator client to perform these tasks:
n
Import the downloaded Software Agent Post-Migration Update package to the source
vRealize Orchestrator.
n
Update the software agent on an existing virtual machine.
n
Re-establish communication with the target vRealize Automation appliance
Note Updating software agents is an irreversible operation. After you do this update, you can no longer
manage software components on existing virtual machines with the source vRealize Automation console.
Prerequisites
n
Successful migration from source vRealize Automation 7.2 environment to target
vRealize Automation 7.3 environment.
n
Download the Software Agent Post-Migration Update package.
a Open the target vRealize Automation appliance Guest and Software Agent Installers page using
the target appliance fully qualified domain name: https://vra-va-
hostname.domain.name/software/index.html.
Migrating vRealize Automation to 7.3 or 7.3.1
VMware, Inc. 57