Hello, Firstly I want to thank the developers, contributors and users for helping make bacula a great product! For whatever it's worth it is of great use to us with Mac OS X, NetBSD, Linux and Windows!
Secondly I'd like to ask is it known and acceptable that when a Job is already scheduled and its schedule passes another duplicate job gets scheduled? For example if a Full backup happened on Sunday that filled a tape and you weren't able to replace that tape until, say, Tuesday, the Monday schedule would add another Full backup (as no previous Full existed) requiring another Tape (and thus filling) in a never-ending cycle. To mitigate I usually manually ascertain which 'new' jobs are duplicates of already scheduled jobs and cancel them. THis seems like it should be avoidable. I imagine an option that makes jobs not get scheduled if the same job (job name,schedule,pool,etc.) already exists in the queue (only difference being the scheduled time). THoughts? Thanks! - Jesse ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
