rgh schrieb:

I use the "volume use duration" directive for a similar setup. If you set it to something long enough to complete the backup, but not to much to overlap the next run time, everything should work. Note: the use duration is counted starting when the tape is written, not from job start.

That's what you'd expect, but Bacula's behaviour is actually the
opposite: it counts volume use duration from the start of the job
which will eventually be the first to use it, *not* from when the
tape is actually accessed or even present. Specifically, if a job
starts for example at midnight but has to wait until eight o'clock
in the morning for the operator to insert an appendable tape, the
volume's "first written" attribute (which is the basis for the
"volume use duration" mechanism) is nevertheless set to midnight.
Surprising, but apparently intentional.

HTH
TS

--
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