After you upgrade your vRealize Automation from version 6.x to version 7.3, you can migrate your existing external Orchestrator 6.x Virtual Appliance to the Orchestrator server that is built into vRealize Automation 7.3.

About this task

Note:

If you have a distributed vRealize Automation environment with multiple vRealize Automation appliance nodes, perform the migration procedure only on the primary vRealize Automation node.

Prerequisites

  • Successful migration to vRealize Automation 7.3.

  • Stop the Orchestrator server service on the external Orchestrator.

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

Procedure

  1. Download the migration tool from the target Orchestrator server to the source Orchestrator.
    1. Log in to the vRealize Orchestrator 6.x Virtual Appliance over SSH as root.
    2. Under the /var/lib/vco directory, run the scp command to download the migration-tool.zip archive.
      scp root@vra-va-hostname.domain.name:/var/lib/vco/downloads/migration-tool.zip ./
    3. Run the unzip command to extract the migration tool archive.
      unzip migration-tool.zipy7
  2. Export the Orchestrator configuration from the source Orchestrator server.
    1. In the /var/lib/vco/migration-cli/bin directory, run the export command.
      ./vro-migrate.sh export

      This command combines the VMware vRealize Orchestrator configuration files and plug-ins into an export archive.

      An archive with file name orchestrator-config-export-orchestrator_ip_address-date_hour.zip is created in the /var/lib/vco folder.

  3. Migrate the exported configuration to the Orchestrator server that is built into vRealize Automation 7.3.
    1. Log in to the vRealize Automation appliance over SSH as root.
    2. Under the /usr/lib/vco/tools/configuration-cli/bin directory, run the scp command to download the exported configuration archive.
      scp root@orchestrator_ip_or_DNS_name:/var/lib/vco/orchestrator-config-export-orchestrator_ip_address-date_hour.zip ./
    3. Change the ownership of the exported Orchestrator configuration file.
      chown vco:vco orchestrator-config-export-orchestrator_ip_address-date_hour.zip
    4. Stop the Orchestrator server service and the Control Center service of the built-in vRealize Orchestrator server.
      service vco-server stop && service vco-configurator stop
    5. Import the Orchestrator configuration file to the built-in vRealize Orchestrator server, by running the vro-configure script with the import command.
      ./vro-configure.sh import --skipDatabaseSettings --skipLicense --skipSettings --skipSslCertificate --notForceImportPlugins --notRemoveMissingPlugins --skipTrustStore --path orchestrator-config-export-orchestrator_appliance_ip-date_hour.zip
  4. If the external Orchestrator server from which you want to migrate uses the built-in PostgreSQL database, edit the database configuration files.
    1. In the /storage/db/pgsql/data/postgresql.conf file, uncomment the listen_addresses line.
    2. Set the values of listen_addresses to a wildcard (*).
      listen_addresses ='*'
    3. Append a line to the /storage/db/pgsql/data/pg_hba.conf file.
      host all all vra-va-hostname.domain.name/32 md5	
      Note:

      The pg_hba.conf file requires using a CIDR prefix format instead on an IP address and a subnet mask.

    4. Restart the PostgreSQL server service.
      service postgresql restart
  5. Migrate the database to the internal PostgreSQL database, by running the vro-configure script with the db-migrate command.
    ./vro-configure.sh db-migrate --sourceJdbcUrl JDBC_connection_URL --sourceDbUsername database_user --sourceDbPassword database_user_password
    Note:

    Enclose passwords that contain special characters in single quotation marks.

    The JDBC_connection_URL depends on the type of database that you use.

    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 
  6. If you migrated vRealize Automation instead of upgrading it, delete the trusted Single Sign-On certificates from the database of the embedded Orchestrator instance.
    sudo -u postgres -i -- /opt/vmware/vpostgres/current/bin/psql vcac -c "DELETE FROM vmo_keystore WHERE id='cakeystore-id';"
  7. Revert to the default configuration of the postgresql.conf and the pg_hba.conf file.
    1. Restart the PostgreSQL server service.

Results

You successfully migrated an external vRealize Orchestrator 6.x Virtual Appliance to a vRealize Orchestrator instance embedded in vRealize Automation 7.3.

What to do next

Set up the built-in vRealize Orchestrator server. See Configure the Built-In vRealize Orchestrator Server.