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
Performing Manual Operations
After Pre-Migration 4
After you finish running pre-migration, you must perform certain manual operations before you start the
migration.
After you finish the pre-migration task and are satisfied with the results in the pre-migration report, use
this checklist to perform the required manual operations before you run the migration task.
For information about the pre-migration task, see Run the Pre-Migration Task.
For information about the migration task, see Run the Migration Task.
Important You can also perform these operations before you rerun the pre-migration task, with the
exception of the final task in which you replace the target system database with the source system
database. After you replace the target vRealize Automation database with the source
vCloud Automation Center 5.2 database you cannot rerun 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.
Table 4‑1. Manual Operations To Perform Before Starting the Migration Task
Step sequence Operation to Perform Description of Operation
1 Run data collection on each endpoint and
compute resource.
Allow data collection to run to completion to ensure
that all your data is collected for migration.
Running data collection on large endpoints can be
time consuming. Consider running data collection on
large endpoints only if you have not run data collection
in the last 24 hours.
2 Complete approval requests. Allow all approval requests to finish.
3 Stop services on the target system. See Stop IaaS Services in Target vRealize Automation
System.
4 Shut down and back up the target system. See Back Up the Target vRealize Automation System.
5 Create a backup of the source SQL database
if you have not already done so.
See Backing Up the vCloud Automation Center 5.2
Database.
VMware, Inc. 36