On Friday 25 November 2005 21:28, Arno Lehmann wrote: > Hello, > > On 25.11.2005 22:00, Phil Stracchino wrote: > > Ross Boylan wrote: > >>Item x: Deletion of Disk-Based Volumes > >>Date: Nov 25, 2005 > >>Original: Ross Boylan <RossBoylan at stanfordalumni dot org> > >>Status: Proposal > >> > >>What: It would be useful to control how long the actual backups > >> were kept for those backups that went to disk-based volumes. A > >> range of options similar to those currently available for > >> retaining catalog information would be useful. An additional > >> option to permit deletion of the actual backup when the record of > >> the associated job and/or files is purged from the catalog would > >> also be useful. However, it should be possible for the actual > >> backups to be retained for more or less time than the associated > >> catalog records. > > > > I suggest this could be accomplished with the addition of a single > > optional Pool directive valid only for disk volumes: > > > > Delete Volume When Pruned = Yes
+1 > I would even suggest that a python event on pruning should be used. > > The python script would need to be called at the SD, obviously, and > it would need knowledge of the file that is purged. > > Arno -- Dominic Marks ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
