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
d Stop the Orchestrator server service and the Control Center service of the built-in
vRealize Orchestrator server.
service vco-server stop && service vco-configurator stop
e Import the Orchestrator configuration file to the built-in vRealize Orchestrator server, by running
the vro-configure script with the import command.
./vro-configure.sh import --skipDatabaseSettings --skipLicense --skipSettings --
skipSslCertificate --notForceImportPlugins --notRemoveMissingPlugins --skipTrustStore --path
orchestrator-config-export-orchestrator_appliance_ip-date_hour.zip
4 If the external Orchestrator server from which you want to migrate uses the built-in PostgreSQL
database, edit its database configuration files.
a In the /var/vmware/vpostgres/current/pgdata/postgresql.conf file, uncomment the
listen_addresses line.
b Set the values of listen_addresses to a wildcard (*).
listen_addresses ='*'
c Append a line to the /var/vmware/vpostgres/current/pgdata/pg_hba.conf file.
host all all vra-va-ip-address/32 md5
Note The pg_hba.conf file requires using a CIDR prefix format instead on an IP address and a
subnet mask.
d Restart the PostgreSQL server service.
service vpostgres restart
Migrating vRealize Automation to 7.3 or 7.3.1
VMware, Inc. 41