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
Review Changes Introduced by Migration from
vRealize Automation 6.2.x to 7.x
vRealize Automation 7 and later introduces various functional changes during and after the upgrade
process. Review these changes before you upgrade your vRealize Automation 6.2.x deployment to the
latest version.
For information about the differences between vRealize Automation 6.2.x and 7.x, see Considerations
About Upgrading to This vRealize Automation Version in Upgrading vRealize Automation 6.2.5 to 7.4.
Note The vRealize Production Test Upgrade Assist Tool analyzes your vRealize Automation 6.2.x
environment for any feature configuration that can cause upgrade issues and checks that your
environment is ready for upgrade. To download this tool and related documentation, go to the VMware
vRealize Production Test Tool download product page.
After you migrate from vRealize Automation 6.2.x to the latest version, catalog items that use these
property definitions appear in the service catalog but are not available to request.
n
Control types: Check box or link.
n
Attributes: Relationship, regular expressions, or property layouts.
In vRealize Automation 7.x, the property definitions no longer use these elements. You must recreate the
property definition or configure the property definition to use a vRealize Orchestrator script action rather
than the embedded control types or attributes. For more information, see Catalog Items Appear in the
Service Catalog After Migration But Are Not Available to Request.
Apply Software Agent Patch
Before you migrate from vRealize Automation 7.1 or 7.3 to 7.4, you must apply a hot fix to the source
appliance so that you can upgrade Software Agents to TLS 1.2.
The Transport Layer Security (TLS) protocol provides data integrity between your browser and
vRealize Automation. This hot fix makes it possible for the Software Agents in your source environment to
upgrade to TLS 1.2. This upgrade ensures the highest level of security and is required for
vRealize Automation 7.1 or 7.3. Each version has its own hot fix.
Prerequisites
A running vRealize Automation 7.1 or 7.3 source environment.
Procedure
u
Apply this hot fix to your source vRealize Automation 7.1 or 7.3 appliance before you migrate to 7.4.
See Knowledge Base article 52897.
What to do next
Change DoDeletes Setting on the vSphere Agent to False.
Migrating vRealize Automation to 7.4
VMware, Inc. 18