Daniel Bareiro wrote: > I was reading the 'catalog maintenance' chapter in order to understand a > little more on the operation of File Retention and Job Retention. But > something is not to me clear still. Beyond what is due to maintain the > rule File Retention < Job Retention < Volume Retention, from the moment > at which I would be leaving AutoPrune = no, then records in the catalog > database are keeping forever with the con the volume of the database > will grow more and more. > > Why it would be necessary to use 'AutoPrune = no' if I can use bscan to > get back the jobs and file records that were purged from the database? > You are absolutely right. I had been under the impression that that is what you wanted.
BTW, one problem with Autoprune is that after you run bscan, the next time pruning happens, the just-scanned volumes/jobs/files would be recognized as old again, and be pruned right back out of the database. -- Kevin Keane Owner The NetTech Find the Uncommon: Expert Solutions for a Network You Never Have to Think About Office: 866-642-7116 http://www.4nettech.com This e-mail and attachments, if any, may contain confidential and/or proprietary information. Please be advised that the unauthorized use or disclosure of the information is strictly prohibited. The information herein is intended only for use by the intended recipient(s) named above. If you have received this transmission in error, please notify the sender immediately and permanently delete the e-mail and any copies, printouts or attachments thereof. ------------------------------------------------------------------------------ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
