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
Prerequisites
n
Verify that you have a new target environment of vRealize Automation.
n
Install relevant proxy agents on the target environment according to these requirements.
n
Target proxy agent name must match the source proxy agent name for vSphere, Hyper-V, Citrix
XenServer, and Test proxy agents.
Note Finish these steps to obtain an agent name.
1 On the IaaS host, log in to Windows as a local user with administrator privileges.
2 Use Windows Explorer to go to the agent installation directory.
3 Open the VRMAgent.exe.config file.
4 Under the serviceConfiguration tag, look for the value of the agentName attribute.
n
Review Knowledge Base article 51531.
n
Target proxy agent endpoint name must match the source proxy agent endpoint name for
vSphere, Hyper-V, Citrix XenServer, and Test proxy agents.
n
Do not create an endpoint for vSphere, Hyper-V, Citrix XenServer, or Test proxy agents on the
target environment.
n
Review the version numbers of vRealize Automation components on the target vRealize Automation
appliance.
a Log in to the target vRealize Automation Appliance Management as root using the password you
entered when you deployed the target vRealize Automation appliance.
b Select vRA Settings > Cluster.
c Expand the Host / Node Name records by clicking the triangle.
Verify that the version numbers of the vRealize Automation IaaS components match.
n
Verify that the target Microsoft SQL Server version for the vRealize Automation target IaaS database
is 2012, 2014, or 2016.
n
Verify that port 22 is open between the source and target vRealize Automation environments. Port 22
is required to establish Secure Shell (SSH) connections between source and target virtual appliances.
n
Verify that the endpoint vCenter has sufficient resources to complete migration.
n
Verify that the target vRealize Automation environment system time is synchronized between Cafe
and the IaaS components.
n
Verify that the IaaS server node in the target environment has at least Java SE Runtime Environment
(JRE) 8, 64 bit, update 161 or later installed. After you install the JRE, make sure the JAVA_HOME
environment variable points to the Java version you installed on each IaaS node. Revise the path if
necessary.
n
Verify that each IaaS node has PowerShell 3.0 or later installed.
Migrating vRealize Automation to 7.4
VMware, Inc. 12