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
Cause
The network is disabled.
Solution
Restart the network.
Cannot Create Application Services Reservation
An error occurs during the vRealize Automation pre-migration task while creating an Application Services
reservation for a business group.
Problem
The pre-migration task reports a problem while preparing to create an Application Services reservation for
a business group.
A sample pre-migration report entry is as follows.
Failed to create AppService reservation for provisioning group MyGroupName.
Provisioning multi-machine blueprints might fail for this provisioning group after migration.
Cause
The dbo.Host table in the source database is missing a required value for the AppService Host record. It
is not clear what causes this occasional problem.
A sample of a complete AppService Host record is as follows.
n
HostID - FBE1198E-2B65-42FB-8437-4942DAD514A2
n
HostName - AppService Host
n
IsVRMManaged - 1
n
MachineType - 3
Solution
1 Open the source database.
2 Navigate to the dbo.Host table.
3 Enter the AppService Host name in the dbo.Host table.
4 Enter the HostID name if it is not already specified in the table.
5 Enter the IsVRMManaged value if it is not already specified in the table.
6 Enter the MachineType value if it is not already specified in the table.
7 Close the source database.
8 Rerun the pre-migration task.
The pre-migration task is successful.
Migrating vCloud Automation Center 5.2.3 to vRealize Automation 6.2
VMware, Inc. 59