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
Problem
Migrated machines are not provisioned or available for management in the migrated target system, as
evidenced by their lack of display on the Machines page on the Items tab.
Cause
This problem most commonly occurs if you migrate to one system and then migrate to another without
first deleting the stale migration tables that were created by the initial migration. For related information,
see Migrating to One Target System and Then to Another.
To delete the stale migration tables, see Cleaning Up Migration Tables in Source 5.2 Database.
Solution
1 Delete the stale migration tables from the source database.
2 Perform the pre-migration and migration procedure from the beginning.
Reservation Not Available After Migration
After migration, an error occurs during machine provisioning if the multi-machine blueprint does not have
a transport zone value specified on the associated reservation.
Problem
The following error message appears after vRealize Automation migration is finished and during machine
provisioning from the migrated system.
No reservation available for network scope with name.
Cause
The reservation associated to a multi-machine blueprint does not contain a transport zone value.
For information about specifying a transport zone value and network information for a multi-machine
blueprint, see IaaS Integration for Multi-Machine Services in vRealize Automation documentation.
Solution
Add a transport zone value to the migrated vCloud Networking and Security reservations that are
associated to multi-machine blueprints. The transport zone setting was not available in
vCloud Automation Center 5.2.
Migrating vCloud Automation Center 5.2.3 to vRealize Automation 6.2
VMware, Inc. 64