Upgrading Orchestrator from 4.1.x to 4.1.x+

Upgrade any Orchestrator 4.1.x instance to a newer 4.1.x+ release.

You can upgrade directly from any 4.1.x release to any 4.1.x+ release without installing intermediate versions. Each release includes all fixes and enhancements from prior versions.

Important: Before upgrading, ensure that all work orders have completed and none are still running. The upgrade process requires approximately 2–3 minutes of downtime.
Attention: If you are upgrading from Orchestrator 4.1.0 to 4.1.1 and were using an external database host (not the default 127.0.0.1), do the following:
  • Back up the /opt/aspera/orchestrator/config/database.yml file before installing the Orchestrator 4.1.1 RPM.
  • Restore the database.yml file before running the orchestrator upgrade command.
  1. Back up the following directories:
    • /opt/aspera/var
    • /opt/aspera/orchestrator
  2. Back up the database: 
    mysqldump -h <DB HOST> -u <DB USER> -p orchestrator > /tmp/orchestrator_db_backup_<timestamp>.sql
  3. Download the appropriate .rpm package and install it (replace the file name with the one you downloaded): 
    rpm -Uvh ibm-aspera-orchestrator-4.1.x.y.x-build-id.x86_64.rpm
  4. Run the Orchestrator upgrade: 
    orchestrator upgrade

    When prompted, type continue to confirm. Orchestrator upgrades to the version installed in the previous step.

    Important: For HA deployments, upgrade each node individually by following all steps in this procedure.