An interesting situation arose today. I had the Copy Job and the original Job with running on the same schedule but different priorities. My goal: copy the original jobs to tape right after the original jobs run.
However, with duplicate job control: Allow Higher Duplicates = no Allow Duplicate Jobs = no Cancel Queued Duplicates = yes I saw this happen: 02-Dec 20:00 bacula-dir JobId 40501: No JobIds found to copy. The above message would appear in bconsole before job 40500 started. My conclusion: the check for jobs to copy is done when the job is queued, not when the job is started. Anyone concur? -- Dan Langille - http://langille.org/ ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users