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
n
Status: Active
n
Levels: 1 approval level
For information about how to create and use approvals and approval policies in the target system, see
Tenant Administration in the vRealize Automation documentation.
Migrating Entitlements
Migration creates entitlements based on vCloud Automation Center 5.2 blueprint settings.
Blueprint management, including approval and entitlement management, has changed. For more
information, see Changes from vCloud Automation Center 5.2 and Foundations and Concepts in
vRealize Automation documentation. The Changes from vCloud Automation Center 5.2 PDF is available
online with the 6.0 documentation.
The migration process creates a service named Infrastructure in the target system. Enabled blueprints
are published to this service during migration. You can add services after migration is finished.
An entitlement is created for each business group, in which all possible actions are listed and available.
Entitlements are also created for business groups based on access settings specified in blueprints that
belong to, or are associated with, that business group. If a blueprint's access is set to everyone, the
blueprint is added to the catalog and it is entitled for everyone in the associated business group. If a
blueprint's access is not set to everyone, the blueprint is added to the catalog and only entitled for the
designated members of the associated business group.
The following entitlements are created for each business group when an associated blueprint has no
restrictions on its security tab.
n
BusinessGroupName Group
n
BusinessGroupName Actions
An additional entitlement is created for each restricted blueprint, for example BusinessGroupName
BlueprintName Blueprint.
In addition to these basic entitlements that are created for every business group, an entitlement is created
for each restricted blueprint. For example, if Blueprint A is unrestricted and available to everyone in the
group and Blueprint B is restricted to a subset group of users in the Accounting department, an
entitlement is created that is available to everyone in the business group. Another entitlement is created
for, and only available to, the Accounting department subset of the group. If no unrestricted blueprints
exist, only the Group and Actions entitlements are created for the business group.
After migration, the tenant administrator can display entitlements by selecting Administration > Catalog
Management > Entitlements. Information about the entitlements is available on the Details and Items
and Approvals tabs.
Resource actions are added to the entitlements. Only the resource actions that are available for a user in
the business group are available for that user's resources, such as machines that the user has
provisioned or has the authority to provision. All resource actions are entitled.
Migrating vCloud Automation Center 5.2.3 to vRealize Automation 6.2
VMware, Inc. 16