[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bacula-devel] Regression 'make setup' broken in svn?


Hello,

In the future, it would be helpful if you would at a minimum change the title.  
I get a huge number of emails every day, so periodically go through my box 
and classify subjects that have been resolved, and if you don't change the 
subject, you risk to have your email classified and thus not properly dealt 
with.

Best regards,

Kern

PS: I will look at moving the code that generates the bsr file from the 
pre-run to the run section.

On Thursday 09 October 2008 19:09:17 Graham Keeling wrote:
> On Wed, Oct 08, 2008 at 03:39:43PM +0100, Graham Keeling wrote:
> > On Wed, Oct 08, 2008 at 03:27:57PM +0200, Kern Sibbald wrote:
> > > The code I used didn't properly sort the JobIds because it was not
> > > needed by the subroutine in the previous code  -- my mistake.  So, it
> > > *should* now be fixed in the latest SVN.
> >
> > Looks OK in the regress test. I'll now continue with my more complicated
> > setup.
>
> Hello,
>
> I tried running a VirtualFull using schedules. My schedules look like this:
>
> Schedule {
>   Name = "tserv"
>   Run = Level=Incremental mon at 15:00
>   Run = Level=Incremental tue at 15:00
>   Run = Level=Incremental wed at 15:00
>   Run = Level=Incremental thu at 15:00
>   Run = Level=Incremental fri at 15:00
>   Run = Level=Incremental sat at 15:00
>   Run = Level=Incremental sun at 15:00
> }
>
> Schedule {
>   Name = "Consolidate:tserv"
>   Run = Level=VirtualFull mon at 15:00
> }
>
> The Job that runs the "tserv" schedule has "Priority" set to 10.
> The Job that runs the Consolidate schedule has Priority set to 20.
> Both Jobs have 'Maximum Concurrent Jobs = 1'.
>
> So, there is an Incremental every day, and on Monday, there is also a
> VirtualFull scheduled at the some time as Monday's Incremental, but with a
> lower schedule in order to make it run after the Incremental.
>
> What happens is that both the Incremental and VirtualFull jobs go
> into the 'Running Jobs' state one after the other, very quickly.
>
> The Incremental one starts actually running, backing things up.
> The VirtualFull one creates its bootstrap file thing, and then hangs around
> waiting for the Incremental to finish:
>
> Running Jobs:
> Console connected at 13-Oct-08 14:58
>  JobId Level   Name                       Status
> ======================================================================
>      4 Increme  tserv.2008-10-13_15.00.03 is running
>      5 Virtual  Consolidate:tserv.2008-10-13_15.00.04 is waiting execution
> ====
>
> ...(a few seconds later, to show that I got the Priorities right)...
>
> Running Jobs:
> Console connected at 13-Oct-08 14:58
>  JobId Level   Name                       Status
> ======================================================================
>      5 Virtual  Consolidate:tserv.2008-10-13_15.00.04 is waiting for higher
> priority jobs to finish ====
>
> Then, when the VirtualFull runs, it already has its bootstrap file, created
> before the most recent Incremental ran, and uses that. It then gets its
> StartTime set to the backup from before the most most recent Incremental.
> The following table demonstrates this...
>
> +---+-------------------+---------------------+------+-------+
>
> | J | Name              | StartTime           | Type | Level |
>
> +---+-------------------+---------------------+------+-------+
>
> | 1 | tserv             | 2008-10-11 15:00:00 | B    | F     |
> | 2 | tserv             | 2008-10-12 15:00:00 | B    | I     |
> | 4 | Consolidate:tserv | 2008-10-12 15:00:00 | B    | F     |
> | 3 | tserv             | 2008-10-13 15:00:00 | B    | I     |
>
> +---+-------------------+---------------------+------+-------+
>
> ...and the following table demonstrates how I would expect it to look:
>
> +---+-------------------+---------------------+------+-------+
>
> | J | Name              | StartTime           | Type | Level |
>
> +---+-------------------+---------------------+------+-------+
>
> | 1 | tserv             | 2008-10-11 15:00:00 | B    | F     |
> | 2 | tserv             | 2008-10-12 15:00:00 | B    | I     |
> | 3 | tserv             | 2008-10-13 15:00:00 | B    | I     |
> | 4 | Consolidate:tserv | 2008-10-13 15:00:00 | B    | F     |
>
> +---+-------------------+---------------------+------+-------+
>
> I think that this is happening because the VirtualFull job generates its
> bootstrap file at the wrong time - it should probably do it when it is its
> turn to actually do some proper work, rather than when it gets moved into
> the 'Running' queue.
>
> You might suggest that I schedule the VirtualFull to be later than the
> Incremental, but that isn't helpful as I have no idea when the Incremental
> might finish. I want the VirtualFull to run after the Incremental has
> completed - or even that the VirtualFull performs some kind of Incremental
> backup as well as cleverly bringing together previous backups (though this
> last idea sounds like wishful thinking ;) ).
>
> Perhaps there is another mechanism to kick off a job after an Incremental
> finishes that I am unaware of? That would be a way around it for me.
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge Build the coolest Linux based applications with Moblin SDK & win
> great prizes Grand prize is a trip for two to an Open Source event anywhere
> in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Bacula-devel mailing list
> Bacula-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/bacula-devel



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-devel mailing list
Bacula-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/bacula-devel


This mailing list archive is a service of Copilotco.