6.2
Table Of Contents
- Migrating vCloud Automation Center 5.2.3 to vRealize Automation 6.2
- Contents
- Migrating from vCloud Automation Center 5.2.3 to vRealize Automation 6.2
- Updated Information
- Understanding vRealize Automation Migration
- Preparing for Migration
- Running the Pre-Migration Task
- Performing Manual Operations After Pre-Migration
- Stop IaaS Services in Target vRealize Automation System
- Back Up the Target vRealize Automation System
- Backing Up the Target vRealize Automation SQL Database
- Disabling Access to the Source System
- Stop IaaS Services in Source vCloud Automation Center 5.2 System
- Replacing the Target vRealize Automation Database with the Source vCloud Automation Center 5.2 Database
- Update Migration Table to Parse Port Value Data
- Running the Migration Task
- Performing Post-Migration Tasks Checklist
- Troubleshooting
- Cleaning Up Migration Tables in Source 5.2 Database
- Database Name Mismatch During Pre-Migration
- User Principals Cannot be Migrated
- Cannot Connect to Model Manager Web Service
- Cannot Connect to Remote Server
- Cannot Create Application Services Reservation
- Model Manager Web Service is Offline
- Pre-Migration Fails with a Load Balancer Timeout Error
- Migration Fails when Port Number is Part of Database Server Address
- Migration Fails with a Wait Operation Timeout Error
- Migration Fails with a RepoUtil Assembly Timeout Error
- Machines Not Visible on Items Page After Migration
- Reservation Not Available After Migration
After migration is finished, the vRealize Automation catalog displays the following published resource
types in the default Infrastructure catalog service.
n
InfrastructureVirtual
n
InfrastructurePhysical
n
InfrastructureCloud
n
InfrastructureMultiMachine
n
InfrastructurevApp
Migrating DEM and Agent Information
Distributed Execution Manager and agent information, including DEM skills, migrates from
vCloud Automation Center 5.2 to the target system and is captured in reports.
Distributed Execution Manager Worker and Distributed Execution Manager Orchestrator information is
migrated.
For successful migration, DEM and agent names that you specify during vRealize Automation installation
must match the names used in the source system.
Name matches retain DEM skill settings and associations. Name matches are not always required for
agents, but an agent is required for each endpoint. The pre-migration task generates warnings in the pre-
migration report when it finds DEM and agent names in the source that do not have a match in the target,
but these warnings do not prevent the task from finishing successfully.
Note To ensure that the pre-migration report does not erroneously report that agents are missing in the
target system, configure an endpoint for each agent in the target system before you start the migration
tool. If the message appears in the pre-migration report and a matching agent does exist in the target
system, configure an endpoint for the agent in the target system and then rerun pre-migration. Otherwise,
ignore the message and configure an endpoint when migration is finished.
Guest agent information is migrated but some post-migration work might be required. See Recreating
ISOs and Templates That Contain a Guest Agent.
Migrating Custom Properties
Custom properties migrate from the vCloud Automation Center 5.2 system.
Most custom properties convert to UPN format during migration. However, the following custom properties
do not convert to UPN format because doing so would potentially break the blueprints in which they are
used.
n
Image.ISO.UserName
n
Image.Network.User
n
Opsware.Server.Username
n
Plugin.AdMachineCleanup.UserName
Migrating vCloud Automation Center 5.2.3 to vRealize Automation 6.2
VMware, Inc. 18