Re: [Bacula-users] disaster recovery of the actual bacula server

[Jérôme B. <jer...@fr...>]

Le 29/11/2012 17:32, lst...@kw... a écrit :
> Zitat von Jonathan Horne <jh...@sk...>:
>
>> I am getting ready to deploy my first bacula server to our
>> production environment.  I would like to practice 2 scenarios of
>> recovery.  First, I will recover the configuration files and  mysql
>> database (from dump files), and hopefully continue on.  The second,
>> I will recover only the configuration files.  Both scenarios, will
>> tear down the server and rebuild new OS and reattach the LUN where
>> the volume pools are stored.
>>
>> The first seems pretty straight forward, especially is the mysqldump
>> is current after the most recent backups that ran.  The 2nd, poses
>> the question of how to import existing volume pool data into a new
>> bacula director installation?
> You need the "bscan" utility to rebuild the catalog from your backup volumes:
>
> http://www.bacula.org/5.2.x-manuals/en/utility/utility/Volume_Utility_Tools.html#SECTION00270000000000000000
>
> Regards
>
> Andreas

As the Bacula catalog is a mainstream database, you can secure it using 
different ways:
     - replication (on another site would be the best)
     - full backup + binlog backup on another site

With these two strategies, you wil be able to survive anything.

The cost to secure the catalog is so low everyone should do it ;)

HTH.
Jerome Blion.