Bacula-users

Re: [Bacula-users] How to prevent to schedule a job if the same job is still running

2009-10-05 03:51:22
Subject: Re: [Bacula-users] How to prevent to schedule a job if the same job is still running
From: Silver Salonen <silver AT ultrasoft DOT ee>
To: bacula-users AT lists.sourceforge DOT net
Date: Mon, 5 Oct 2009 10:48:42 +0300
I now discovered a downside of this: cancelled duplicate jobs cause the level 
to be ran again if "Rerun Failed Levels = yes". And we're back where we 
started. Frustrating, hysterically funny, depressing.

Does it seem like a bug to anyone?

I guess I'll have to keep using my check-job.sh script.

-- 
Silver

On Tuesday 15 September 2009 13:57:07 Silver Salonen wrote:
> Actually, you can do it - "Allow Higher Duplicates" really means ANY
>  duplicate job, not only a higher one. I just tested it and an incremental
>  job is cancelled if either full or incremental instance of the same job is
>  still running.
> 
> So in my case "Allow Higher Duplicates" did the trick :)
> 
> > Hello,
> >
> > This works as reported for me as well, however, what I want to have in
> > the first case is for the originally scheduled job to be canceled, not
> > the duplicate.  The reason being that my incrementals fall into a daily
> > schedule, whereas my fulls are scheduled out-of-band, so I want the
> > incremental to be canceled on the day that a full is scheduled.
> >
> > Given what you all say below, this doesn't seem possible with bacula's
> > Duplicate Job Control.  Correct?
> >
> > thanks!
> > Stephen
> >
> > Silver Salonen wrote:
> > > On Monday 14 September 2009 15:59:24 Bram Vandoren wrote:
> > >> Hi All,
> > >>
> > >> Silver Salonen wrote:
> > >>> Hmm, I guess not then. But it has been reported several times in the
> > >>> list. So, any volunteers? :)
> > >>
> > >> This configuration:
> > >>   Allow Higher Duplicates = no
> > >>   Cancel Queued Duplicates = yes
> > >>
> > >> Seems to work fine in my situation (some more testing is needed). It
> > >> cancels the newly created duplicate job immediately.
> > >>
> > >> This configuration:
> > >>   Allow Higher Duplicates = no
> > >>   Cancel Running Duplicates = yes
> > >> cancels the running job and starts the same one. If you have a job
> > >> that takes more than 24h to complete a runs daily, it will never
> > >> finish.
> > >>
> > >> Hope it helps.
> > >>
> > >> When I find some try I will reopen the bug report.
> > >>
> > >> Cheers,
> > >> Bram.
> > >
> > > I'll try that on my servers with a few hundred jobs and report about it
> > > tomorrow :)
> > >
> > > But as default options are "Cancel Queued Duplicates = yes" and "Cancel
> > > Running Duplicates = no", the only needed option seems to be "Allow
> > > Higher Duplicates = no". I myself had set "Allow Duplicate Jobs = no",
> > > because I thought it includes  "Allow Higher Duplicates = no" too.
> > > Whether the one option helps or not, I'll tell tomorrow.

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

<Prev in Thread] Current Thread [Next in Thread>
  • Re: [Bacula-users] How to prevent to schedule a job if the same job is still running, Silver Salonen <=