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
5 Import the configuration file to the embedded target vRealize Orchestrator server.
/usr/lib/vco/tools/configuration-cli/bin/vro-configure.sh import --skipDatabaseSettings --
skipLicense --skipSettings --skipSslCertificate --skipTrustStore --notForceImportPlugins --
notRemoveMissingPlugins --path /tmp/vro-config.zip
Import of Orchestrator Configuration finished successfully appears when the
configuration file import succeeds.
Note If the import is successful, you can safely ignore any messages marked [ERROR] or [WARN]
when you run this command.
6 Migrate the source vRealize Orchestrator database to the PostgreSQL server running on the target
vRealize Automation appliance. Before you run the command, replace SOURCE-VRA-APPLIANCE-
HOST-NAME with the fully qualified domain name of the source vRealize Automation appliance and
VRO-MIGRATION-USER-PASSWORD with the vro_migration user password that you created in the
Temporarily Change the Configuration of the Source vRealize Automation Appliance procedure.
/usr/lib/vco/tools/configuration-cli/bin/vro-configure.sh db-migrate --sourceJdbcUrl
jdbc:postgresql://SOURCE-VRA-APPLIANCE-HOST-NAME:5432/vcac --sourceDbUsername vro_migration --
sourceDbPassword VRO-MIGRATION-USER-PASSWORD
7 Delete the old trusted certificates from the migrated database.
sudo -u postgres -i -- /opt/vmware/vpostgres/current/bin/psql vcac -c "DELETE FROM vmo_keystore
WHERE id='cakeystore-id';"
8 Delete old vRealize Orchestrator nodes from the migrated database.
sudo -u postgres -i -- /opt/vmware/vpostgres/current/bin/psql vcac -c "DELETE FROM
vmo_clustermember;"
9 Delete vro-config.zip from the /tmp directory.
rm -rf /tmp/vro-config.zip
10 Start the vRealize Orchestrator server service.
service vco-server start
For a high-availability deployment, start the vRealize Orchestrator server service only on the master
vRealize Automation appliance.
What to do next
Reconfigure the Target Embedded vRealize Orchestrator to Support High Availability
Migrating vRealize Automation to 7.3 or 7.3.1
VMware, Inc. 51