>>>>> On Mon, 22 Dec 2008 17:04:41 +0900, Troy Daniels said: > > Hi, > > Bacula: 2.4.2, CentOS 5.2, MySQL 5.0.22 > > I noticed today whilst doing some routing bacula work that the Catalog > had grown large (well large for my site anyways :) ) and the > BaculaCatalog dump file is now over 3.6Gb. > > Out of curiosity I ran the following query from bconsole: > > 10: List total files/bytes by Job > > +------+------------+-------------------+----------------------+ > | Jobs | Files | Bytes | Job | > +------+------------+-------------------+----------------------+ > | 59 | 141 | 206,781,463,656 | BackupCatalog | > | 582 | 1,022,941 | 68,722,412,431 | Verify-BackupCatalog | > | 507 | 8,896,399 | 310,277,718,356 | Verify-fs1 | > | 526 | 9,450,665 | 165,052,894,094 | Verify-intranet1 | > | 182 | 1,773,363 | 0 | Verify-repo | > | 540 | 387,787 | 24,657,181,324 | Verify-warehouse | > | 8 | 89,367 | 4,188,830,613 | backup1 | > | 57 | 381,701 | 473,310,459,000 | backup2 | > | 57 | 1,226,525 | 94,625,363,872 | build | > | 58 | 8,056,738 | 347,350,624,685 | cvs | > | 60 | 11,653,878 | 2,913,691,631,062 | fs1 | > | 57 | 856,393 | 429,717,533,097 | imaprep | > | 56 | 9,444,635 | 956,770,555,284 | intranet1 | > | 57 | 602,916 | 173,175,405,062 | jira | > | 57 | 548,043 | 71,925,053,651 | osmosis5 | > | 57 | 239,485 | 51,417,661,937 | pabxav | > | 57 | 1,876,326 | 104,668,113,092 | repo | > | 4 | 114,665 | 221,538,929,525 | vmserver | > | 57 | 305,702 | 1,215,267,960,551 | warehouse | > +------+------------+-------------------+----------------------+ > > Something that immediately stood out was that even tho there was only > about 2 months worth of backup jobs I had a lot of Verify jobs shown. > > My system is configured to run verify jobs on certain more important > backups as a confirmation process. However it looks like these jobs > aren't getting purged from the catalog like the backups are. > > Checking the jobs list I can see the verify jobs from early 2007 are > still listed in the DB. > > I've poked around with the prune, and even purge (albeit carefully) > commands in an attempt to work out how to clear the verify jobs, but the > best I've found is how to remove file records from individual jobs. > > I even checked dbcheck and whilst it has options to cleanup admin and > restore jobs it has nothing for verify jobs. > > All my retention periods are set on the Client, not the job and a glance > thru the Bacula manual's config chapter showed to indication it was > possible on a per-job basis. > > So what I'd like to know is: > 1) Is there a config option somewhere I can turn on to make Bacula > cleanup the verify jobs automagically?
No. > 2) Should verify jobs be auto-purged without special intervention? > Should I therefore be logging a bug or a feature request for this case? A feature request would be appropriate, because I think there is currently no attempt to delete them. The same applies to other types of job that don't write data to a volume, such as Admin and Restore. > 3) If the answer to the first of the above is No, what's the best way to > manually clean these records out - Is it OK to do a delete from Jobs > where type = 'V' and date < 2 months ago? Yes, it is safe to do that. > With a dbcheck run afterwards > to cleanup the rest of the DB perhaps? There is no other information added to the DB by running a verify job, so that will make no difference. __Martin ------------------------------------------------------------------------------ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
