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

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 2^nd, poses the question of how to import existing volume pool data into a new bacula director installation?

Any advice or acedotes from when this has been previously performed would be appreciated.

Thanks,

jonathan

This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind SKOPOS to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.

------------------------------------------------------------------------------
Keep yourself connected to Go Parallel: 
VERIFY Test and improve your parallel project with help from experts 
and peers. http://goparallel.sourceforge.net

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users