You can migrate your existing vRealize Orchestrator 6.x Virtual Appliance to Orchestrator 7.3 by exporting the configuration from the source Orchestrator instance and importing it to a new Orchestrator Appliance that is already installed on version 7.3.

Prerequisites

  • Deploy and configure an Orchestrator node on the target version. See Configuring a Standalone Orchestrator Server.

  • If the source Orchestrator uses a SHA1 package-signing certificate, make sure to regenerate the certificate using a stronger signing algorithm.

  • Stop the source and target Orchestrator servers.

  • Back up the database of the source Orchestrator server, including the database schema.

    Note:

    If you plan to use the source Orchestrator environment until the new one is fully configured, create a copy of the source database. Otherwise, you can configure the target Orchestrator to use the same database but in that case the source Orchestrator environment will no longer work because the database schema is upgraded to the version of the target Orchestrator.

Procedure

  1. Download the migration tool from the target Orchestrator server to the source Orchestrator.
    1. Log in to the vRealize Orchestrator 6.x Virtual Appliance over SSH as root.
    2. Under the /var/lib/vco directory, run the scp command to download the migration-tool.zip archive.
      scp root@vro-va-hostname.domain.name:/var/lib/vco/downloads/migration-tool.zip ./
    3. Run the unzip command to extract the migration tool archive.
      unzip migration-tool.zip
  2. Export the Orchestrator configuration from the source Orchestrator server.
    1. In the /var/lib/vco/migration-cli/bin directory, run the export command.
      ./vro-migrate.sh export

      This command combines the VMware vRealize Orchestrator configuration files and plug-ins into an export archive.

      An archive with file name orchestrator-config-export-orchestrator_ip_address-date_hour.zip is created in the /var/lib/vco folder.

  3. On the target VMware vRealize Orchestrator, back up the catalina.properties, server.xml, and web.xml files in the /etc/vco/app-server and /etc/vco/configuration directories.

    For example:

    cp catalina.properties catalina.properties-$(date +%Y-%m-%d_%H-%M-%S)
  4. On the target VMware vRealize Orchestrator, back up the setenv.sh file in the /usr/lib/vco/app-server/bin and /usr/lib/vco/configuration/bin directories.

    For example:

    cp setenv.sh setenv.sh-$(date +%Y-%m-%d_%H-%M-%S)
  5. Import the configuration to the target Orchestrator server.
    1. Log in to Control Center as an administrator.
    2. Open Export/Import Configuration in Control Center and click the Migrate Configuration tab.
    3. Browse to the exported configuration file and click Import.
    4. Select the type of files that you want to import.

      Option

      Description

      Migrate database settings

      Uses the database of the vRealize Orchestrator 6.x cluster.

      Note:

      If the source and target Orchestrator servers are not configured to use the same external database, leave the Migrate database settings check box unselected to avoid upgrading the database schema to the newer version. Otherwise the source Orchestrator environment stops working.

      You must configure the database that the target Orchestrator will use before the migration.

      Migrate plug-ins

      Migrates all plug-ins that are not included in the Orchestrator platform.

      Migrate legacy plug-in configurations

      Migrates the configuration of plug-ins that is stored in the /var/lib/vco/app-server/conf/plugins folder.

      Migrate trusted certificates

      Migrates all certificates from the trust store of the vRealize Orchestrator 6.x cluster.

    5. Click Finish Migration.

      A message indicates that the migration completed successfully.

    The Orchestrator server service restarts automatically.

  6. Stop the Orchestrator server service and the Control Center service of the target Orchestrator.
    service vco-configurator stop && service vco-server stop
  7. Replace the catalina.properties, server.xml, and web.xml files from the imported configuration with the backup copies you created in Step 3.

    For example:

    mv catalina.properties-date_hour catalina.properties
    1. Change the ownership of the files to the vco user.

      For example:

      chown vco:vco catalina.properties
  8. Replace the setenv.sh file from the imported configuration with the backup copies you created in Step 4.

    For example:

    mv setenv.sh-date_hour setenv.sh
    1. Change the ownership of the files to the vco user.

      For example:

      chown vco:vco setenv.sh
  9. Start the Orchestrator server service and the Control Center service of the target Orchestrator.
    service vco-configurator start && service vco-server start
  10. On the Startup Options page, make sure that the Active Configuration Fingerprint and the Pending Configuration Fingerprint strings match.
    Note:

    You might need to refresh the page several times until the two strings match.

  11. Verify that Orchestrator is configured properly at the Validate Configuration page in Control Center.

Results

You successfully migrated a vRealize Orchestrator 6.x Virtual Appliance to VMware vRealize Orchestrator 7.3.