...

Introduction

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

...

The JOC Cockpit configuration data are is stored to in files in the JETTY_BASE/resources/joc directory hierarchy, for example:

• joc
  • start.ini (Jetty Servlet Container settings)
  • joc.properties (installer options, see JS7 - JOC Cockpit Configuration Items)
  • log4j2.xml (see JS7 - Log Files and Locations)
  • *.p12 (keystore and truststore files, see JS7 - JOC Cockpit HTTPS Connections)
  • lib
    • *.jar (optional location for JDBC Driver .jar files and the js7-license.jar file, see JS7 - Database).
  • license
    • *.pem, *.crt (license certificate files, see JS7 - How to apply a JS7 License Key)
  • patches
    • *.jar (patched libraries, see JS7 - Patches for JOC Cockpit)

Configuration data are is created during installation and is optionally are modified by users later on. This suggests that repeated backups of configuration data are required only in case of changes is only required after changes have been made by users.

Inventory Data, Transaction Data

All objects managed with the JOC Cockpit are stored in the JS7 - Database.

This includes data that are is managed by the JOC Cockpit GUI:

• Inventory Data
  • JS7 - Inventory of workflows, jobs and related objects to that manage dependencies.
  • JS7 - Settings that determine the working of the JOC Cockpit.
  • JS7 - Controllers and Agents that are managed by the JOC Cockpit.
  • JS7 - Identity Services that are managed by the JOC Cockpit.
  • JS7 - Profiles that hold user preferences.
• Transaction Data
  • JS7 - History of past order and task executions, of deployments and submissions.
  • JS7 - Daily Plan for future order starts.

Users should take make backups of the JS7 database on a regular basis.

• The database backup tool is required to create consistent backups, for example, in case the event of concurrent transactions if new items are added to the JS7 History while a backup is performed.
• The database backup tool should not interfere with JS7 database transactions and should not affect JS7 operations. 
• If no decent backup tool is in place then users can shutdown JOC Cockpit to take a backup by exporting the JS7 database.

...

JOC Cockpit log files are stored in the JETTY_BASE/logs directory.

Except for problem analysis log Log files are not too relevant except for problem analysis, However, compliance reasons can suggest to backup require backups of log files.

Controller

Configuration Data

The Controller's configuration data are is available from files in the JS7_CONTROLLER_DATA/config directory hierarchy, for example:

• config
  • controller.conf (see JS7 - Controller Configuration Items)
  • log4j2.xml (see JS7 - Log Files and Locations)
  • lib
    • *.jar (optional location for the js7-license.jar file, see JS7 - How to apply a JS7 License Key)
  • license
    • *.pem, *.crt (license certificate files, see JS7 - How to apply a JS7 License Key)
  • patches
    • *.jar (patched libraries, see JS7 - Patches for Controller)
  • private
    • private.conf (see JS7 - Controller Configuration Items)
    • *.p12 (keystore and truststore files, see JS7 - Controller HTTPS Connections)

Configuration data are is created during installation and is optionally are modified by users later on. This suggests that repeated backups of configuration data are required only in case of changes is only required after changes have been made by users.

Transaction Data

Transaction data of Controller instances are available from the Controller's JS7_CONTROLLER_DATA/state directory that holds a journal of JS7 - Deployment operations and JS7 - Order State Transitions. This applies to Standalone Controller instances and to Controller Cluster instances.

• It Backing up transaction data is pointless to backup transaction data as they it can change every millisecond.
• Restoring from a backup that is for example 30 minutes back old is of no use as in between times jobs will have been executed and orders will have proceeded which includes . This will result in severe data loss and results in an inconsistent journal.

Standalone Controller

• Use of a cluster file system for the Standalone Controller instance's journal is an option. However, this includes also brings performance penalties and requires user intervention to restart a failed Standalone Controller instance from a clean copy of its journal.
• Should If transaction data of for a Standalone Controller be is lost then this affects will affect the state of orders that are currently running or for which the orders whose execution status has not yet been reported back to JOC Cockpit. When a Standalone Controller is started with a new journal then:
  • JOC Cockpit will automatically re-assign the Controller and related Agents,
  • users have to redeploy any related scheduling objects such as workflows from the JOC Cockpit's inventory,
  • users have to resubmit any orders from the JOC Cockpit's Daily Plan.

...

• The JS7 - Controller Cluster guarantees redundancy and consistency of transaction data that are which is synchronized between Active and Standby Controller instances on different machines.
• Should If the Active Controller instance's journal be is lost, for example due to disk failure, then the Standby Controller instance will pick up operation form from a synchronized copy of the journal. If the failed Controller instance is started later on then it will be assigned the standby role and will synchronize its journal from the Active Controller Instance.

Log Data

Log files of for the Controller (not: of workflows or jobs) are available from available in the Controller's JS7_CONTROLLER_DATA/logs directory.

Except for problem analysis the log Log files are not too relevant except for problem analysis, However, compliance reasons can suggest to backup require backups of log files.

Agent

Configuration Data

The Agent's configuration data are is available from files in the JS7_AGENT_DATA/config directory hierarchy, for example:

• config
  • agent.conf (see JS7 - Agent Configuration Items)
  • log4j2.xml (see JS7 - Log Files and Locations)
  • patches
    • *.jar (patched libraries, see JS7 - Patches for Agent)
  • private
    • private.conf (see JS7 - Agent Configuration Items)
    • *.p12 (keystore and truststore files, see JS7 - Agent HTTPS Connections)

Configuration data are is created during installation and is optionally are modified by users later on. This suggests that repeated backups of configuration data are required only in case of changes is only required after changes have been made by users.

Transaction Data

Transaction data of for Agents are is available from the Agent's JS7_AGENT_DATA/state directory that which holds a journal of JS7 - Deployment operations and JS7 - Order State Transitions.

• It Backing up transaction data is pointless to backup transaction data as they it can change every millisecond.
• Restoring from a backup that is for example 30 minutes back old is of no use as in between times jobs will have been executed and orders will have proceeded which includes . This will result in severe data loss and results in an inconsistent journal.

Standalone Agent

• Use of a cluster file system for the Standalone Agent instance's journal is an option. However, this includes also brings performance penalties and requires user intervention to restart a failed Standalone Agent from a clean copy of its journal.
• Should If transaction data of for a Standalone Agent be is lost then this affects will affect the state of orders currently running orders , until their execution status is 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.

...

• The JS7 - Agent Cluster guarantees redundancy and consistency of transaction data that are which is synchronized between the Active and Standby Director Agent instances on different machines. Should IF the Active Director Agent's journal be is lost, for example due to disk failure, then the Standby Director Agent will pick up operation form a synchronized copy of the journal. If the failed Director Agent instance is started later on then it will be assigned the standby role and will synchronize its journal from the Active Director Agent.
• Subagents do not make use of a journal as they are used for job execution only. Workflows and order state transitions are managed by the Director Agent only.

...

Log files of the Agent (not: of workflows or jobs) are available from the Agent's JS7_AGENT_DATA/logs directory.

Except for problem analysis the log Log files are not too relevant except for problem analysis, However, compliance reasons can suggest to backup require backups of log files.