You can use the automatic migration process to migrate your vRealize Automation 6.2.x deployment to 7.1 using automatic IaaS database cloning.

About this task

Although this procedure automates most of the migration process, successful migration depends on the following conditions:

  • The Model Manager node must have good connectivity with the source and target Microsoft SQL Servers. Networks with low bandwidth can time out while transferring a huge amount of data between the servers.

  • The source and target Microsoft SQL Servers must be in the same domain.

  • The target Microsoft SQL Server IaaS database logins must be the same as the logins configured in the source Microsoft SQL Server IaaS database.

Procedure

  1. Obtain the encryption key from your vRealize Automation 6.2.x deployment.
    1. Run the following command in an administrative command prompt on the virtual machine that hosts active Manager service to obtain the encryption key .

      C:\Program Files (x86)\VMware\vCAC\Server\ConfigTool\EncryptionKeyTool\DynamicOps.Tools.EncryptionKeyTool.exe" key-read -c "C:\Program Files (x86)\VMware\vCAC\Server\ManagerService.exe.config" -v

      If your installation directory is not in the default location, C:\Program Files (x86)\VMware\vCAC, you must edit the path to your own installation directory.

    2. Copy and save the key that appears after you run the command.

      The key is a long string of characters that looks similar to this:

      NRH+f/BlnCB6yvasLS3sxespgdkcFWAEuyV0g4lfryg=

  2. In your target vRealize Automation 7.1 environment, open the management console for your virtual appliance by using its fully qualified domain name: https://va-hostname.domain.name:5480.
  3. Log in with the user name root and the password you specified when the appliance was deployed.
  4. Select vRA Settings > Migration.
  5. Ensure the Auto Clone Source IaaS DB check box is selected.
  6. Select or deselect the Enable SSO2 migration check box according to how you migrated your tenants and identity stores.
  7. Enter the requested information for Source vRA SSO2 Appliance.

    Option

    Description

    Host name

    Host name for the source vRealize Automation 6.2.x SSO2 Identity Server.

  8. Enter the requested information for Source vRA Appliance.

    Option

    Description

    Host name

    Host name for the vRealize Automation 6.2.x appliance.

    Root username

    root

    Root password

    Root password that you entered when you deployed the vRealize 6.2 appliance.

    Re-enter password

    Re-enter root password.

  9. Enter the requested information for the Target vRA Appliance

    Option

    Description

    Default tenant

    Tenant you created when you configured single sign-on in the installation wizard, for example, vsphere.local.

    Administrator username

    Default tenant administrator user name that you entered when you deployed the vRealize 7.1 appliance, for example, administrator@vsphere.local.

    Administrator password

    Administrator password that you entered when you deployed the vRealize 7.1 appliance.

    Re-enter password

    Re-enter administrator password.

    Root username

    root

    Root password

    Root password that you entered when you deployed the vRealize 7.1 appliance, for example.

    Re-enter password

    Re-enter root password.

  10. Enter the requested information for the Source vRA IaaS Database Server.

    Option

    Description

    Database Host Name

    Name of the vRealize Automation 6.2.x IaaS Microsoft SQL database host.

    Database Name

    Name that you entered when you deployed the vRealize Automation 6.2.x appliance. The default name is vCAC..

    Encryption Key

    Encryption key string from your source vRealize Automation 6.2.x deployment.

    Database Security

    SQL Server authentication mechanism. Select Windows Authentication or SQL Authentication. If you select SQL Authentication, you must enter a user name and password.

    If the vRealize Automation 6.2.x database and the 7.1 database are on different domains, Windows authentication fails.

  11. Enter the requested information for the Target vRA IaaS Database Server.

    Option

    Description

    Database Host Name

    Name of the vRealize Automation 7.1 IaaS Microsoft SQL database host.

    New Database Name

    Name of the new database that you are migrating to.

    Create Database

    Accept default selection.

    Passphrase

    New passphrase to re-encrypt sensitive content stored in migrated Microsoft SQL database. A passphrase is a series of words used to generate an encryption key to protect data while at rest in the database, such as endpoint credentials. You use this passphrase each time you install a new component.

    Database Security

    SQL Server authentication mechanism. Select Windows Authentication or SQL Authentication. If you select SQL Authentication, you must enter a user name and password .

    If the vRealize Automation 6.2.x database and the 7.1 database are on different domains, Windows authentication fails.

  12. Click Migrate.

    Migration Status shows the migration progress and displays a message when migration is finished.

    More migration details are contained in the following log files. You can tail these log files to observe the migration progress.

    • vRealize Automation 6.2.x virtual appliance: /var/log/vcac/migration-package.log

    • vRealize Automation 7.1 virtual appliance: /var/log/vcac/migrate.log

    • Iaas nodes: C:\Program Files (x86)\VMware\vCAC\InstallLogs-YYYYMMDDHHMMSS\Migrate.log

      The installation directory for the IaaS nodes might be in a non-default location.

  13. When migration finishes, submit your vRealize Automation 7.1 license key.
    1. On the management console, click Licensing.
    2. Enter your vRealize Automation 7.1 license key in the New License Key text box.
    3. Click Submit Key.
  14. If you are migrating to a clustered environment, access the management console on each secondary node and join the secondary node to the master node.
    1. Select vRA Settings > Cluster.
    2. Click Join Cluster.
  15. If you are migrating to a clustered environment, configure each secondary node in the load balancer.

What to do next

Validate the vRealize Automation Migrated Environment