Silver Salonen wrote:
> On Wednesday 25 November 2009 03:22:41 Dan Langille wrote:
>> I'm running Bacula 3.0.3 I have this Job:
>>
>> Job {
>> Name = "nyi maildir"
>> JobDefs = "DefaultJobRemote"
>> Schedule = "Maildir"
>> Client = "nyi-fd"
>> FileSet = "nyi mymaildir"
>> Write Bootstrap = "/home/bacula/working/nyi-fd-maildir.bsr"
>> }
>>
>> JobDefs {
>> Name = "DefaultJobRemote"
>> Type = Backup
>> Level = Incremental
>> Client = polo-fd
>> FileSet = "Full Set"
>> Schedule = "WeeklyCycle"
>> Storage = DLT
>> Messages = Standard
>> Pool = Default
>> Priority = 20
>> Spool Data = Yes
>>
>> Allow Duplicate Jobs = no
>> Cancel Queued Duplicates = yes
>>
>> RunAfterJob = "/home/dan/bin/dlt-stats"
>> }
>>
>> Yet, I see duplicates queued. Yes, the daemons have been restarted
>> since the latest change to bacula-dir.conf.
>>
>> Running Jobs:
>> Console connected at 25-Nov-09 00:23
>> JobId Level Name Status
>> ======================================================================
>> 31130 Full BackupCatalog.2009-11-24_08.15.00_12 is running
>> 31131 Differe nyi_maildir.2009-11-24_12.01.00_19 is waiting execution
>> 31132 Full nyi_maildir_tarball.2009-11-24_12.01.00_20 is waiting
>> execution
>> 31133 Increme nyi_maildir.2009-11-24_16.00.00_22 is waiting execution
>> 31134 Increme nyi_maildir.2009-11-24_20.00.00_23 is waiting execution
>> 31135 Increme nyi_maildir.2009-11-25_00.00.00_24 is waiting execution
>> ====
>>
>>
>> Why are the last three jobs queued up? I would expect at most one.
>
> Hi.
>
> Previously we've discovered that you should use "Allow Higher Duplicates =
> no"
> for that.
>
> See my e-mail "Re: [Bacula-users] How to prevent to schedule a job if the
> same
> job is still running" (sent on 5th of Oct) for my comments on using that.
Thank you. Yes, I think we need to alter that documentation to make
things clear.
After not changing the tape this morning, I now see thigs:
Running Jobs:
Console connected at 29-Nov-09 19:05
JobId Level Name Status
======================================================================
31232 Differe ngaio_basic.2009-11-29_05.55.02_15 is waiting for a
mount request
31233 Differe ngaio_databases.2009-11-29_05.55.02_16 is waiting on
max Storage jobs
31234 Differe ngaio.2009-11-29_05.55.02_17 is waiting on max Storage jobs
31235 Differe nyi.2009-11-29_05.55.02_18 is waiting for higher
priority jobs to finish
31236 Increme nyi_maildir.2009-11-29_08.00.00_33 has been canceled
31237 Differe supernews.2009-11-29_08.15.00_34 is waiting execution
31238 Differe latens_basic.2009-11-29_08.15.00_35 is waiting execution
31239 Differe latens_home.2009-11-29_08.15.00_36 is waiting execution
31240 Full BackupCatalog.2009-11-29_08.15.00_37 is waiting execution
31241 Differe nyi_maildir.2009-11-29_12.01.00_38 is waiting execution
31242 Full nyi_maildir_tarball.2009-11-29_12.01.00_39 is waiting
execution
31243 Increme nyi_maildir.2009-11-29_16.00.00_40 has a fatal error
====
Of interest is the nyi_maildir jobs. I see three. Incremental,
Differential, and Incremental, respectively. Only the second is still
queued to run.
29-Nov 16:00 bacula-dir JobId 31243: Fatal error: JobId 31236 already
running. Duplicate job not allowed.
FYI, these are my directives:
Allow Higher Duplicates = no
Allow Duplicate Jobs = no
Cancel Queued Duplicates = yes
I just mounted the new tape, and we'll see what happens from here.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
