Configure Bacula for Open Source Backups


Want the latest storage insights?

Download the authoritative guide: Enterprise Data Storage 2018: Optimizing Your Storage Infrastructure

Since we covered installation and a very basic initial run the last time we looked at Bacula, let's look at some of the more specific configuration options and capabilities this time.

We aren't trying to provide a comprehensive collection of all Bacula capabilities, which are incredibly numerous. Instead, we want to give you an overview of how Bacula's basic options and capabilities might be configured.

Device Resources

Device resources specify the details of a storage device that can be used by the Bacula storage daemon. One of the most common storage devices likely to be used are tape autochangers. In Bacula, storage devices are configured in the bacula-sd.conf file as well as in the bacula-dir.conf file. An autochanger configuration in bacula-sd.conf might look similar to the following:

Autochanger {
Name = Autochanger
Device = Exabyte
Changer Device = /dev/sg0
Changer Command = "/etc/bacula/mtx-changer %c %o %S %a %d"

Device {
Name = Exabyte
Media Type = LTO
Archive Device = /dev/nst0
Autochanger = Yes
Hardware End of File = no
Spool Directory = /var/bacula/spool
Random Access = no
AutomaticMount = yes
RemovableMedia = yes
AlwaysOpen = yes
Maximum Spool Size = 300G

Device above refers to the archive device, which in this case, is a tape drive. Autochanger = Yes in the Device section tells Bacula that this device belongs to an automatic tape changer and necessitates the definition of a changer device, which is detailed in the first section. AutomaticMount = yes means that Bacula will automatically access the volume unless the operator explicitly unmounts it in the console. AlwaysOpen = yes tells Bacula to keep the device open unless specifically unmounted, so that the tape drive is always available to Bacula. When using tapes, this should always be set to 'yes' to avoid unnecessary operator intervention.

If you're using a DVD device instead of tapes, the Archive Device above might be specified as /dev/hdc with Random Access set to 'yes'.  If you're archiving to disk, you would put the full absolute path to the disk directory here instead. In that case, Bacula would write to that directory, and would use the Volume name configured in the catalog. Also, the RemovableMedia parameter would be set to 'no'.  The Media Type would be 'File',  the Autochanger parameter would be set to 'no',  and the separate autochanger device configuration would be unnecessary.

In bacula-dir.conf, the device resource must also be defined, and the name must match what is configured in bacula-sd.confabove:

Storage {
Name = Autochanger
Address = stash.crystle.com
SDPort = 9103
Password = "xxxxxxverylongpasswordstringxxxxx"
Device = Autochanger
Autochanger = yes
Media Type = LTO


The parameters Spool Directory, and Maximum Spool Size in bacula-sd.conf are worth noting.  If you're using tapes and running incremental backups, you'll want to use a disk spool. The reason for this is that it takes a long time for data to come in to the file daemon (bacula-fd) during an incremental backup. If this data is written directly to tape, the tape will start and stop often, causing what's called shoe-shining of the tape.  By writing the data to disk first, then to tape, the tape can be kept in continual motion, reducing wear on the tape.   Of course, the larger the spool device, the better. In the above configuration, the Spool Directory is set to /var/bacula/spool (which can be a link to another directory elsewhere on the system), and the Maximum Spool Size is set to 300G.

The reason for setting a Maximum Spool Size is to keep the spooled data from filling up the entire disk. Bacula becomes very unhappy when the spool device becomes full during a backup so you don't want that to happen.  Make it large, but limit it to keep it from filling your disk. Otherwise, Bacula will happily spool data to disk until the entire disk is full, at which point it will become very unhappy.

It's worth remembering that Bacula writes backup information to the catalog AFTER the data is written to tape. So, once the job is done spooling and the backup data is actually written to tape, Bacula will then write the information about that backup to the catalog.  This is to prevent having backup information written to the catalog for backups that haven't actually been written to backup media yet.

Volumes, Pools and Labels

How Bacula deals with Volumes, Pools and Labels can be confusing for first-time users, so here's a synopsis:

In Bacula, a Volume is a single tape or file on which Bacula will write your backup data.  A Pool is a collection of volumes, configured such that Bacula does not have to limit a backup to the length of a single Volume (tape, or disk). Instead of naming Volumes in Bacula, you define Pools, so that Bacula can simply add data to the next appendable Volume in the Pool. Adding Volumes to a Pool is done using the 'label' command from within the Bacula Console (bconsole).  Bacula will not write to a Volume until it has been labeled from within Bacula.  The Volume label, along with other data, such as the first and last write times, and the number of files and bytes written to a Volume, are stored in the Bacula catalog (database). The Bacula catalog also contains information about the Pool as well as the Volumes in a Pool. The Pool resource is defined in the Bacula Director configuration.

A simple example of a Pool setup in bacula-dir.conf is below:

Pool {
Name = full

Pool Type = Backup
Recycle = yes # automatically recycle Volumes
AutoPrune = yes # Prune expired volumes
Volume Retention = 6 months
Accept Any Volume = yes # write on any volume in the pool

Most of the options above are self-explanatory, however, much more information about how to configure Pools in Bacula can be found in Bacula's online documentation

Page 2: Jobs and Restoring Data

Submit a Comment


People are discussing this article with 0 comment(s)