pichi wrote:
> Hello to all,
>
> I am new to Bacula and LINUX in general. I have read the documentation and
> most of it makes sense to me. I am trying to roll out a production install
> of Bacula for a small shop (20 machines in all). But I wanted to experiment
> with Bacula before putting it to real work. We are going to backup important
> data and not systems as a whole. So we are not using bacula to do system
> recovery. Our backup strategy is for file recovery only.
>
> I have successfully installed bacula_1.38.11-8 on Debian 4.0 with MYSQL
> 5.0.32. I also was able to get Bacula-Web 1.38.5 working. I am using a SONY
> SDX-500C AIT device as storage. I was able to sucessfully backup and restore
> files over the network, create newjobs, clients, and write bootstraps to
> other machines for recovery purposes. In general I tried to change the
> defualt install as little as possible.
>
> So after building everything up and being satisfied I was able to do the
> basics for several days: backup and restore, I decided to reformat the
> original install. I did a complete install of Derbian and Bacula from
> scratch because I had read as long as I had my .bsr files and the bacula.sql
> file I was OK. The .bsr files are on the rebuilt server and the bacula.sql
> file that was on tape has since been recovered to /tmp/baclula-restores on
> the new rebuild. Also I kept copies of all the original .conf files and
> copied them to the new build.
>
> OK, so now I have I think what I need to get my catalog the way it was
> before no? but this is where I get lost. What do I do once I have recovered
> the bacula.sql file? What do I do with this file? And the client .bsr files?
> How do I use them to rebuild the database? I have gone over the sections
> called Distaster Recovery, Catalog Maintenance, and The Restore Command and
> I am not getting anywhere.
The bacula.sql file is a snapshot of the database that holds the catalog. The
exact set of commands required to import it has to do with the database engine
you're running, and is completely outside of Bacula. For example, with mysql,
you'd launch the mysql shell, create the database, and then run the bacula.sql
script with:
\. bacula.sql
> I am sorry if the answers to all this are in the documentation, but it is
> just not jumping out at me and I think I need help.
>
> I would feel much better doing a dry run of a database/catalog rebuild at
> test time than 6 months from now when my boss is hovering over me asking why
> it is taking so long to rebuild the backup server.
If you're doing this kind of testing, it might also be a good idea to test out
recovering using bscan instead of the bacula.sql catalog snapshot. This will
recreate the catalog data by examining the data in volumes. It's a lot
slower, but can save you if you lose the catalog completely.
--
Frank Sweetser fs at wpi.edu | For every problem, there is a solution that
WPI Senior Network Engineer | is simple, elegant, and wrong. - HL Mencken
GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
