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
5 Locate the machine to back up or snapshot.
6 Create the machine backup or machine snapshot.
Backing Up the Target vRealize Automation SQL
Database
Before you start the migration process, create a backup of the target vRealize Automation SQL database
using your preferred method of database backup.
For information about the required order of operations to be performed before you start migration, see
Chapter 4 Performing Manual Operations After Pre-Migration.
This task assumes that you are using the step sequence published by Microsoft to back up and restore a
SQL database by using Microsoft SQL Server Management Studio.
The procedure to back up and restore a SQL database is described in the following Microsoft Developer
Network documentation topics.
n
Back Up and Restore of SQL Server Databases
n
Create a Full Database Backup (SQL Server)
n
Restore a Database Backup (SQL Server Management Studio)
For more information about backing up the vRealize Automation SQL database, see System
Administration.
Disabling Access to the Source System
To prepare the source environment for maintenance mode, you can disable access to the administrative
and self-service portals by using an app_offline.htm file. This file prevents users from working in the
source vRealize Automation system during migration. It also informs users that the system is not
available.
Perform this task before migrating. For information about the required order of operations to perform
before you start migration, see Chapter 4 Performing Manual Operations After Pre-Migration.
For more information about creating and using an application offline file, see the To take a Web
application offline before deployment section of the How to: Prepare to Deploy a Web Project topic in
Microsoft Developer Network documentation. Also see the Easiest way to take your web site offline (IIS
6.0 or IIS 7.5 with .NET 4.0) blog post at the MSDN Blogs site.
The following example procedure is provided for reference only. Your app_offline.htm file content may
vary.
1 Log in to each machine on which you installed any of the source vCloud Automation Center 5.2
components with full Windows administrative access.
Migrating vCloud Automation Center 5.2.3 to vRealize Automation 6.2
VMware, Inc. 39