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
Deployment customizations, including
custom workflows, events, built-in stubs,
plug-ins, email customizations, and so on
No Record all customization information
before migrating. Consider uninstalling
customizations before starting the
migration process. If you received
customization packages from VMware or
from a third party, and you still want to use
the customizations after migration, check
with the contact who authored the
customizations to request updated
versions.
Branding graphics No You can recreate branding graphics in the
target system before or after you run the
migration task.
Blueprint icons No See Migrating Blueprints.
Licenses No
Local machine users and built-in users No
Approval policies No Approval policies are not migrated but a
generic approval policy is created in the
target system. See Migrating Approval
Policies.
You can recreate approval policies in the
target system before or after you run the
migration task. See Recreating Approval
Policies.
Guest agent ISO settings or Guest agent
vRealize Automation management
addresses
No See Migrating DEM and Agent Information
and Recreating ISOs and Templates That
Contain a Guest Agent.
Email settings, including email
customizations
No Email configuration settings do not
migrate. Recreate email configuration and
settings when migration finishes. For
information, see Recreating Email
Notifications.
Notifications No Notification settings do not migrate.
Recreate notification settings when
migration finishes. For information, see
Recreating Email Notifications.
Active or pending requests and approvals
including reconfiguration, leasing, and
reclamation
No Allow all workflows and pending actions to
complete before you start the migration
task.
Migrating Users and Groups
You can migrate users, roles, groups, and other user-related data.
If you make changes to users, groups, or permissions while pre-migration is running, those changes
might not be processed. Rerun pre-migration to include those changes.
Migrating vCloud Automation Center 5.2.3 to vRealize Automation 6.2
VMware, Inc. 11