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
5 In the URL Name text box, enter a tenant URL name that matches the tenant URL name in the
source environment.
The URL name is used to append a tenant-specific identifier to the vRealize Automation console
URL.
For example, if the URL name for DEVTenant in the source environment is dev, enter dev to create
the URL https://vra-va-hostname.domain.name/vcac/org/dev.
6 (Optional) Enter an email address in the Contact Email text box.
7 Click Submit and Next.
What to do next
Create an Administrator for Each Added Tenant.
Create an Administrator for Each Added Tenant
You must create an administrator for each tenant that you added to the target environment. You create an
administrator by creating a local user account and assigning tenant administrator privileges to the local
user account.
Perform this procedure for each tenant in your target environment.
Prerequisites
n
Add Each Tenant from the Source vRealize Automation Environment to the Target Environment.
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 a tenant that you added.
For example, for DEVTenant, click DEVTenant.
3 Click Local users.
4
Click the New icon ( ).
5 In User Details, enter the requested information to create a local user account to assign the tenant
administrator role.
The local user name must be unique to the default local directory, vsphere.local.
6 Click OK.
7 Click Administrators.
Migrating vRealize Automation to 7.4
VMware, Inc. 24