Introduction
JobScheduler can be operated for high availability. A number of options are available:
Redundancy in a Passive Cluster
- A Primary JobScheduler and Backup JobScheduler are operated in a Passive Cluster
- Should the primary instance fail then the backup instance will take over the load from the primary instance.
- In case of failover all jobs, job chains and orders are processed from the status on that they achieved in the primary instance.
Distributed Processing with an Active Cluster
- An Active Cluster consists of a number of JobScheduler instances on different server nodes.
- Jobs can be executed in any of the connected JobScheduler instances.
- Should a JobScheduler instance fail then the processing is continued by one of the connected JobScheduler instances.
- Actively clustered JobScheduler instances allow hot plug-in, i.e. they can be added to a cluster at any point in time and can be removed accordingly.
Dynamic Agent Assignment in a Master / Agent Cluster
- In a Master / Agent Cluster a number of Agents is operated on different server nodes.
- The cluster can be configured to dynamically select the next available JobScheduler Agent.
- In case of failure of a JobScheduler Agent the Master JobScheduler will switch processing to the remaining Agents.
Resources
Architecture in Detail
Technical Information
How To ... Instructions
Frequently Asked Questions
Examples in detail