Hi,

11.04.2008 11:08, Tilman Schmidt wrote:
> If a job has been waiting for a tape to be mounted for longer than the
> tape's maximum use duration, once the tape is finally mounted it is
> immediately marked as "Used" because of "Max configured use duration
> exceeded." which is surprising because it hasn't actually been in use
> at all. Apparently Bacula counts the volume's "use duration" from the
> start of the job even if the volume hasn't been present during all that
> time. I do not think that is sensible.

Difficult scenario... the behavior you observe is correct from Baculas 
point of view: Once the tape is reserved it counts as 'in use'. It 
might be sensible to not count times when the tape is not actually 
available, but I suspect that the in use timestamp needs to be set at 
the moment a tape is reserved. I don't know...

Probably it would be good if you created a sample with shor times 
where you can show what's happening and report that along with a bug 
report.

Arno

-- 
Arno Lehmann
IT-Service Lehmann
www.its-lehmann.de

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users