Kern Sibbald said: > On Thursday 23 February 2006 11:21, Ralf Gross wrote: >> Volume Use Duration >> [...] >> The use duration is checked and the Used status is set only at the end >> of >> a job that writes to the particular volume, which means that even though >> the use duration may have expired, the catalog entry will not be updated >> until the next job that uses this volume is run. >> >> If I understand this right, I should never see the 'Used' state set by >> 'Volume Use Duration' in the volume list, because it will only be >> updated >> by the next job that uses that tape. Does that make sense at all? > > Yea, it really should say "attempts" to use that volume.
Ok, but why did bacula mark the volume the week before as used, although no job attempted to use it (see below). I see nothing related in the log file, the last entry before the volume was marked as 'Used' was the auto prune job the day before. >> 13-Feb 17:17 bacula-dir: Begin pruning Jobs. >> 13-Feb 17:17 bacula-dir: No Jobs found to prune. >> 13-Feb 17:17 bacula-dir: Begin pruning Files. >> 13-Feb 17:17 bacula-dir: No Files found to prune. >> 13-Feb 17:17 bacula-dir: End auto prune. >> 14-Feb 08:42 bacula-dir: Max configured use duration exceeded. Marking >> Volume "Bang3-2006-02-08" as Used. I still think I'm missing something... Ralf ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
