Instead of upgrading your cluster of vRealize Orchestrator 7.0.x, 7.1 or 7.2 instances to 7.3, you can migrate the configuration to an Orchestrator node that is already installed on version 7.3 and join other newly installed Orchestrator 7.3 nodes to the new cluster.

Prerequisites

  • Set up a load balancer to distribute traffic among multiple instances of vRealize Orchestrator. For more information, see vRealize Orchestrator Load Balancing.

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

  • Stop the Orchestrator server service of the source Orchestrator instances.

  • Back up the database, including the database schema, of the external Orchestrator.

    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. Export the configuration from one of the nodes in the source Orchestrator cluster.
    1. Log in to Control Center as root or as an administrator, depending on the source version.
    2. On the Export/Import Configuration page, select the type of files you want to export.
      Note:

      If you select Export plug-in configurations and the plug-in configurations contain encrypted properties, you must also select Export server configuration to successfully decrypt the data when importing.

    3. (Optional) : Enter a password to protect the configuration file.

      Use the same password when you import the configuration later.

    4. Click Export.

    Orchestrator creates an orchestrator-config-export-hostname-dateReference.zip file that is downloaded on your local machine. You can use this file to clone or to restore the system.

  2. Import the configuration to the target Orchestrator instance.
    1. Log in to Control Center as an administrator.
    2. Click Export/Import Configuration and navigate to the Migrate Configuration tab.
    3. Browse to and select the .ZIP file that you exported from your previous installation.
    4. Enter the password that you used when exporting the configuration.

      Leave blank if you did not export the configuration with a password.

    5. Click Import.
    6. Select the type of files you want to import.
      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 Finish Migration.

      A message states that the configuration is successfully imported. The Orchestrator server service of the target Orchestrator instance restarts automatically.

  3. Reconfigure the Orchestrator cluster.
    1. Open the advanced Orchestrator Cluster Management page, at https://your_orchestrator_server_IP_or_DNS_name:8283/vco-controlcenter/#/control-app/ha?remove-nodes.
    2. Select the check boxes next to the source Orchestrator nodes and click Remove.

      Refresh the browser page by clicking the F5 button on the keyboard.

  4. 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.

  5. Verify that Orchestrator is configured properly at the Validate Configuration page in Control Center.
  6. Deploy a new Orchestrator instance on the upgraded version.
  7. Join the instance to the vRealize Orchestrator 7.3 node.

    For more information, see Configuring an Orchestrator Cluster.

  8. (Optional) : Repeat Step 6 and Step 7 for each node you are adding to the cluster.

Results

You successfully migrated a cluster of vRealize Orchestrator 7.0.x, 7.1 or 7.2 instances to vRealize Orchestrator 7.3.

What to do next

  • On the Orchestrator Cluster Management page, make sure that the Active Configuration Fingerprint and the Pending Configuration Fingerprint strings on all nodes in the cluster match.

    Note:

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

  • Verify that the vRealize Orchestrator cluster is configured properly by opening the Validate Configuration page in Control Center.

  • Log in to the Orchestrator client and verify whether the configurations of all installed plug-ins are correct.