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
Migration Fails with a RepoUtil Assembly Timeout Error
vRealize Automation migration fails if the RepoUtil utility phase of IaaS assembly upgrade does not
complete within the specified timeout period.
Problem
The upgrade phase of migration fails because the IaaS assembly upgrade utility did not finish in the
specified timeout period. To correct the situation, increase the timeout period.
A sample timeout error message is as follows.
2014-09-18 10 43 07 843 :Started running command %AppData%\..\Local\Temp\vCAC-
IaaS\version\RepoUtil.exe Assembly-Install -f %AppData%\..\Local\Temp\vCAC-
IaaS\version\DynamicOps.UcsModel.Interface.dll" -v 2014-09-18 10 46 32
104 :System.Net.WebException: The operation has timed out 2014-09-18 10 46 32 104 :
at System.Net.HttpWebRequest.GetResponse() . . . 2014-09-18 10 46 32 104 :Warning:
Non-zero return code. Command failed. 2014-09-18 10 46 32 120 :Failed to deploy file
DynamicOps.UcsModel.Interface.dll 2014-09-18 10 46 32 120 :Failed to deploy
repository.
Cause
The timeout setting for the Repoutil utility is not long enough to allow all IaaS assemblies to be upgraded.
To correct the problem, increase the timeout setting value (in seconds) in the configuration file and rerun
migration.
Solution
You can increase the timeout value to address the problem. 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 RepoUtil.exe.config file for editing.
2 Find the repositoryTimeout line.
3 Set a new timeout value, for example 10 minutes specified as <add key="repositoryTimeout"
value= "600" /> or 30 minutes, specified as <add key="repositoryTimeout" value=
"1800" />.
4 Save and close the RepoUtil.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.
Machines Not Visible on Items Page After Migration
After migration, migrated machines are visible using the Infrastructure tab but are not visible using the
Items tab.
Migrating vCloud Automation Center 5.2.3 to vRealize Automation 6.2
VMware, Inc. 63