>>>>> On Thu, 14 Apr 2005 17:01:24 -0700, Karl Cunningham <[EMAIL PROTECTED]> >>>>> said:
Karl> The other day our incremental backup of about 20 machines (concurrent Karl> backups) took about 2 hours to complete where it usually takes about 20 Karl> minutes. That day the file retention periods for a past full backup Karl> expired and the incremental backups triggered automatic pruning. I suspect Karl> the autopruning of finished jobs slowed down the database operations for Karl> other jobs still running so the whole thing took a LOT longer than usual. Karl> It would be more convenient if the autopruning could instead be done from a Karl> cron job at times when no backups are scheduled to run. Karl> I set AutoPrune = no for the pools in question but couldn't figure out a Karl> script to initiate pruning of retention-expired file records. Does anyone Karl> know of a way to do this? The prune command should do it (with appropriate args). __Martin ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
