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
The pre-migration task generates and populates the pre-migration report. The migration tool provides a
link to the report when pre-migration is finished. View the report to determine your readiness to migrate.
The pre-migration report, PreMigration.html, is generated in the reports subdirectory of the directory
in which you downloaded and extracted the migration tool.
Each time you run pre-migration, the migration tool renames the PreMigration.html report by
appending the date and time at which the report was generated, for example as
PreMigration2014_August_20-17_53_47.html. It then generates a new report named
PreMigration.html.
The pre-migration report includes the following information.
n
Fabric and business group names
n
Blueprint names
n
Entitlements
n
Agents, DEMs, and endpoints associated with agents
n
Deployment customizations such as custom operations, workflows, and events
n
Pending approval requests, reclamation requests, and workflows
n
Approvals that you can manually recreate in the target system
You can use information in the pre-migration report to recreate approval policies in the target system
before or after migration.
n
User principal names that can migrate successfully
n
Warnings indicating user principal names that cannot be migrated
n
Warnings indicating that the fully qualified domain name for the server is different between the source
and target systems
Pre-Migration Log Files
The migration tool generates the following log files in the Program Files
(x86)\VMware\vCACMigration\Logs folder.
n
Migration.log
The Migration.log file contains information gathered during pre-migration and migration, including
generated warnings and errors.
n
Migration-Error.log
The Migration-Error.log file contains error messages that are generated during pre-migration and
migration.
n
vCACMigration.log
The vCACMigration.log file contains information about the migration tool itself.
Migrating vCloud Automation Center 5.2.3 to vRealize Automation 6.2
VMware, Inc. 32