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 installation of vRealize Automation with a master and replica virtual
appliances configured for high availability. See vRealize Automation High Availability Configuration
Considerations in Reference Architecture.
n
Verify that all vRealize Automation virtual appliances use the same password for root user.
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
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
Check the version numbers of vRealize Automation components on the target vRealize Automation
appliance.
a In your target vRealize Automation environment, start a browser and go to the
vRealize Automation appliance management console at https:// vra-va-
hostname.domain.name:5480.
b Log in with the user name root and the password you entered when you deployed the appliance.
c Select vRA Settings > Cluster.
d To expand the Host / Node Name records so you can see the components, click the expand
button.
Verify that the version numbers of vRealize Automation components match across all virtual
appliance nodes.
Verify that the version numbers of vRealize Automation IaaS components match across all IaaS
nodes.
n
Review Knowledge Base article 51531.
n
Perform these steps to direct traffic to only the master node.
a Disable all the redundant nodes.
Migrating vRealize Automation to 7.4
VMware, Inc. 15