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
Using the Migration Report and Logs
The migration report contains information about the source and target systems. Information categories
include errors, warnings, and successes.
When you start the migration task you are prompted to run the prerequisites checker. The prerequisites
checker generates and populates the migration report. The migration tool provides a link to the report. To
determine your readiness to migrate, view the report before continuing with the migration.
The Migration.html migration report is generated in the reports subdirectory of the directory to which
you extracted the migration tool.
To support data collection, the prerequisite checker checks if the Microsoft Distributed Transaction
Coordinator (MSDTC) service is running and configured for local and remote SQL database instances
that use local or clustered MSDTC configurations.
The prerequisite checker outputs the following information in the migration report:
n
System information indicating whether the source and target Model Manager Web Services are
online, as is required
n
System information indicating whether the other source and target services are offline, as is required
n
Endpoints for which data was not collected in the last 24 hours
n
DEMs that are still running on the source system
n
Agents that might still be running on the source system
n
Pending source system requests, such as reclamation, approval, and machine requests that aren't
yet approved or denied
When the migration task is finished, click the migration report link to reopen the report and examine its
contents.
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. 47