Recovery & Failover: Difference between revisions
From Obsidian Scheduler
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
=Multiple Concurrent Hosts= | =Multiple Concurrent Hosts= | ||
Out-of-the-box, Espresso can be run with as many hosts for which you are licensed. As long as at least one host is running and the jobs are not constrained to specific hosts, any server failures will not prevent jobs from being run on schedule. Any jobs running when a server fails will be recovered as defined in | Out-of-the-box, Espresso can be run with as many hosts for which you are licensed. As long as at least one host is running and the jobs are not constrained to specific hosts, any server failures will not prevent jobs from being run on schedule. Any jobs running when a server fails will be recovered as defined in Instance Outage Recovery. | ||
=Instance Outage Recovery= | =Instance Outage Recovery= | ||
Revision as of 17:59, 21 February 2011
Espresso ensures continuity in the execution of your scheduled jobs by providing a variety of built-in recovery mechanisms.
- Multiple concurrent hosts support
- Instance outage recovery
- Configurable recovery options by job
- Resubmission of abnormally terminating jobs
Multiple Concurrent Hosts
Out-of-the-box, Espresso can be run with as many hosts for which you are licensed. As long as at least one host is running and the jobs are not constrained to specific hosts, any server failures will not prevent jobs from being run on schedule. Any jobs running when a server fails will be recovered as defined in Instance Outage Recovery.
