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
Table 1‑1. Understanding What Data is Migrated (Continued)
vCloud Automation Center Item Migrates Yes or No Details and Related Information
Endpoints Yes Endpoint information is migrated.
Associated machine and compute
resource information is also migrated.
Endpoint information is captured in
reports. You can update your endpoints
before or after migration. See the support
matrix invRealize Automation product
documentation for a list of supported
endpoints.
Blueprints Yes See Migrating Blueprints and Migrating
Entitlements.
Reservations and reservation policies Yes Machine and compute resource
information is also migrated. Reservations
retain their settings, including capacity
alerts, memory, priority, storage, and so
on. Each reservation is configured for a
named business group. Business group
users can request machines on a
specified compute resource.
Storage reservation policies and storage
cost profiles
Yes
Compute resources Yes Compute resource information is
migrated, including cost profile, storage
cost profile, storage reservation policy,
custom properties, and so on. The
associated machine and reservation
information for each business group is
also migrated.
Distributed Execution Managers, DEM
skills, and agents
Yes See Migrating DEM and Agent
Information.
Network profiles Yes
Cost profiles Yes
Supplied custom properties Yes See Migrating Custom Properties.
Supplied workflows Yes Standard workflows are migrated. Custom
workflows are not migrated.
Machines, including lease, linked clone,
and machine limit settings
Yes Machine and compute resource
information is migrated. See Migrating
Machines.
Global properties Yes Global properties that are supported in the
target system are migrated.
Snapshots Yes
Migrating vCloud Automation Center 5.2.3 to vRealize Automation 6.2
VMware, Inc. 10