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
2 Create a plan file to upgrade the Software Agent on a Linux or a Windows virtual machine.
n
Modify the migrate params file under /var/log/vcac/agentupdate/{tenant}/{subtenant-UUID} to
contain the value of the private IP address corresponding to the AWS or Azure endpoint.
"key": "ipAddress",
"value": {
"type": "string",
"value": "<$PrivateIp:$PrivatePort>"
}
n
Use this command for updating a Linux machine.
/usr/lib/vcac/server/webapps/ROOT/software/updateSoftwareAgents.py -a <$DestionationVRAServer>
-t <$Tenant> -S <$SourceVRAServer> -tu <$TenantUser> -CL Software.LinuxAgentUpdate74 --
source_cloud_provider azure
n
Use this command for updating a Windows machine.
/usr/lib/vcac/server/webapps/ROOT/software/updateSoftwareAgents.py -a <$DestionationVRAServer>
-t <$Tenant> -S <$SourceVRAServer> -tu <$TenantUser> -CW Software.WindowsAgentUpdate74 --
source_cloud_provider azure
n
This command runs the plan file.
/usr/lib/vcac/server/webapps/ROOT/software/updateSoftwareAgents.py -a <$DestionationVRAServer>
-t <$Tenant> -tu <$TenantUser> --plan_file /usr/lib/vcac/server/webapps/ROOT/software/plan
Migrating vRealize Automation to 7.4
VMware, Inc. 50