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 4‑1. Manual Operations To Perform Before Starting the Migration Task (Continued)
Step sequence Operation to Perform Description of Operation
6 Disable access to the source system. See Disabling Access to the Source System.
7 Complete all workflows. Allow all workflows to finish.
The pre-migration report displays a warning for each
workflow that finished more than 24 hours ago. Before
you run the migration task, be sure that your
completed workflows are current. If they are not, finish
any open workflows and rerun pre-migration.
For information about viewing distributed execution
status and workflow history, see Viewing Distributed
Execution Status and Workflow History in the vCloud
Automation Center Operating Guide for 5.2.
8 Stop services on the source system. See Stop IaaS Services in Source vCloud Automation
Center 5.2 System.
9 Replace the target system database with the
source database.
See Replacing the Target vRealize Automation
Database with the Source vCloud Automation Center
5.2 Database.
10 If you specified a non-standard port value
during pre-migration, you must manually
update the migration table to include that port
value before you start the migration task. If
you specified port number 443 during pre-
migration, you do not need to perform this
manual step.
See Update Migration Table to Parse Port Value Data.
This chapter includes the following topics:
n
Stop IaaS Services in Target vRealize Automation System
n
Back Up the Target vRealize Automation System
n
Backing Up the Target vRealize Automation SQL Database
n
Disabling Access to the Source System
n
Stop IaaS Services in Source vCloud Automation Center 5.2 System
n
Replacing the Target vRealize Automation Database with the Source vCloud Automation Center 5.2
Database
n
Update Migration Table to Parse Port Value Data
Stop IaaS Services in Target vRealize Automation System
You must stop the target vRealize Automation IaaS services, except the Model Manager Web Service,
before you perform the migration. This includes stopping IaaS DEMs and agents.
The Model Manager Web Service must remain online during pre-migration and migration. For information
about the required order of operations to be performed before you start migration, see Chapter 4
Performing Manual Operations After Pre-Migration.
Migrating vCloud Automation Center 5.2.3 to vRealize Automation 6.2
VMware, Inc. 37