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
Guest agent and agent bootstrap code must be updated in the source environment templates. If you are
using a linked clone option, you might need to remap the templates with the newly created virtual
machines and their snapshots.
To upgrade your templates, you complete these tasks.
1 Log in to vSphere.
2 Convert each template from vRealize Automation 7.1, 7.2, 7.3 or 7.3.1 to a virtual machine and power
on the machine.
3 Import the appropriate software installer and run the software installer on each virtual machine.
4 Convert each virtual machine back to a template.
Use this procedure to locate the software installers for Linux or Windows.
Prerequisites
n
Apply Software Agent Patch if you migrated from vRealize Automation 7.1, or 7.3 to 7.4.
n
Successful migration from vRealize Automation 7.1, 7.2, 7.3 or 7.3.1 to 7.4.
Procedure
1 Start a browser and open the vRealize Automation 7.4 appliance splash page using the fully qualified
domain name of the virtual appliance: https://vra-va-hostname.domain.name.
2 Click Guest and software agents page.
3 Follow the instructions for the Linux or Windows software installers.
What to do next
Identify Virtual Machines that Need Software Agent Upgrade.
Identify Virtual Machines that Need Software Agent Upgrade
You can use the Health Service in the vRealize Automation Console to identify virtual machines that need
software agent update to TLS 1.2.
Sometimes the patch applied to your vRealize Automation source environment does not upgrade all of
the virtual machines. You can use the Health Service to identify the virtual machines that still need a
software agent update to TLS 1.2. All software agents in the target environment need to be updated for
post-provisioning procedures.
Prerequisites
n
Apply Software Agent Patch if you migrated from vRealize Automation 7.1, or 7.3 to 7.4.
n
You have successfully migrated vRealize Automation 7.1, 7.2, 7.3 or 7.3.1 to 7.4.
n
You are logged in to vRealize Automation 7.4 on the primary virtual appliance.
Migrating vRealize Automation to 7.4
VMware, Inc. 45