Hi,
bacula 2.0.3, debian etch, psql 8.1
My diff pool has a voluseduration of 4 days (96h). I just got a mail
from bacula that tape 06D124L3 was marked as used, because the
voluseduration exceeded. Thats fine, but the tape was last used on
2007-06-24. I think the tape should have been marked as used 4 days
after that. I run an admin job each day on 18:05 which issues a
'status dir'. I know that the algorithms bacula uses for
pruning/recycling/reuse are compicated, but the voluseduration is a
fix time span.
04-Jul 18:05 VU0EM005: Max configured use duration exceeded. Marking
Volume "06D124L3" as Used.
This is the 'llist pool' output from 04-Jul-2007 12:46:06. The tape
was still marked as Append, although the last write was 10 days ago.
Pool: Differential
mediaid: 5
volumename: 06D124L3
slot: 5
poolid: 5
mediatype: LTO3
firstwritten: 2007-06-24 00:07:06
lastwritten: 2007-06-24 01:10:37
labeldate: 2007-06-24 00:07:06
voljobs: 3
volfiles: 80
volblocks: 1,218,227
volmounts: 4
volbytes: 78,590,324,736
volerrors: 0
volwrites: 1,514,788
volcapacitybytes: 0
volstatus: Append
enabled: 1
recycle: 1
volretention: 2,678,400
voluseduration: 345,600
[...]
Now the status changed to Used.
Is this the normal behavior? Why didn't bacula notice the exceeded
voluseduration after the configured 4 days instead of 10?
Ralf
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
