Scripsit Adrian Moisey die 20 Oct 2008 14:50:06:
>>>> My way around that is adding the directive:
>>>>
>>>>   RunAfterJob  = "/usr/local/bin/bacula-eject"
>>>>
>>>> to the (last) backup job, where /usr/local/bin/bacula-eject is the
>>>> script:
>>> I would like to do that, but during the week I backup to disk.
>>> Can I get this to run only if there is a tape job that ran?
>> 
>> Sure. Just add the RunAfterJob line to the Job resource of the tape
>> job, but not to the one of the disk job.
> 
> I change between tapes and files on the scheduler, so I only use 1 job 
> per client

Ah, sorry for my clouded crystal ball. :-)
Well, it's difficult to design a solution for you without knowing
more about your configuration, but generally speaking I see two
possible avenues:

a. Add information to the script command line about the job that ran,
   via Bacula's "character substitution" mechanism, which allows the
   script to determine whether the job went to tape or to disk.
   "%l" [job level] or "%n" [volume name] look promising. The pool
   name would be perfect, but the manual doesn't list a substitution
   letter for that.)

b. Check the system date within the script to determine whether it's
   a day on which a tape job is scheduled.

HTH
T.

-- 
Tilman Schmidt
Phoenix Software GmbH
Bonn, Germany

signature.asc
Description: OpenPGP digital signature

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users