Migrate your source vRealize Orchestrator 6.x Windows configuration to a target vRealize Orchestrator 7.6 environment.

Prerequisites

  • Deploy and configure your new vRealize Orchestrator 7.6 environment. For more information, see Installing and Configuring VMware vRealize Orchestrator.
  • If the source vRealize Orchestrator uses an SHA1 package-signing certificate, regenerate the certificate using a stronger signing algorithm, such as SHA2.
  • Enable SSH access for each node in your target vRealize Orchestrator environment.
  • Verify that the source vRealize Orchestrator database is accessible from the target vRealize Orchestrator environment.
  • Stop the vRealize Orchestrator server service on the source and target vRealize Orchestrator instances.
  • Back up the database, including the database schema, of the source vRealize Orchestrator server.

Procedure

  1. Download the migration tool from your target vRealize Orchestrator server.
    1. Log in to the Control Center as root.
    2. Open the Export/Import Configuration page and click the Import Configuration tab.
    3. Download the migration tool as specified in the description on the page, or download it directly from https://orchestrator_server_IP_or_DNS_name:8283/vco-controlcenter/api/server/migration-tool.
  2. If you are running a clustered vRealize Orchestrator deployment, stop the Control Center service on all replica nodes in the target vRealize Orchestrator environment.
    1. Open a new secure shell connection to each replica node.
    2. Stop the Control Center service
      service vco-configurator stop
    3. Logout and close the secure shell session.
  3. Export the source vRealize Orchestrator configuration.
    1. Upload and extract the downloaded migration tool archive in the vRealize Orchestrator Windows install folder.
      The default path to the vRealize Orchestrator installation folder in a Windows-based installation is C:\Program Files\VMware\Orchestrator.
    2. Ensure that the migration tool bin folder is orchestrator-install-folder\migration-cli\bin.
    3. Add the bin folder of the Java JRE installed with vRealize Orchestrator to the Windows PATH environment variable.
      The default path of the Java JRE bin folder installed with vRealize Orchestrator is C:\Program Files\VMware\CIS\jre\bin.
    4. Open the Windows command prompt and navigate to the migration tool bin folder.
      The default path to the migration tool bin folder is C:\Program Files\VMware\Orchestrator\migration-cli\bin.
    5. To export the vRealize Orchestrator configuration, run the migration command.
      vro-migrate.bat export
      An archive with the filename orchestrator-config-export-orchestrator_ip_address-date_hour.zip is created in the vRealize Orchestrator install folder. The vRealize Orchestrator configuration files and plug-ins are bundled into this archive.
  4. Import the source vRealize Orchestrator configuration to the target vRealize Orchestrator environment.
    1. Log in to the Control Center as root.
    2. Open the Export/Import Configuration page in Control Center and click the Import Configuration tab.
    3. Browse to and select the exported vRealize Orchestrator source configuration archive.
    4. (Optional) Enter the password that you used when exporting the configuration.
      Leave blank if you did not export the configuration with a password.
    5. Set the import type as External.
    6. Click Import.
      A message states that the configuration is successfully imported. The vRealize Orchestrator server service of the target vRealize Orchestrator instance restarts automatically.
    7. Stop the vRealize Orchestrator server service.
  5. Migrate the source vRealize Orchestrator database to the target vRealize Orchestrator environment.
    1. Open a new SSH connection and log in as root.
    2. Navigate to the vRealize Orchestrator configuration-cli folder.
      cd /usr/lib/vco/tools/configuration-cli/bin
    3. Run the migration command.
      ./vro-configure.sh db-migrate --sourceJdbcUrl JDBC_connection_URL --sourceDbUsername database_user --sourceDbPassword database_user_password
      Note: Enclose values that contain special characters in single quotation marks.

      The JDBC_connection_URL is stored in the vmo.properties file in your source vRealize Orchestrator environment. The default path to the vmo.properties file is C:\Program Files\VMware\Orchestrator\app-server\conf.

      The JDBC_connection_URL depends on the type of database that you use. The following examples show the JBDC_connect_URL format based on the configured database type:

      PostgreSQL: jdbc:postgresql://host:port/database_name
      MSSQL: jdbc:jtds:sqlserver://host:port/database_name\; if using SQL authentication and MSSQL: jdbc:jtds:sqlserver://host:port/database_name\;domain=domain\;useNTLMv2=TRUE if using Windows authentication.
      Oracle: jdbc:oracle:thin:@host:port:database_name 
  6. Restart the vRealize Orchestrator services in the target environment.
    1. Restart the vRealize Orchestrator server service.
    2. Restart the vRealize Orchestrator Control Center service.
  7. (Optional) If you are using a clustered vRealize Orchestrator environment, join the replica nodes to the cluster to synchronize the vRealize Orchestrator configuration.
    For more information, see Configure a Cluster of vRealize Orchestrator Instances in VAMI in Installing and Configuring VMware vRealize Orchestrator.

What to do next

To verify the vRealize Orchestrator configuration, follow the post migration steps.