>>>>> On Fri, 7 Aug 2009 07:55:08 -0700, Jeremy Koppel said: > > I ended up running dbcheck 3 more times. The first time got another > 10,000,000, the second another 8,000,000+, and the 3rd was trivial. Running > it a fourth time came up all 0s. Running another full vacuum got the DB > size down to 597MB, which sounds right.
Nice space saving! In theory Bacula will remove stale file records, but there was a bug in some version that could leave them. > So, there has been a job in the crontab that runs the standard vacuumdb (not > full), but, it does this while Bacula is running. For the past few days, > while running the full vacuum, I shut it off as a precaution. Perhaps I > should modify the script to shut down Bacula during the standard vacuum? Is > this needed? It is probably better to avoid vacuuming while Bacula is updating the database, but there is no need to shut it down. You could run the vacuum from a Bacula admin job rather than cron if you want to control it better. I run it after the backups, so pruning has had a chance to remove records. __Martin ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
