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
vCACMigration-Error.log
The vCACMigration-Error.log file contains errors that are related to the migration tool itself.
Rerun the Pre-Migration Task
You can run the pre-migration task as many times as necessary.
Important The objects that the pre-migration task creates in the target system are not functional until
migration is finished. Refrain from using the target system until migration is finished.
You can recreate approval policies after pre-migration and before migration by using information in the
pre-migration report. Otherwise, you can recreate approval policies after migration. For more information,
see Recreating Approval Policies.
Rerun pre-migration in the following situations:
n
The pre-migration task did not finish successfully.
You can restart the migration tool and rerun the pre-migration task.
n
The pre-migration task finished successfully.
Open the pre-migration report and decide if you should rerun pre-migration. For example, if you
added users after you started pre-migration, rerun pre-migration to capture those new users. When
you are satisfied with the pre-migration report, perform the manual tasks that are required after pre-
migration is finished and start the migration task.
n
Time elapsed between when you last ran pre-migration and when you are ready to run migration.
As a general rule and to be sure that the latest data was collected by the pre-migration task, rerun
pre-migration if more than one day elapsed since you last ran pre-migration.
n
You are satisfied with the pre-migration report but want to quiet the system before running a final pre-
migration.
The suggested practice is to run the pre-migration task once, review the report, make any necessary
corrections, and rerun pre-migration. When you are satisfied with the pre-migration report results,
perform the specified manual tasks to quiet the system and run pre-migration a final time. After you
run the final pre-migration, replace the target database with the source 5.2 database and run
migration. While this practice is more time consuming, it provides a higher confidence level in the
migration readiness of the source system.
You might also need to remove database tables that the pre-migration task added to the source 5.2
database before you can successfully rerun pre-migration. For information about removing tables from
the source database that were added by the pre-migration task, see Cleaning Up Migration Tables in
Source 5.2 Database.
For related information, see Run the Pre-Migration Task.
Prerequisites
n
Run the pre-migration task. See Run the Pre-Migration Task.
Migrating vCloud Automation Center 5.2.3 to vRealize Automation 6.2
VMware, Inc. 33