> My volumes are of type files so using new volumes vs recycling expired > ones just fills up the file system with old data. It makes it hard to > manage and forecast filesystem space needs. > > I have never understood Bacula's desire to override my policy and insist > on preserving data that I already defined as useless.
If one of the issues is getting rid of old data that goes beyond the retention period then one should be able to use the truncate volume on purge directive and then set up a way then to ask Bacula to purge those volumes once they are moved into your recycle pool (via a separate job/script that runs the appropriate bconsole commands). As far as I understand things, Bacula won't do the truncate automatically when it marks the volume as purged and moves it into the recycle pool. Bacula will still use new never before used volumes when it grabs one from the recycle pool (although I suspect if you knew what you were doing you could get around that by updating the proper time stamps/attributes on the media records for the truncated volumes so they would appear as "new") but if the used volumes are truncated then they won't fill up the file system and the backup data should be deleted. hope this helps, --tom ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
