>>>>> On Fri, 30 Dec 2005 16:23:38 +0100 (CET), Gabriele Bulfon <[EMAIL 
>>>>> PROTECTED]> said:

  Gabriele> At last, I think I discovered the basic problem behind the 
Automatic Recycle/Purge/Prune so many people are facing (me included).
  Gabriele> I decided to start from a scratch situation, with the latest 
configuration I came up with, using all the suggestions I received in this list.
  Gabriele> As a first step, I just used bconsole to purge all my 7 weekly 
volumes, assuming that any previous job would have been deleted and removed 
from the database.
  Gabriele> With a lot of surprise, I discovered that some jobs were still in 
the bconsole list. Don't know why.
  Gabriele> So I decided to delete them by hand (delete job).
  Gabriele> Finally I had a scratch situation....I thought...
  Gabriele> But I wanted to be sure.
  Gabriele> So I stopped bacula daemons, ran psql on bacula database (I am 
using Postgres) and issued
  Gabriele> some sql statements to examine the database status:
  Gabriele> - a "select count(*) from job" was never returning....(or probably 
returning  after a long time)
  Gabriele> - a "select count(*) from file" was never returining.....
  Gabriele> (or probably returning  after an even longer time)
  Gabriele> So I supposed that both tables should have been very very large and 
still containing hidden data!
  Gabriele> Now, to get my hands on its data, I used pg_dump to dump all the 
bacula db on a flat file and see its content.
  Gabriele> ......many minutes of dump........300Mb of flat file was 
produced.....
  Gabriele> ...wow.....and there, I found a lot of data inside the job and file 
tables.
  Gabriele> So, I decided to drop the whole bacula db and recreate it.
  Gabriele> After doing this, my latest configuration files work perfectly!
  Gabriele> So, my last suggestion to anyone going crazy with their weekly 
backup, is to start from scratch
  Gabriele> any time you need to change the bacula-dir.conf file, then "add" 
the pre-labaled volumes by hand.
  Gabriele> Bacula won't prune or recycle some of your tapes, because old jobs 
are probably still in the db
  Gabriele> in some hidden status.
  Gabriele> I hope somone can clarify why this situation occurs.

Junk in the File and Path tables is OK, because the entries are never removed
and shouldn't affect recycling.

Junk in the Jobs table is more worrying though.  However, some types of job
(e.g. Admin and Verify) are not directly associated with any media, so they
don't get pruned and shouldn't effect recycling either.

I think the JobMedia table is the one that affects Recycle/Purge/Prune most.

__Martin


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to