Hello.
I noticed one thing today.. a big full backup was ran on friday, so it wasn't
completed 24 hours later, but when the next job's time arrived, it wasn't run.
I was very surprised, because I expected it to run as it has been the case
without "allow duplicate jobs = no" with Bacula 2.x. When the full job
completed, the scheduled (and not run) one started immediately and was
correctly making an incremental backup.
So it seems that duplicate job control does work, just not the way I expected,
ie. I expected it to being cancelled (I guess I thought it's the "Cancel
Queued Duplicates" directive, but now, I guess not) instead of being hidden
and waiting somewhere back there.
--
Silver
On Friday 24 April 2009 18:33:10 Stephen Thompson wrote:
>
> Hi,
>
> We seem to be having identical problems, duplicate job control does not
> work as advertised (doesn't seem to do anything at all actually) and
> canceling jobs results in termination errors. I haven't figured
> anything out since posting. Please let me know if you figure anything
> out and I'll do likewise.
>
> thanks,
> Stephen
>
>
>
> Silver Salonen wrote:
> > Hello.
> >
> > In Bacula 2.x I used to use my own script that I ran in dir before every
job.
> > The script would query dir whether the job is already ran (the job may be
> > still waiting for smth or running) and if this is the case, the script
would
> > return 1 and cancel the job.
> >
> > I hoped that would be the case with "Allow Duplicate Jobs = no" in 3.0
(I'm
> > using it on FreeBSD), but it seems the directive doesn't change anything,
at
> > least in my case:
> >
> > 1) I ran a job with level=Full and
> > 2) started another instance of the same job with level=Incremental
> > 3) I saw the 2nd job's level upgraded to Full ("No prior or suitable Full
> > backup found in catalog") and then
> > 4) the 2nd job started waiting for the storage (as it uses the same device
as
> > the 1st job, and a device may have only 1 job using it, even if the device
is
> > HDD).
> > 5) After the 1st job completed running, the 2nd started running.
> >
> > This is exactly the same scenario I wrote my "cancelling duplicate jobs
> > script" for. I don't understand what's the point of the new duplicate job
> > control (because I first thought it was to resolve the problem described
> > above). Or doesn't it just work?
> >
> > Anyone having success with it?
------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations
Conference from O'Reilly Media. Velocity features a full day of
expert-led, hands-on workshops and two days of sessions from industry
leaders in dedicated Performance & Operations tracks. Use code vel09scf
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
