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
Temporarily Change the Configuration of the Source
vRealize Automation Appliance
Before you migrate the vRealize Orchestrator server from your vRealize Automation 7.x source
environment to vRealize Automation 7.3, you must run the commands in this procedure to temporarily
change 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.
Procedure
1 Create a vro_migration user in the source PostgreSQL server.
a Before you run the command, replace VRO-MIGRATION-USER-PASSWORD with a password for
the vro_migration user .
sudo -u postgres -i -- /opt/vmware/vpostgres/current/bin/psql vcac
-c "CREATE USER vro_migration WITH PASSWORD
'VRO-MIGRATION-USER-PASSWORD';"
b Grant the vro_migration user access to the tables in the vcac database.
sudo -u postgres -i -- /opt/vmware/vpostgres/current/bin/psql vcac
-c "GRANT SELECT ON ALL TABLES IN SCHEMA public TO vro_migration;"
2 Create a backup of the source PostgreSQL client authentication configuration file
at /storage/db/pgdata/pg_hba.conf.
cp /storage/db/pgdata/pg_hba.conf /storage/db/pgdata/pg_hba.conf.bak
3 Modify the source PostgreSQL client authentication configuration file to grant vro_migration user
remote access to vcac database from the target vRealize Automation appliance. Before you run the
command, replace TARGET-VRA-APPLIANCE-IPV4-ADDRESS with the IP v4 address of the target
vRealize Automation appliance.
echo "host vcac vro_migration TARGET-VRA-APPLIANCE-IPV4-ADDRESS/32 md5"
>> /storage/db/pgdata/pg_hba.conf
4 Restart the source PostgreSQL server.
service vpostgres restart
Migrating vRealize Automation to 7.3 or 7.3.1
VMware, Inc. 48