7.4
Table Of Contents
- Migrating vRealize Automation to 7.4
- Contents
- Migrating vRealize Automation
- vRealize Automation Environment User Interfaces
- Migration Prerequisites
- Pre-Migration Tasks
- Review Changes Introduced by Migration from vRealize Automation 6.2.x to 7.x
- Apply Software Agent Patch
- Change DoDeletes Setting on the vSphere Agent to False
- Check Templates in Your vRealize Automation 6.x Source Environment
- 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
- Run Test Connection and Verify Migrated Endpoints
- Run Data Collection on Target
- Reconfigure Load Balancers After Migration
- Migrate an External 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
- Delete Original Target vRealize Automation IaaS Microsoft SQL Database
- Update Data Center Location Menu Contents After Migration
- Upgrading Software Agents to TLS 1.2
- Validate the Target vRealize Automation 7.4 Environment
- Troubleshooting Migration
- PostgreSQL Version Causes Error
- Some Virtual Machines Do Not Have a Deployment Created during Migration
- Migration Log Locations
- Catalog Items Appear in the Service Catalog After Migration But Are Not Available to Request
- Data Collection Radio buttons Disabled in vRealize Automation
- Troubleshooting the Software Agent Upgrade
4 Make a list of each tenant and IaaS administrator user name.
5 Click Cancel.
What to do next
Add Each Tenant from the Source vRealize Automation Environment to the Target Environment.
Add Each Tenant from the Source vRealize Automation
Environment to the Target Environment
You must add tenants in the target environment using the name of each tenant in the source environment.
For successful migration, it is mandatory that each tenant in the source environment is created in the
target environment. You must also use a tenant-specific access URL for each tenant that you add using
the tenant URL name from the source environment. If there are unused tenants in the source
environment that you do not want to migrate, delete them from the source environment before migration.
Perform this procedure for each tenant in your source environment.
n
When you migrate from a vRealize Automation 6.2.x environment, you migrate your existing SSO2
tenants and identity stores on the source environment to the VMware Identity Manager on the target
environment.
n
When you migrate from a vRealize Automation 7.x environment, you migrate your existing
VMware Identity Manager tenants and identity stores on the source environment to the
VMware Identity Manager on the target environment.
Prerequisites
n
Gather Information Required for Migration.
n
Log in to the target vRealize Automation console as Administrator with the password you entered
when you deployed the target vRealize Automation appliance.
Note For a high-availability environment, open the console using the fully qualified domain name of
the target virtual appliance load balancer: https://vra-va-lb-hostname.domain.name/vcac.
Procedure
1 Select Administration > Tenants.
2
Click the New icon ( ).
3 In the Name text box, enter a tenant name that matches a tenant name in the source environment.
For example, if the tenant name in the source environment is DEVTenant, enter DEVTenant.
4 (Optional) Enter a description in the Description text box.
Migrating vRealize Automation to 7.4
VMware, Inc. 23