>>>>> On Mon, 15 Feb 2010 07:19:48 -0500, John Drescher said:
> 
> > The catalog backup always contains the whole database, so there should be no
> > need to keep old copies of it.  Therefore, a pool with two volumes that
> > recycle frequently might work best, without using much more disk space.
> >
> 
> There is one reason for this. A few years ago I had my bacula database
> on a machine with a hardware problem. At one point my bacula database
> became corrupt but I did not find out for a week or so since backups
> merrily continued. When I detected the corruption a few weeks have
> passed. So when I went to recover the database I had to keep going
> back till I found a database that was good. The good thing is I
> retained the boot strap files otherwise this would have been very
> difficult. After finding the working database I recovered it on a new
> machine and then used the bacula tools to recover the missing records.
> I did that bu knowing which tapes were used in the period that the
> database had been corrupted.

Yes, that's a good point in general.  With the configuration described in the
example though, all of the volumes are on a single disk, which makes it quite
easy to bscan them to rebuild the catalog.

__Martin

------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users