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
Prerequisites
n
Successful migration to vRealize Automation 7.3.
n
Stop the Orchestrator server service on the external Orchestrator.
n
Back up the database, including the database schema, of teh external Orchestrator server.
Procedure
1 Download the migration tool from the target Orchestrator server to the source Orchestrator.
a Log in to the vRealize Orchestrator 6.x Virtual Appliance over SSH as root.
b Under the /var/lib/vco directory, run the scp command to download the migration-
tool.zip archive.
scp root@vra-va-hostname.domain.name:/var/lib/vco/downloads/migration-tool.zip ./
c Run the unzip command to extract the migration tool archive.
unzip migration-tool.zipy7
2 Export the Orchestrator configuration from the source Orchestrator server.
a In the /var/lib/vco/migration-cli/bin directory, run the export command.
./vro-migrate.sh export
This command combines the VMware vRealize Orchestrator configuration files and plug-ins into
an export archive.
An archive with file name orchestrator-config-export-orchestrator_ip_address-
date_hour.zip is created in the /var/lib/vco folder.
3 Migrate the exported configuration to the Orchestrator server that is built into vRealize Automation
7.3.
a Log in to the vRealize Automation appliance over SSH as root.
b Under the /usr/lib/vco/tools/configuration-cli/bin directory, run the scp command to
download the exported configuration archive.
scp root@orchestrator_ip_or_DNS_name:/var/lib/vco/orchestrator-config-export-
orchestrator_ip_address-date_hour.zip ./
c Change the ownership of the exported Orchestrator configuration file.
chown vco:vco orchestrator-config-export-orchestrator_ip_address-date_hour.zip
Migrating vRealize Automation to 7.3 or 7.3.1
VMware, Inc. 40