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
n
For a high-availability deployment: Synchronize Users and Groups for an Active Directory Link Before
Migration to a High-Availability Environment.
Synchronize Users and Groups for an Active Directory
Link Before Migration to a Minimal Environment
Before you import your users and groups to a minimal deployment of vRealize Automation, you must
connect the target vRealize Automation to your Active Directory link.
Perform this procedure for each tenant. If a tenant has more than one Active Directory, perform this
procedure for each Active Directory that the tenant uses.
Prerequisites
n
Create an Administrator for Each Added Tenant.
n
Verify that you have access privileges to the Active Directory.
n
Log in to the vRealize Automation console as a tenant administrator.
Procedure
1 Select Administration > Directories Management > Directories.
2
Click Add Directory icon ( ) and select Add Active Directory over LDAP/IWA.
3 Enter your Active Directory account settings.
u
For Non-Native Active Directories
Option Sample Input
Directory Name Enter a unique directory name.
Select Active Directory over LDAP when using Non-Native Active Directory.
This Directory Supports DNS Service
Location
Deselect this option.
Base DN Enter the distinguished name (DN) of the starting point for directory server
searches.
For example, cn=users,dc=rainpole,dc=local.
Bind DN Enter the full distinguished name (DN), including common name (CN), of an
Active Directory user account that has privileges to search for users.
For example, cn=config_admin infra,cn=users,dc=rainpole,dc=local.
Bind DN Password Enter the Active Directory password for the account that can search for users and
click Test Connection to test the connection to the configured directory.
u
For Native Active Directories
Option Sample Input
Directory Name Enter a unique directory name.
Select Active Directory (Integrated Windows Authentication) when using
Native Active Directory.
Domain Name Enter the name of the domain to join.
Migrating vRealize Automation to 7.3 or 7.3.1
VMware, Inc. 21