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
Database Name Mismatch During Pre-Migration
A warning appears if the vRealize Automation database name you specify does not match the name in
the Model Manager Web Service configuration file.
Problem
A database mismatch error appears during vRealize Automation pre-migration.
Warning: There is a mismatch between the database name entered:
“database_name_entered” and the database name in the Model Manager Web Service
configuration file: “database_name”. Enter the database name that is specified in
the configuration file.
Cause
The target vRealize Automation SQL database name that you specified does not match the SQL
database name in the Model Manager Web Service configuration file.
The target vRealize Automation SQL database name that you specify during pre-migration must match
the database name that appears in the target Model Manager Web Service configuration file.
Solution
Enter the database name that is specified in the configuration file. See Run the Pre-Migration Task.
User Principals Cannot be Migrated
The pre-migration report indicates that user principal names cannot be migrated or that domain trust
issues exist between the source and target systems.
Problem
One or more domain users fails to resolve from their source account identifier to a target user principal
name. The pre-migration report displays the following messages to describe the problem and offer
problem resolutions.
n
Fatal Error – No users are migrated and pre-migration suspended.
Command ExtractUPN failed. Error: 'Users cannot be uploaded to the repository.
Verify that the administrator who is running pre-migration has domain access to
the source and target systems.
n
Warning – A single instance of a user failed to migrate.
Failed to resolve user principal with Sid
S-1-5-21-0000000000-0000000000-0000000000-0000 and account name DOMAIN\Username.
This user principal will not be migrated. If you see multiple instances of this
error, verify that you are running the migration tool from a machine that is
joined to the same domain as the machine on which the source 5.2 server is
installed.
Migrating vCloud Automation Center 5.2.3 to vRealize Automation 6.2
VMware, Inc. 56