You can run the pre-migration task as many times as necessary.

About this task

Important:

The objects that the pre-migration task creates in the target system are not functional until migration is finished. Refrain from using the target system until migration is finished.

You can recreate approval policies after pre-migration and before migration by using information in the pre-migration report. Otherwise, you can recreate approval policies after migration. For more information, see Recreating Approval Policies.

Rerun pre-migration in the following situations:

  • The pre-migration task did not finish successfully.

    You can restart the migration tool and rerun the pre-migration task.

  • The pre-migration task finished successfully.

    Open the pre-migration report and decide if you should rerun pre-migration. For example, if you added users after you started pre-migration, rerun pre-migration to capture those new users. When you are satisfied with the pre-migration report, perform the manual tasks that are required after pre-migration is finished and start the migration task.

  • Time elapsed between when you last ran pre-migration and when you are ready to run migration.

    As a general rule and to be sure that the latest data was collected by the pre-migration task, rerun pre-migration if more than one day elapsed since you last ran pre-migration.

  • You are satisfied with the pre-migration report but want to quiet the system before running a final pre-migration.

    The suggested practice is to run the pre-migration task once, review the report, make any necessary corrections, and rerun pre-migration. When you are satisfied with the pre-migration report results, perform the specified manual tasks to quiet the system and run pre-migration a final time. After you run the final pre-migration, replace the target database with the source 5.2 database and run migration. While this practice is more time consuming, it provides a higher confidence level in the migration readiness of the source system.

You might also need to remove database tables that the pre-migration task added to the source 5.2 database before you can successfully rerun pre-migration. For information about removing tables from the source database that were added by the pre-migration task, see Cleaning Up Migration Tables in Source 5.2 Database.

For related information, see Run the Pre-Migration Task.

Prerequisites

Run the migration tool from a target vRealize Automation system on which the Model Manager Web Service component is installed.

Procedure

  1. Log in as a domain administrator on an IaaS system on which the target vRealize Automation system's Model Manager Web Service is installed.
  2. Run the vCACMigration.exe migration tool.

    The vCACMigration.exe file is located in the subfolder that was created when you ran the vCACMigrationTool.exe self-extracting executable file. The default location is C:\Program Files (x86)\VMWare\vCACMigration.

  3. Follow the prompts to the Migration Tasks page.
  4. Click Pre-migration on the Migration Tasks page and click Next.
  5. Enter information for the source vCloud Automation Center 5.2 Model Manager Web Service.

    If you specify a port value other than the default, you may need to manually update a migration table value after the pre-migration task is finished.

  6. Accept information for the source vCloud Automation Center 5.2 database and click Next.

    The source database text box is pre-populated with content from the source page.

  7. Enter information for the target vRealize Automation Model Manager Web Service.

    If you specify a port value other than the default, you may need to manually update a migration table value after the pre-migration task is finished.

  8. Enter information for the target vRealize Automation database.
    1. Enter the target SQL database server name in the Database server field.
    2. Enter the target SQL database name in the Database name field.
    3. Select Windows or SQL authentication.

      If you selected SQL authentication, enter the SQL database administrator credentials.

  9. Click Next.
  10. Enter the security passphrase or encryption key for the source database.

    This is the security passphrase or encryption key that was used when vCloud Automation Center 5.2 was installed. If you do not know the passphrase or encryption key, you can click the Retrieve the Encryption Key link to open the supplied instructions.

    • Click Enter passphrase, enter the passphrase, and click Test.

      • If the passphrase is valid, click Next.

      • If the passphrase is invalid, click Enter encryption key.

    • Click Enter encryption key, enter the encryption key, and click Test.

      • If the encryption key is valid, click Next.

      • If the encryption key is invalid, retrieve and enter a valid key.

  11. Click Load to display a list of users who have been given administrator access to the default vsphere.local tenant.
  12. Select an administrator name from the list of names.

    If you manually enter a user name, specify an individual administrator name such as jsmith@mycompany.com, rather than an administrator group name. The administrator name administrator@vsphere.local is not a valid entry.

  13. Click Next.
  14. Review the Ready to Run Pre-Migration screen and click Start.
  15. When the pre-migration task is finished, click View detailed report to open and review the pre-migration report.
  16. Review the list of tasks that must be performed after pre-migration is complete.
  17. Click the linked documentation topic to display information about how to perform the required manual tasks.
  18. Click Finish.

What to do next

  1. Review the pre-migration report. See Using the Pre-Migration Report and Logs.

  2. If necessary, resolve any outstanding issues and rerun pre-migration. See Rerun the Pre-Migration Task.

  3. Review the list of tasks that must be performed after pre-migration is finished.

  4. When you are satisfied with the content of the pre-migration report, perform the listed manual tasks. See Performing Manual Operations After Pre-Migration.