Hi,

we have to do a few backups over a slow and lossy line which makes those
backups pretty unpredictable. In our case, a job duration of more than
24 hours is possible and if the link goes down for some reason a
successful job can even take days to complete (Reschedule On Error).

This scenario is not perfect, but it works and we have at least some
backups of the mentioned clients. Our scheduler however doesn't play
along and reschedules these jobs every day, which means that the queue
gets longer and longer after every `long' job.

I thought `Maximum Concurrent Jobs' is what I want, but unfortunately
(for me), MCJ=1 just prevents bacula from running two jobs with the same
name at the same time, it doesn't prevent it from queueing the job.

Is there something I missed?


Thanks,

Petar

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users