Disaster Recovery Preparation

• Ensure that you always have a valid bootstrap file for your backup and your Catalog backup and that it is saved to an alternate machine. This will permit you to easily do a full restore of your system.

• Ensure that your Catalog is saved everyday. You can also add Bacula configuration files to the BackupCatalog default FileSet.

• If possible copy your Catalog nightly to an alternate machine. If you have a valid bootstrap file, this is not necessary, but can be very useful if you do not want to reload everything.

• Make a copy of your Bacula .conf files, particularly your bacula-dir.conf, and your bacula-sd.conf files, because if your server goes down, these files will be needed to get it back up and running, and they can be difficult to rebuild from memory. Using a source version control system such as git or svn with a remote repository on your configuration and scripts directories can help you to track configuration changes and do remote backup after each modifications.

• Perform tests using the Rescue USB or CDROM before you are forced to use it in an emergency situation.

• Ensure that you have captured the disk partitioning layout on all servers to be protected. The Bacula Systems USB key for Linux and for Windows automates this process.

See also

Go to:

• Storage Considerations

• Mirroring Data between Data Centers

• Disaster Recovery Plan

• Standard Recovery Solution

Go back to the Disaster Recovery chapter.

Go back to the main Bacula Infrastructure Recovery page.