Hi,
I can think of 2 ways to go with this that might work:
1) Implement an option to the 'run' command to specify the verify job by job
id. Using some scripting magic it should be easy enough to grab the specific
job id you want to verify and trigger a job to perform this verification
whenever you want to.
I believe that this is already implemented via the run command then
using "mod". However, since no one seems to have used setting the JobId, it
has been rather neglected. I'd suggest that you try what exists, and if it
is broken, the best is probably to submit a bug report.
I checked for this capability (and double checked just now) when I setup my
Admin verify trigger jobs.
I dont get an option to specify the job by JobID (eg 'Verify JobID=6192')- only
by selecting a job name from a list.
I even tried to enter the job id at this prompt but was told to enter a number
between 1 and 9.
Not sure that comes under the heading of bug report, unless it's supposed to be
an option and isn't showing up. If that's the case, let me know and I'll file
it. :-D
2) Add the ability to specify a job by offset or scheduled start time. ie
Verify the 2nd last BaculaCatalog job or the BaculaCatalog job that was
scheduled to start on Friday. The offset would enable automatic scheduling
of
jobs, and could be potentially more useful than the specific date. (which
would
still need to be controlled thru scripting)
This is an idea that I think given a bit of careful thought and good
specification could be very useful. This idea would need to be submitted as
a feature request.
Which is exactly why I haven't rushed in a feature request yet.
Once I wrap my head around it and work out how I think it should work I'll post
the request. Currently I'm leaning towards something along the lines of 'Verify
Job Offset = 2' which would verify the 2nd last backup job instead of the last one.
Not sure the name is quite right, because it isn't really clear what it does.
But its a work in progress.
Cheers
