Cluster Installation Overview

The Orchestrator platform runs in active/active mode for Apache and Orchestrator services, and in active/passive mode for MySQL.

The Orchestrator cluster can run on-premise or in the cloud.

For Orchestrator on-premise cluster installation, a shared external storage must be set up for the folders and other data sources listed below.

The following folder, which must be shared between the nodes:
```
/opt/aspera/var/run/orchestrator/
```
Important runtime information is stored in this folder. For example, the file trigger history is stored here, and thus each node has the same perspective of already-triggered files. (Alternatively, the history may also be kept in the shared MySQL data. In orchestrator.yml, set the parameter persistence_mode to either drive or db (both options are correct values)).
The following folder, which must also be shared between the nodes because the plugin directories are present in this folder (in the actions subdirectory):
```
/opt/aspera/var/config/orchestrator/
```
Importing a plugin can then be done on only one node.
This folder, which must be shared because the plugins are archived here:
```
/opt/aspera/var/archive/orchestrator/
```
This allows nodes to share the same view of archived plugins.
MySQL data from the following folder:
```
/opt/aspera/common/mysql/data
```
ACM data.

Note: On servers that have other Aspera products installed, do not share the following folder:

/opt/aspera/var/

Instead, share the these folders:

/opt/aspera/var/config/orchestrator
/opt/aspera/var/run/orchestrator
/opt/aspera/var/archive/orchestrator