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
Solution
To use a script to update the database by correctly parsing the table entry, and allow the migration task to
correctly access the source database, see Update Migration Table to Parse Port Value Data.
After making the database update, you can re-run the migration task and proceed with migration.
Migration Fails with a Wait Operation Timeout Error
The vRealize Automation migration task does not finish and the migration log indicates that a wait
operation has timed out.
Problem
The migration task must finish in a specified amount of time or it fails with a timeout error. A sample
timeout error message is as follows.
Command Update-VmUsers failed. Error: 'System.Data.EntityCommandExecutionException:
An error occurred while executing the command definition. See the inner exception
for details. ---> System.Data.SqlClient.SqlException: Timeout expired. The timeout
period elapsed prior to completion of the operation or the server is not responding.
---> System.ComponentModel.Win32Exception: The wait operation timed out.
Cause
The migration task did not finish in the allocated amount of time. This might occur in an environment
where there are a large number of users to be migrated.
Solution
As a first course of corrective action, verify that your target SQL server is properly resourced according to
the reference architecture.
You can increase the timeout value to address the problem. The default timeout value is 10 minutes,
specified as 600 seconds in the migration.exe.config file. Use the following procedure to set a
different timeout value. After you have specified the value, restart the migration tool and rerun the
migration task.
1 Locate and open the migration.exe.config file.
2 Find the <add key="userMigrationCommandTimeout" value="600" /> line in the
<appSettings> section of the file.
3 Set a new timeout value, for example 30 minutes specified as <add
key="userMigrationCommandTimeout" value="1800" />.
4 Save and close the Migration.exe.config file.
5 Start the vCACMigration.exe migration tool.
6 Follow the prompts and click Migration on the Migration Tasks page to rerun the migration task.
Migrating vCloud Automation Center 5.2.3 to vRealize Automation 6.2
VMware, Inc. 62