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

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. The recommended signing algorithm is SHA2.
  • Stop the Orchestrator server service on both the source and the target Orchestrator instances.
  • Back up the source Orchestrator database, including the database schema.
    Note: If you plan to preserve the source Orchestrator environment after migration, clone the source Orchestrator database to another database. Afterwards, configure the target Orchestrator to use the cloned instance, instead of the instance configured during installation. If you skip this step, the target Orchestrator will upgrade the source Orchestrator database and it will no longer work with the source Orchestrator environment.

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.
      Note: You can ignore SLF4J error messages when running the export command.
  3. Import the configuration to the target Orchestrator instance.
    1. Log in to Control Center as root.
    2. Open Export/Import Configuration in Control Center and click the Import Configuration tab.
    3. Browse to and select the .ZIP file exported from the source Orchestrator instance.
    4. Enter the password that you used when exporting the configuration.
      Leave blank if you did not export the configuration with a password.
    5. Select the import type.
    6. If you are importing the configuration to an external Orchestrator server, choose whether to import the database settings.
      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.

    7. Click IMPORT to finish the migration.
      A message states that the configuration is successfully imported. The Orchestrator server service of the target Orchestrator instance restarts automatically.

Results

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

What to do next

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