High Availability Failover

Figure 1: High Availability Failover Outline

The ActiveBatch® High Availability solution, Non-cluster Failover, allows one or more Job Schedulers and Users on different machines to fully fail over, without intervention and with transparency, to standby systems so that jobs and plans are executed and completed on or near schedule in the event of a failure of the primary job scheduler.

The ActiveBatch Job Scheduler currently uses an active-standby scheme similar to Microsofts or Symantec Cluster facility. The primary Job Scheduler is in active mode and dispatching jobs. The other Job Scheduler(s) enter a standby mode monitoring the "heartbeat" for the preferred Job Scheduler.

When an active Job Scheduler fails or is deemed unresponsive, one of the standby Job Schedulers will attempt to go active and take over the job scheduling load.

With the use of Microsoft’s Active Directory and ActiveBatch Enhanced Directory Services the starting or failover of the ActiveBatch Execution Agent on a Windows or Non Windows systems is enhanced. This combined capability allows both Windows and non-Windows systems, in particular, to have access to publishing and high-availability features that would otherwise be only available on the Windows platforms. In addition the ActiveBatch client systems, within that ActiveBatch scheduling environment, will seamlessly failover to the new scheduler and all jobs will continue to be executed.