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
Consider reducing the number of provisioning groups and special case blueprints before migration to
keep the number of migrated entitlements to a minimum. In addition to the two standard entitlements, an
entitlement is also created for each blueprint for which restricted access is configured.
The following considerations are helpful to further understand how entitlements are migrated:
n
Approval policies are linked to entitlements.
n
Blueprints that are entitled or assigned to more than one group are published with a shared scope.
n
Entitlements are created with an active status.
n
Entitlements cannot be deleted, although they can be deactivated.
n
Blueprints that are disabled are migrated but are not published to the catalog or listed as an entitled
catalog item on the Entitlements page.
n
If a business group has no blueprints, the migration process does not create entitlements for that
business group.
For more information about entitlements, see Migrating Blueprints and Migrating Approval Policies.
For information about how to create and use entitlements in the target vRealize Automation system, see
Tenant Administration in the vRealize Automation documentation.
Migrating Machines
Machine information is migrated. Associated reservation, compute resource, and endpoint information is
also migrated.
Migrated machines are published to the target vRealize Automation system catalog as resources.
Published resources are displayed on the Items tab. Although these published resources are not
associated with a service, they are connected by catalog items that are associated with the Infrastructure
service. Actions to which the business group members are entitled are maintained as available catalog
item actions.
Catalog resources are also created for each multi-machine service and its component machines and
each vApp machine and its vApp component machines.
Multi-machine blueprint vCloud Networking and Security configurations are not migrated.
The following machine characteristics are migrated for each resource.
n
Owner
n
Cost
n
Machine type
n
Lease
n
Description notes
Migrating vCloud Automation Center 5.2.3 to vRealize Automation 6.2
VMware, Inc. 17