In response to Eric Bollengier <e...@eb.homelinux.org>: > Le Wednesday 01 July 2009 17:20:22 Bruno Friedmann, vous avez écrit : > > This is just a question if the need exist > > [ Y / N ] > > > > Insert the necessary command to dbcheck to optimize compact tables after a > > full run. > > > > optimize for mysql / vaccum [whatever is not auto] / pack for sqlite. > > > > I've done a dbcheck ( half-year maintenance ) on a customer site yesterday > > and I've made the optimize inside the mysql bacula tables. > > We get half index size and 1/3 data length. > > > > A full restore on big jobs take now <3minutes to build the path opposite to > > the 10 minutes before. > > > > Don't know if this could be a baby-dev job or not ? ( sql writing is ok for > > me, not really c/c++ ) > > Hello Bruno, > > I would say that optimize or vacuum should be run everyday or twice per week. > dbcheck should be used one per month or twice per year and needs bacula to be > stopped... > > So, i prefere having admin or crontab jobs for that.
With PostgreSQL, autovacuum should probably be enabled, which *usually* eliminates the need for manual vacuuming. Of course, every rule has an exception. Running dbcheck is liable to cause HUGE changes to the DB if it hasn't been run in a while, which would justify a VACUUM FULL and REINDEX. Those two commands are not generally used as part of regular maintenance because they tend to be disruptive to performance (since they lock tables). -- Bill Moran Collaborative Fusion Inc. http://people.collaborativefusion.com/~wmoran/ ------------------------------------------------------------------------------ _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
