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 origi
Author: Phil Stracchino <alaric AT metrocast DOT net>
Date: Thu, 02 Dec 2010 19:37:27 -0500
I seem to recall this has been reported previously, yes. -- Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355 alaric AT caerllewys DOT net alaric AT metrocast DOT net phil AT co.ordinate DO
My solution: create a new schedule, and hope that none of the jobs overlap. :) -- Dan Langille - http://langille.org/ -- Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into
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 yo
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 hap
How are the two jobs different then? Don't you have one for each host? Here's an example from my config. The start-job script just starts the specified job using bconsole. Job { Name = "ottertail" Cl
They were run at different times, same host each time. There are different jobs for each host. I've thought of doing that, but the ideal solution is: * run all jobs * copy to tape, a slower process,