Run the commands in this procedure to migrate the vRealize Orchestrator server from your vRealize Automation 7.x source environment to vRealize Automation 7.3.

Prerequisites

  • For a minimal deployment, log in using SSH to the source vRealize Automation appliance as root.

  • For a high-availability deployment, log in using SSH to the master source vRealize Automation appliance as root.

Procedure

  1. Stop the vRealize Orchestrator server service.
    service vco-server stop
  2. Stop the vRealize Orchestrator Control Center service.
    service vco-configurator stop

    For a high-availability deployment, stop the vRealize Orchestrator server service and vRealize Orchestrator Control Center service on the master vRealize Automation appliance and on each replica appliance.

  3. Copy vro-config.zip from the source vRealize Automation appliance to the /tmp directory on the target vRealize Automation appliance. Before you run the command, replace SOURCE-VRA-APPLIANCE-HOST-NAME with the fully qualified domain name of the source vRealize Automation appliance. When prompted, enter the password for the source vRealize Automation appliance root user.
    scp root@SOURCE-VRA-APPLIANCE-HOST-NAME:/tmp/vro-config.zip /tmp/vro-config.zip
  4. Change the ownership of /tmp/vro-config.zip.
    chown vco:vco /tmp/vro-config.zip
  5. Import the configuration file to the embedded target vRealize Orchestrator server.
    /usr/lib/vco/tools/configuration-cli/bin/vro-configure.sh import --skipDatabaseSettings --skipLicense --skipSettings --skipSslCertificate --skipTrustStore --notForceImportPlugins --notRemoveMissingPlugins --path /tmp/vro-config.zip
    

    Import of Orchestrator Configuration finished successfully appears when the configuration file import succeeds.

    Note:

    If the import is successful, you can safely ignore any messages marked [ERROR] or [WARN] when you run this command.

  6. Migrate the source vRealize Orchestrator database to the PostgreSQL server running on the target vRealize Automation appliance. Before you run the command, replace SOURCE-VRA-APPLIANCE-HOST-NAME with the fully qualified domain name of the source vRealize Automation appliance and VRO-MIGRATION-USER-PASSWORD with the vro_migration user password that you created in the Temporarily Change the Configuration of the Source vRealize Automation Appliance procedure.
    /usr/lib/vco/tools/configuration-cli/bin/vro-configure.sh db-migrate --sourceJdbcUrl jdbc:postgresql://SOURCE-VRA-APPLIANCE-HOST-NAME:5432/vcac --sourceDbUsername vro_migration --sourceDbPassword VRO-MIGRATION-USER-PASSWORD
    
  7. Delete the old trusted certificates from the migrated database.
    sudo -u postgres -i -- /opt/vmware/vpostgres/current/bin/psql vcac -c "DELETE FROM vmo_keystore WHERE id='cakeystore-id';"
  8. Delete old vRealize Orchestrator nodes from the migrated database.
    sudo -u postgres -i -- /opt/vmware/vpostgres/current/bin/psql vcac -c "DELETE FROM vmo_clustermember;"
  9. Delete vro-config.zip from the /tmp directory.
    rm -rf /tmp/vro-config.zip
  10. Start the vRealize Orchestrator server service.
    service vco-server start

    For a high-availability deployment, start the vRealize Orchestrator server service only on the master vRealize Automation appliance.

What to do next

Reconfigure the Target Embedded vRealize Orchestrator to Support High Availability