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
Change DoDeletes Setting on the vSphere Agent to False
If you migrate from a vRealize Automation 6.2.4 environment, you must change the DoDeletes setting on
your target vSphere agent before migration. This prevents virtual machines from your source environment
being deleted after migration.
Follow the steps in the Configure the vSphere Agent procedure in Installing vRealize Automation to set
DoDeletes to false.
Prerequisites
You have completed the prerequisites for migration.
What to do next
Prepare vRealize Automation Virtual Machines for Migration.
Check Templates in Your vRealize Automation 6.x Source
Environment
Before you migrate from a vRealize Automation 6.x to 7.4, you must check your virtual machine templates
to make sure that every template has a minimum memory setting of at least 4 MB.
If you have a virtual machine template in your vRealize Automation 6.x source environment with less than
4 MB of memory, migration fails. Complete this procedure to determine if any blueprints in the 6.x source
environment have less than 4 MB of memory.
Prerequisites
You are migrating from vRealize Automation 6.x to 7.4.
Procedure
1 Log in to the primary vRealize Automation appliance over SSH as root.
If your vRealize Orchestrator is external, log in to the Orchestrator host machine.
2 Check if there are any blueprints with memory specified at less than 4 MB.
select * from [vCAC].[dbo].[VirtualMachineTemplate] where IsHidden = 0 and
MemoryMB < 4;
where vCAC is the database name.
3 If the script finds any blueprints with memory specified at less than 4 MB, then update the memory to
at least 4 MB.
update [vCAC].[dbo].[VirtualMachineTemplate] set MemoryMB = 4 where IsHidden = 0
and MemoryMB < 4;
where vCAC is the database name.
Migrating vRealize Automation to 7.4
VMware, Inc. 19