Thanks Doug and others. All the information provided has been very helpful.
Regards, SriSamSri Appecherla Mobile# +91 991 610 6008 On Sat, Nov 6, 2010 at 12:43 AM, Mueller, Doug <[email protected]> wrote: > ** > SriSamSri, > > Since it is probably obvious to you that when the system is down, no > escalations fire, I am going to assume > you are asking what is the affect on the overall running of things when the > system comes back up. > > > Escalations on Time > > If the time the escalation should fire occurred while the system was down, > that escalation will not be run on > that time instance. It will next run the next time a time that it is > supposed to run comes up while the > AR System is up. > > In other words, the system doesn't remember that the escalation time has > been skipped over because the > system was down and then run it when it comes up. > > Think of it as a prize drawing where you must be present to win. If you > aren't present, you don't get the prize. > For escalations on time, if the server is not up when time comes, you don't > run. > > > Escalations on interval > > These types of escalations don't run on a fixed time but periodically on an > interval. The interval is a relative > concept from the last time the escalation fired or the last time the server > started or the escalation was > created. We do not remember the time of last firing except in memory so > there is no memory of when last > fired on a server shutdown. > > Any interval missed while the server is down is missed. > > When the server restarts, it acts like any interval escalation has just > finished firing and all intervals are from > that startup time and then follow along for the interval after the previous > firing. > > Note that if you are on an older server (pre 7.0 I think), escalations on > interval fire IMMEDIATELY on > startup and on creation rather than waiting the interval past the > startup/create for first firing. So, you will see > a different behaviour in older servers. This caused a flood of escalations > at startup that was a performance > challenge so we changed the behaviour to waiting for an interval after > startup. > > There is no tie to any interval things were on from a previous run of the > server. So, if for example you had an > interval of 1 hour and the escalation ran at 8:00. Then, the server went > down at 8:57. The server was brought > back up at 8:59. The escalation would next run at 9:59 (actually 1 hour > and 59 minutes past the previous > run). It is 1 hour after the event, the server startup, that it was > intervalling from. We do not record the fact > that the last run was at 8:00. > > > I hope this has been helpful in describing how escalations work after a > restart of the system. > > Doug Mueller > > ------------------------------ > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *SriSamSri Appecherla > *Sent:* Wednesday, November 03, 2010 9:50 AM > > *To:* [email protected] > *Subject:* Reg: Escalations when ARS is down > > ** Hi, > > I have a basic question. What happens to the escalations firing on > Time/Interval when the ARS is down? > > ARS 7.5 > > Regards, > SriSamSri Appecherla > Mobile# +91 991 610 6008 > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
