On 9/25/2012 12:39 PM, lst_hoe02 AT kwsoft DOT de wrote:
> Zitat von dweimer <dweimer AT dweimer DOT net>:
>
>> ...
>>
>> Here's where things go a little wrong, I mount my external backup drive
>> to the test server, launch bconsole, and issue the status command for
>> the client, since I restored the state files, I can see the job ID of my
>> last catalog Backup.  Then issue the run command, select restore, enter
>> the job ID when prompted, and select mod, enter the bootstrap file from
>> the catalog backup and start the job.
> Hello
>
> I have myself not fully tested disaster recovery but as far as i know
> you need a valid bootstrap from your catalog (database) backup. With
> this you can first recover the catalog backup (ASCII dump) and then
> use the tools provided for you database to import this dump. After
> that you are up and running to restore from your volumes. If you don't
> have a recent catalog backup you might use "bscan" to create needed
> records by scanning your volumes.

I find it much easier to just manually save a bzip'd copy of the sql 
dump file. A daily admin job copies the sql dump file via NFS to another 
server and is used to restore the database in the even that the server 
running bacula-dir dies. For a true disaster resulting in the loss of 
all servers, I manually backup a copy of the sql dump file that gets 
stored along with the offsite backup media in a bank safe deposit box.


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users