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
To restore the original health check settings so replica nodes can accept incoming traffic, configure
the load balancers for these items.
n
vRealize Automation appliance.
n
IaaS Web Server that hosts the Model Manager.
n
Manager Service.
Migrating an External vRealize Orchestrator Server to
vRealize Automation 7.3
You can migrate your existing external vRealize Orchestrator server to a vRealize Orchestrator instance
embedded in vRealize Automation.
You can deploy vRealize Orchestrator as an external server instance and configure vRealize Automation
to work with that external instance, or you can configure and use the vRealize Orchestrator server that is
included in the vRealize Automation appliance.
VMware recommends that you migrate your external vRealize Orchestrator to the Orchestrator server that
is built into vRealize Automation. The migration from an external to embedded Orchestrator provides the
following benefits:
n
Reduces the total cost of ownership.
n
Simplifies the deployment model.
n
Improves the operational efficiency.
Note Consider using the external vRealize Orchestrator in the following cases:
n
Multiple tenants in the vRealize Automation environment
n
Geographically dispersed environment
n
Workload handling
n
Use of specific plug-ins, such as the Site Recovery Manager plug-in
Control Center Dierences Between External and Embedded
Orchestrator
Some of the menu items that are available in Control Center of an external vRealize Orchestrator are not
included in the default Control Center view of an embedded Orchestrator instance.
In Control Center of the embedded Orchestrator server, a few options are hidden by default.
Menu Item Details
Licensing The embedded Orchestrator is preconfigured to use vRealize Automation as a license provider.
Export/Import Configuration The embedded Orchestrator configuration is included in the exported vRealize Automation
components.
Migrating vRealize Automation to 7.3 or 7.3.1
VMware, Inc. 36