Fault Tolerant Automation
On Premise and in the Cloud
When designing a software system, most of the work focuses on the functional areas of the product like the user interface, system storage, and processes running in the background. The possibility of long-term downtime—due to hardware, operating system, or software failure—often gets neglected.
IT management has been aware of unplanned downtime for many years. Billions of dollars are lost each year because of it.
Fault tolerance is a key way to prevent such downtime. The concept is a design and implementation approach that ensures a software system stays available to its users even when there are hardware or software problems.
HIGH AVAILABILITY VS. FAULT TOLERANCE
Both high availability and fault tolerance are designed to keep your systems up and running—but there is one major difference. High availability environments are prone to minimal service interruptions while fault tolerant environments have no interruptions to service.
- High Availability: critical IT systems and infrastructure that are accessible virtually all the time—99.999 percent available—designed to minimize the risks of downtime.
- Fault Tolerance: hardware specially designed to detect faults and immediately transfer service to a redundant hardware component.
THE JAMS APPROACH TO FAULT TOLERANCE
JAMS provides completely transparent failover support, allowing one or more JAMS Schedulers to failover automatically to standby systems so that jobs and processes are executed on or near schedule in the event of a failure of the primary JAMS Scheduler(s).
When a JAMS Primary Scheduler fails or is unresponsive, one of the JAMS Failover Schedulers will go active and assume all of the management of activities that the JAMS Primary Scheduler had. The JAMS Failover Scheduler will then connect to all JAMS Agents to ensure all processing continues to run. Once the JAMS Primary Scheduler comes back online, it can be set to regain control of the schedule as the JAMS Failover Scheduler reverts to sleep mode.
In a cluster aware job scheduling architecture, JAMS uses an active-passive scheme where the primary JAMS Scheduler is in an active setting, managing and dispatching processes across your organization’s infrastructure. The passive JAMS Scheduler resides on another machine in the cluster, monitoring the primary JAMS Scheduler to ensure that everything is running according to plan.
Leverage JAMS on AWS to create a fault-tolerant, secure cloud automation environment.