Page History

...

• Configuration Data
  • This includes installation options and configuration items that which are updated after installation, for example certificates and settings for HTTPS connections.
• Inventory Data
  • JS7 - Inventory of workflows, jobs and related objects managed with JOC Cockpit.
• Transaction Data
  • JOC Cockpit
    • JS7 - History of past order and task executions, of deployments and order submissions.
    • JS7 - Daily Plan for future order starts.
  • Controller and Agent
    • JS7 - Order State Transitions that which are persisted persistent to allow restart capabilities.
• Log Data
  • Log files are created and updated continuously and are mainly used for problem analysis. As past log files are not used at run-time many users consider them not be an immediate target of backups. 

...

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

...

• The database backup tool is required to create consistent backups , in situations such as concurrent transactions - for example, in the event of concurrent transactions if new items are being added to the JS7 History while a backup is being 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 shut down the JOC Cockpit to take and make a backup by exporting the JS7 database.

...

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

...

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

...

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

• Backing There is little point in backing up transaction data is pointless as it can change every millisecond.
• Restoring from a backup that is, for example, 30 minutes old is of no use as in between times jobs will have been executed and orders will have proceeded. This will result in severe data loss and an inconsistent journal.

...

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

...

• The JS7 - Controller Cluster guarantees redundancy and consistency of transaction data which is synchronized between Active and Standby Controller instances on different machines.
• If the Active Controller instance's journal is lost, for example due to disk failure, then the Standby Controller instance will pick up operation 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.

...

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

...

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

...

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

• Backing There is little point in backing up transaction data is pointless as it can change every millisecond.
• Restoring from a backup that is, for example, 30 minutes old is of no use as in between times jobs will have been executed and orders will have proceeded. This will result in severe data loss and an inconsistent journal.

...

• The JS7 - Agent Cluster guarantees redundancy and consistency of transaction data which is synchronized between the Active and Standby Director Agent instances on different machines. If the Active Director Agent's journal is lost, for example due to disk failure, then the Standby Director Agent will pick up operation form from 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 use a journal as they are used for job execution only. Workflows and order state transitions are managed by the Director Agent only.

...

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

...