On Monday 19 February 2007 15:06, Frank Altpeter wrote: > On 2/19/07, Bill Moran <[EMAIL PROTECTED]> wrote: > > In response to "Frank Altpeter" <[EMAIL PROTECTED]>: > > > My current bacula system (FreeBSD, bacula-2.0.1, mysql-4.1) has > > > currently some massive performance problems. One of the reasons i > > > think is caused by the massive amount of old and obsolete records. > > > For example, i had a client to backup once, which has dissappeared > > > some time ago. When this machine has been removed, the client has been > > > deleted from the bacula configuration. But this way the database > > > records for these clients remain in the database, thus making the db > > > records more and more unusable. > > > So, i would like to prune such records to reduce unneeded data. > > > > > > Is there any way on archiving this? > > > > dbcheck should clean this stuff up. > > > > > And, for the future, what's the best practice to avoid this? > > > > Purge the volumes prior to removing the clients. > > > > On the flip side, running dbcheck periodically is pretty much a > > requirement for keeping Bacula's database reasonably sized. I have it > > run once a month in read-only mode via cron and email us the results. > > When the extra stuff gets significant, I use it to go in and clean up. > > dbcheck is being run on a weekly basis (every sunday before backup > starts) but didn't catch all the old entries from the database. > I just removed manually old entries from Job and File database > relating to jobs back in 2005 ... about 5 million file entries (from > about 25 currently)... > So, dbcheck doesn't seem to clean up that much :)
That is exactly correct. dbcheck is designed to remove orphaned records. That is records that are not consistant with the state of the database -- i.e. a File record where there is no corresponding Job that contains them or Path or Filename records where there is no File record that points to them (deleted files ...). dbcheck does not do pruning -- that is something that is done within Bacula providing you run jobs. If you have a job that you never run, those job records will never be prunned. As a consequence, if you have old jobs that you never run any more, you must manually prune or delete them. The same goes for client records. If you no longer use a client, you need to manually clean up the database. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
