| Upgrading Orchestrator | |
The topics in this section provide guidance in upgrading Orchestrator to the current release for a single node and an Orchestrator cluster.
The upgrade procedure involves upgrading the .rpm file. The upgrade is done with Orchestrator service interruption on a single node and without interruption in an active/active cluster model.
Note that plugins can be upgraded live without restarting Orchestrator, on a single node or a cluster.
When Orchestrator is stopped and restarted, the previously running workflow instances will 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.