On Feb 10, 2008 2:38 PM, Mark Maas <[EMAIL PROTECTED]> wrote:
>
> ----- "Drew Bentley" <[EMAIL PROTECTED]> wrote:
> > On 2/10/08, Mark Maas <[EMAIL PROTECTED]> wrote:
> > > I was wondering how I could force cancelling of jobs after "x" hours
> > of
> > > scheduled time if they have not started yet.?
> >
> > Anything is possible. Sounds to me you could just simply write a
> > script that either uses the bconsole commands to query the info and
> > act upon the info returned or found. Or you could write a script that
> > checks and directly accesses the database to find any jobs that are
> > still pending, if it's beyond the time specified, then cancel the
> > job,
> > etc.
> >
> > Be creative. If you're not sure how to script, better start there
> > first though..  ;)
>
>
> Hehe, yeah sure, a bit SQL could do this for me. But I've never really
> liked that way of "solving" things. Such things are better left to the
>  software
>
> Best reason would be that my "solution" may very likely brake with
> the next update of the software.
>
> So I keep trying to solve this within Bacula configs.
>
> If not, yes indeed i'll use the python interfacing I guess.
>
> Thanks,
> Mark
>

Okay then, seems you are looking for this most likely:

Max Run Time = <time>
    The time specifies the maximum allowed time that a job may run,
counted from when the job starts, (not necessarily the same as when
the job was scheduled). This directive is implemented in version 1.33
and later.

Max Wait Time = <time>
    The time specifies the maximum allowed time that a job may block
waiting for a resource (such as waiting for a tape to be mounted, or
waiting for the storage or file daemons to perform their duties),
counted from the when the job starts, (not necessarily the same as
when the job was scheduled). This directive is implemented only in
version 1.33 and later.

But this isn't a guarantee that you jobs will get killed at 8:00 am or
the like since the job could start at different times waiting on the
previous jobs to finish, etc.

But then again, it's backups and how important is your data? I'd
suggest just letting them run til complete. Unless backups impact your
systems when users are using them. And if that's the case, perhaps you
need to re-evaluate your systems as I never have any issues kicking
off a backup while a system is being used.

-Drew

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to