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
b Log in with the user name root and the password you entered when you deployed the appliance.
c Select vRA Settings > Database.
d Verify that the database node host mode is MASTER.
n
Verify that the target Microsoft SQL Server version for the vRealize Automation target IaaS database
is 2012, 2014, or 2016.
n
Verify that port 22 is open between the source and target vRealize Automation environments. Port 22
is required to establish Secure Shell (SSH) connections between source and target virtual appliances.
n
Verify that the IaaS Web Service and Model Manager Server nodes in the target environment have
the right Java Runtime Environment. You must have Java SE Runtime Environment (JRE) 8, update
111 (64 bit) or later installed. Make sure the JAVA_HOME system variable points to the Java version
you installed on each IaaS node. Revise the path if necessary.
n
Verify that each IaaS node has at least PowerShell 3.0 or later installed.
n
Verify that the source and target vRealize Automation environments are running.
n
Verify that no user and provisioning activities are happening on the source vRealize Automation
environment.
n
Verify that any antivirus or security software that might interact with the operating system and its
components running on IaaS nodes in the target vRealize Automation environment is correctly
configured or disabled.
n
Security software must not interact with the operating system and its components running on IaaS
nodes in the target vRealize Automation environment during migration. If you have any antivirus or
security software installed, verify that it is correctly configured or disabled for migration.
What to do next
Chapter 3 Pre-Migration Tasks.
Migrating vRealize Automation to 7.3 or 7.3.1
VMware, Inc. 12