Michael Galloway wrote:
> ok, my bacula db (postgres) is corrupt due to a disk problem on the raid 
> array it resides on.
> i have a complete database dump (from pg_dumpall) from last wednesday that i 
> plan to drop back
> to. my backup environment is bacula 2.2.x and postgres 8.2.5. my plan is to 
> install current 
> bacula 2.4.3 and postgres 8.3.2, initialize the db, make bacula tables for 
> 2.4.3 and then import
> the postgres dump from last wednesday. i realize that the file counts on the 
> tapes will be incorrect,
> and i will have to update the volume info, file count, etc. 
> 
> is this a reasonable course of action or am i asking for trouble?
> 
> -- michael
> 

Perharps you have a catalog_backup job which is more recent ?
It's quite normal for bacula administrator to have one running each day after 
all other backup.
If yes you can restore this dump ( /var/lib/bacula/bacula.sql if normal ) then 
inject it to the db.
And just add bscan to the volumes impacted from that date .

-- 

     Bruno Friedmann


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users