Hi Ryan, Ryan Novosielski wrote: > I'm fairly certain that is not actually the case. Run `llist > volume=<volname>`. VolUseDuration should show 16 hours in seconds, > which is 57,600. My guess is you have something else there (probably > 0).
Okay, that was a excellent tip. For some bizarre reason the VolUseDuration values are indeed all messed up. I thought I had done the update volumes from pool command recently, but apparently things are pretty messed up. > Remember that volumes are created with the pool settings at the time > of the volume labeling and not touched afterwards, unless you use the > `update` command to "Update volumes from pool" or to manually change > a volume's settings. Yes, I was aware of this, but I thought the values were ok. Oh well, at least we know what is going wrong now. Thank you very very much! There is still the problem of the database growing at an alarming rate. But perhaps this is linked to the problem of volumes not being purged as they should. I'll set the VolUseDuration for all volumes right and then we'll see how it goes. Kind regards, Costyn. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
