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
4 Replace the target vRealize Automation SQL database with the source vCloud Automation Center 5.2
SQL database using your preferred method.
The following example procedures are provided for reference purposes. Your procedure might vary.
n
Example - Replace SQL Database by Using Win2008 R2 SP1
n
Example - Replace SQL Database by Using Win2012
5 After you have replaced the database, restart the IIS service on the target Web site Host machine
before you start the migration task.
6 Verify that the Iaas Component services remain stopped while you run the migration task.
Example - Replace SQL Database by Using Win2008 R2 SP1
This sample procedure illustrates how to use Microsoft SQL Server Management Studio to restore a
database using Win2008 R2 SP1.
This example procedure is provided for reference purposes only. Your restore procedure may vary. For
information about when to use this sample procedure, see Replacing the Target vRealize Automation
Database with the Source vCloud Automation Center 5.2 Database.
Prerequisites
1 Shut down the source vCloud Automation Center 5.2 services. Do not shut down the Model Manager
Web Service.
2 Back up the vCloud Automation Center 5.2 database, for example DB52.
3 Shut down the target vRealize Automation services. Do not shut down the Model Manager Web
Service.
4 Back up the target vRealize Automation database, for example DB62.
5 Log in to Windows using your Domain or SQL administrator credentials.
Procedure
1 In Microsoft SQL Server Management Studio, right-click the DB62 database.
2 Select Tasks > Detach.
3 Check the Drop Connections check box and click OK.
4 In Microsoft SQL Server Management Studio, right-click the DB52 database folder name.
5 Select Tasks > Restore Database.
6 In Microsoft SQL Server Management Studio, display the General page.
7 Change the Destination database name to DB62 and keep the source database name as DB52.
8 In Microsoft SQL Server Management Studio, display the Options page.
9 Check the Overwite the existing database (WITH REPLACE) check box and click OK.
Migrating vCloud Automation Center 5.2.3 to vRealize Automation 6.2
VMware, Inc. 42