On 12/3/2010 8:20 AM, Jon Schewe wrote:
> On 12/02/2010 06:37 PM, Phil Stracchino wrote:
>> On 12/02/10 19:22, Dan Langille wrote:
>>
>>> 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?
>>>
>> I seem to recall this has been reported previously, yes.
>>
>>
> That's correct. I've run into this and my solution has been to have each
> job to be copied to explicitly queue the copy job for it by selecting
> the last ID with the same job name. This ensures that you don't end up
> with 2 copy jobs for the same original job.

That is the problem I'm encountering now.  There are two incremental 
jobs to be copied, both of the same name.  They'll never both get copied 
over....

-- 
Dan Langille - http://langille.org/

------------------------------------------------------------------------------
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users