Upgrading: Overview

The topics in this section provide guidance in upgrading Orchestrator to the current release for a single node and an Orchestrator cluster.

The upgrade is done with Orchestrator service interruption so customers must plan ahead for downtime. This procedure also involves uninstalling the previous installation and installing the new version.Therefore, it is essential that the user create a backup according to the procedure in Upgrading: Requirements in case rollback is needed after upgrading the product.

Aspera supports upgrades from versions 1.9 and higher.
Note: For installed versions prior to 1.9, contact Technical Support and request that they explore upgrade solutions with you.

Note that plugins can be upgraded "live", without restarting Orchestrator.

When Orchestrator is stopped and restarted, the previously running workflow instances pick up at the point where they were left just before they were stopped.

Orchestrator is backward compatible so that the existing workflows can still run with the newer Orchestrator version. If the workflows must be upgraded as well (for example, to take advantage of a new plugin), the upgrade can be done live by manually exporting/importing each workflow.