You can migrate an external standalone vRealize Orchestrator 7.x instance to a vRealize Orchestrator 8.x environment. Migration is supported for vRealize Orchestrator 7.x instances authenticated with vSphere or with vRealize Automation 7.x.

Important: Upgrading vRealize Orchestrator 7.x or earlier to vRealize Orchestrator 8.x is not supported.
The migration transfers an external standalone vRealize Orchestrator 7.x configuration to your vRealize Orchestrator 8.x environment. The migration involves overwriting all existing elements in your vRealize Orchestrator 8.x environment, such as workflows, actions, configuration and resource elements, including secure strings in workflows and configuration elements, packages, tasks, policies, certificates and trusted certificates, plug-ins and plug-in configurations, custom records in the the js-io-rights.conf file, Control Center system properties. The migration of vRealize Orchestrator instances authenticated with vSphere also includes the state of currently running entities, such as workflow execution tokens, scheduled tasks, policy runs. For vRealize Orchestrator instances authenticated with vRealize Automation, the currently running entities appear in a failed state in the target vRealize Orchestrator environment. The migration includes both built-in and custom vRealize Orchestrator content.
Note: Migration of clustered vRealize Orchestrator 7.x deployments to vRealize Orchestrator 8.x is not supported. You can migrate the primary node of your clustered deployment by stopping the services of the replica nodes before you run the migration script. 
service vco-server stop
service vco-configurator stop
You perform the migration by using the vro-migrate command on the vRealize Orchestrator appliance.
Note: The migration script stops the vRealize Orchestrator services automatically.

Prerequisites

  • Migration is supported for vRealize Orchestrator 7.3 or later.
  • Download and deploy a vRealize Orchestrator 8.x environment. See Download and Deploy the vRealize Orchestrator Appliance in Installing and Configuring VMware vRealize Orchestrator.
  • Configure the authentication provider of your target vRealize Orchestrator environment. The authentication provider of the source vRealize Orchestrator instance is not migrated. See Configuring a Standalone vRealize Orchestrator Server in Installing and Configuring VMware vRealize Orchestrator.
  • Back up the target vRealize Orchestrator environment.
  • Verify that SSH access is enabled on the source vRealize Orchestrator instance and target vRealize Orchestrator environment. See Activate or Deactivate SSH Access to the vRealize Orchestrator Appliance in Installing and Configuring VMware vRealize Orchestrator.
  • Verify that the source vRealize Orchestrator database is accessible from the target vRealize Orchestrator environment.

Procedure

  1. Log in to the vRealize Orchestrator appliance command line of your target environment over SSH as root.
  2. To start the migration, run the vro-migrate command.
  3. Follow the command prompts to provide the fully qualified domain name (FQDN) and credentials of the source vRealize Orchestrator instance.
  4. (Optional) To follow the migration progress, access the migration log:
    1. Log in to your target vRealize Orchestrator appliance command line over a separate SSH session as root.
    2. Run the tail -f /var/log/vmware/prelude/vro-migration.log command.
      Note: The name of the migration log file includes the date and time of when the migration log is generated. 
      vro-migration-YYYY-MM-DD-HH-MM-SS.log
  5. (Optional) If you want to access your source vRealize Orchestrator 7.x environment after migration, restart the vco-server and vco-configurator services on the source system.

Results

The migration process begins. You receive a notification on the target vRealize Orchestrator appliance when the migration finishes.