Jeffrey L. Taylor wrote: Hi Jeffrey,
> Quoting Ralf Folkerts <[EMAIL PROTECTED]>: > [snip] >> However, the Volumes themself are never being removed from the Filesystem >> with this config. AutoPrune nicely removes the Jobs and Volumes from the >> Database but not the Volume-File itself. >> > > This is how Bacula works, it will never delete a Volume. Remember > it's primarily about backup to tape. You don't delete tapes. You > overwrite them. Somewhere on the list on in the documentation Kern > says that Bacula will never delete volumes. If you want them deleted > automatically, run it as a cron job. Below is > a starting point. > > (cd /path/to/bacula/volumes; find . -mtime +31 | xargs rm) > > This will remove ALL files that were modified more than 31 days ago > (actually 31 * 24 hours). Further refinement is possible and probably > desired. ah, thanks for making this clear! I must admit I didn't find the note re. Bacula will never delete Volumes... Well, I think I write a Script to check for the existence of a Volume in the Database and remove it, when it's not being referenced; that'll also make changes to the Duration more error-prone :-) Btw: Taken the Tape-analogy: As I could relabel a Tape that's being reused: Is there a way to relabel a Disk-Volume, too? That could save me from writing the Shellscript ;-) Thanks again! Cheers, _ralf_ ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
