...

Introduction

Taking a backup includes involves consistently storing the following data in a JS7 environment:

...

Transaction data of Controller instances is available in the Controller's JS7_CONTROLLER_DATA/state directory which holds the journal of JS7 - Deployment of Scheduling Objects operations and JS7 - Order State Transitions. This applies to Standalone Controller instances and to Controller Cluster instances.

...

Transaction data for Agents is available in the Agent's JS7_AGENT_DATA/state directory which holds the journal of JS7 - Deployment of Scheduling Objects operations and JS7 - Order State Transitions.

...

• Use of a cluster file system for the Standalone Agent instance's journal is an option. However, this also brings performance penalties and requires user intervention to restart a failed Standalone Agent from a clean copy of its journal.
• If transaction data for a Standalone Agent is lost then this will affect the state of orders currently running, until their execution status has been reported back to the Controller. When a Standalone Agent is started with a new journal then the Controller will automatically forward workflows and orders to bring the Agent's journal in sync with information from the Controller's journal.
• Do not try to restore a version of the Agent's journal that is not in sync with the Controller. If an older version of an Agent's journal is restored then this will be inconsistent with latest changes to the Controller's journal and will prevent the Agent from being coupled. If you have to restore an Agent, for example after disk failure, then you have to accept that currently running orders are lost and you should start the Agent with a new journal. To this purpose end you can remove the contents of the Agent's state directory.

...