"Jo Rhett" <[EMAIL PROTECTED]> kirjoitti viestissä news:[EMAIL PROTECTED] > On Sun, Aug 20, 2006 at 12:09:39PM +0300, Timo Neuvonen wrote: > > AFAIK, enabling this would make it auto-prune record by record, when > > the next job is run and the retention period for a certain record has > > expired. > > > > What I neeed to do, is to prune all the records from the pool only later. > > Reason for this is that the volumes in the pool needs to be recycled as soon > > as 28 days after the last write, but the volume needs to be valid (and must > > not > > be pruned before) up to 60 days from the first write. So the retention > > period will expire significantly earlier than I actually can prune the > > volumes. > > I'm confused by this statement because a Recycled volume has already been > Pruned. The cart is definitely pulling the horse in this case. > That's how I see it: Recycling (~overwriting data) actually happens when Bacula needs a recyclable volume again. Volume must be completely pruned (which sets its status to purged) before it can be recycled. Pruning means deleting "expired" database entries, either by
- auto prune, which (if enabled) happens during the next job after retention time has expired. This means, that database entries older than expiration period are deleted one by one, _not_ all entries for a volume (or pool) at the same time. This works ok, but it's not a solution this time. - or pruning may be done manually (console prune command). Means error-prone manual typing at the proper time, not a permanent solution, although that's how I've configured the system now. - close to the latter one, the manual mentions an admin job that could be used to prune. Anyway, I haven't found any documentation / example about it. But it should allow me to keep all database entries in the catalog until I really need to recycle the volume. So, the problem is, that I should set volume retention period to 28 days since volume may be written to until the January 31st, and may need to be recycled on March 1st. However, using auto-prune this would cause that the first jobs that were run in the beginning of January, would be pruned from the catalog already before the end of the same month, but I need to keep them _all_ until the end of February. That's why I can't use auto prune, but try to set an admin job to do the pruning "with a single shot" instead. Actually, my statement above assumes I've figured correctly what volume retention period means. This would be a solution, if I've had a wrong idea about it... Does it also allow pruning database entries one by one (like file and job retention) or does it maybe wait until the whole volume hadn't been written into for the retention period? The months mentioned above are the worst case; same 2-month cycle would go on all year long. > Assuming I reverse those words it kindof makes sense but I have > experience attempting this, so I'm useless to you. Good luck. > Any experienced help would be appreciated... unless you mean "experience in reversing the words" ;-) ...I just wasn't quite sure which way you meant it... Regards, Timo ------------------------------------------------------------------------- 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
