[prev in list] [next in list] [prev in thread] [next in thread]
List: bacula-users
Subject: Re: [Bacula-users] Wrong pool for rescheduled job after error
From: Michael Scherer <michi () buks-island ! org>
Date: 2008-03-31 13:10:30
Message-ID: 47F0E2C6.5020505 () buks-island ! org
[Download RAW message or body]
Hi Bruno.
Maybe you want to read mails more closely ...
I didn't issue any run command. The job reported an error and rescheduled
itself correctly for the configured time.
Thats why it said:
>> 31-Mar 13:39 GiS-dir JobId 15499: Rescheduled Job
>> software_fserv1.2008-03-29_09.00.20 at 31-Mar-2008 13:39 to re-run in 3600
>> seconds (31-Mar-2008 14:39).
Maybe you want to check the docs for:
# Error Handling
Reschedule On Error = yes
Reschedule Interval = 1 hours
Reschedule Times = 2
So no, that doesn't explain why the "wrong" pool is used. Except for the fact
that in my JobDefs there's "Pool = Daily" though the aborted job didn't use
that pool.
Cheers,
Michael
Am 31.03.2008 15:00 Bruno Friedmann schrieb:
> Michael Scherer wrote:
> > Hi (again).
> >
> > A few hours ago some backup-job was rescheduled due to an error.
> >
> > [...]
> > Job: software_fserv1.2008-03-29_09.00.20
> > Client: "bck01" 2.2.8 (26Jan08) x86_64-suse-linux-gnu,suse,10.0
> > FileSet: "software_fserv1" 2005-12-19 10:59:55
> > Pool: "Weekend" (From Run pool override)
> > Storage: "LTO" (From Job resource)
> >
> > Termination: *** Backup Error ***
> >
> > 31-Mar 13:39 GiS-dir JobId 15499: Rescheduled Job
> > software_fserv1.2008-03-29_09.00.20 at 31-Mar-2008 13:39 to re-run in 3600
> > seconds (31-Mar-2008 14:39).
> > [...]
> >
> > This job just started with the following settings:
> > [...]
> > Job: software_fserv1.2008-03-31_13.39.37
> > Backup Level: Full
> > Client: "bck01" 2.2.8 (26Jan08) x86_64-suse-linux-gnu,suse,10.0
> > FileSet: "software_fserv1" 2005-12-19 10:59:55
> > Pool: "Daily" (From Job resource)
> > [...]
> >
> >
> > This job never runs with the Daily pool.
> > Seems to be a bug?
> >
> > Cheers,
> > Michael
> >
> >
>
> Hi Michael
>
> When you issue the run command, did you notice that you can ( or have to ) change \
> every thing in job definition. By default it run with the content of the job's \
> definition. Not with what you define in schedule.
> As it is explain in documentation, and this is a "I'm not completely familiar with \
> the power of bacula mistake". ;-)
>
> Hope this explain a bit the why ...
>
--
Every time you install Ubuntu God kills a penguin ...
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic