Use this procedure to migrate the VMware vRealize ™ Orchestrator ™ server from your VMware vRealize ™ Automation 7.2 source environment to vRealize Automation 7.3.

Prerequisites

  • For a minimal deployment, open an SSH console session to the target vRealize Automation appliance as root user.

  • For a high-availability deployment, open an SSH console session to the master target vRealize Automation appliance as root user.

Procedure

  1. Run this command to stop the vRealize Orchestrator server service.
    service vco-server stop
  2. Run this command to 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. Run this command to copy vro-config.zip from the source vRealize Automation appliance to the /tmp directory on the target vRealize Automation appliance. When prompted, enter the password for the source vRealize Automation appliance root user. Before you run the command, replace {SOURCE-VRA-APPLIANCE-HOSTNAME} with the fully qualified domain name of the source vRealize Automation appliance.
    scp root@{SOURCE-VRA-APPLIANCE-HOSTNAME}:/tmp/vro-config.zip /tmp/vro-config.zip
  4. Run this command to change the ownership of /tmp/vro-config.zip.
    chown vco:vco /tmp/vro-config.zip
  5. Run this command to 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
    
  6. Run this command to 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-HOSTNAME} with the fully qualified domain name of the source vRealize Automation appliance and {VRO-MIGRATION-USER-PASSWORD} with the vro_migration user password.
    /usr/lib/vco/tools/configuration-cli/bin/vro-configure.sh db-migrate --sourceJdbcUrl jdbc:postgresql://{SOURCE-VRA-APPLIANCE-HOSTNAME}:5432/vcac --sourceDbUsername vro_migration --sourceDbPassword {VRO-MIGRATION-USER-PASSWORD}
    
  7. Run this command to 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. Run this command to 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. Run this command to delete vro-config.zip from the /tmp directory.
    rm -rf /tmp/vro-config.zip
  10. Run this command to 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