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
Procedure
u
Run NSX Network and Security Inventory data collection in your source vRealize Automation
environment before you migrate to vRealize Automation 7.3. See Start Endpoint Data Collection
Manually in Managing vRealize Automation.
What to do next
Manually Clone the Source vRealize Automation IaaS Microsoft SQL Database.
Manually Clone the Source vRealize Automation IaaS
Microsoft SQL Database
Before migration, you must back up your IaaS Microsoft SQL database in the vRealize Automation source
environment and restore it to a new blank database created in the vRealize Automation target
environment.
Prerequisites
n
Run NSX Network and Security Inventory Data Collection in the Source vRealize Automation
Environment.
n
Obtain information about backing up and restoring an SQL Server database. Find articles on the
Microsoft Developer Network about creating a full SQL Server database backup and restoring an
SQL Server database to a new location.
Procedure
u
Create a full backup of your source vRealize Automation 6.2.x or 7.x IaaS Microsoft SQL database.
You use the backup to restore the SQL database to a new blank database created in the target
environment.
What to do next
Snapshot the Target vRealize Automation Environment.
Snapshot the Target vRealize Automation Environment
Take a snapshot of each target vRealize Automation virtual machine. If migration is unsuccessful, you can
try again using the virtual machine snapshots.
For information, see your vSphere documentation.
Prerequisites
Manually Clone the Source vRealize Automation IaaS Microsoft SQL Database.
What to do next
Perform one of the following procedures:
n
Migrate vRealize Automation Source Data to a vRealize Automation 7.3 Minimal Environment.
Migrating vRealize Automation to 7.3 or 7.3.1
VMware, Inc. 25