Backup Policy Configuration

CommunityEnterprise

The following article presents information on configuration of Bacula backup policy.

Assumptions

The following are the assumptions that we have made:

  • You have a basic understanding of Bacula, Volumes, recycling, and backup strategies. Please read the fundamentals chapter to get acquainted with those.

  • The retention period for recovering a file on a daily basis is 30 days. That is for 30 days, you can go back to any prior version of a file on a day by day basis.

  • The retention period for recovering a file on a monthly basis is 60 days.

  • You are doing only disk based backups.

  • You have more than one Storage daemon that has access to large data stores.

  • You have one to two thousand client machines to backup each day.

  • You are using PostgreSQL as your Bacula catalog database. This is highly recommended by Bacula Systems.

  • You are using multiple Pools to separate the Volumes that various clients write to, and to help optimize recycling of old data that is no longer needed. More on Pools below.

Basic Disk Configuration

Getting Bacula to write to disk rather than tape in the simplest case is rather easy. In the Storage daemon’s configuration file, you simply define an Archive Device to be a directory. For example, if you want your disk backups to go into the directory /mnt/bacula/backups, you could use the following:

Device {
    Name = DiskDevice_Dev0
    DriveIndex = 0
    Media Type = DiskStorage-mnt-bacula
    Archive Device = /mnt/bacula/backups
    Random Access = Yes;
    AutomaticMount = yes;
    RemovableMedia = no;
    AlwaysOpen = no;
}

The above disk device should be part of a disk autochanger:

Autochanger {
    Name = DiskAutochanger
    Device = DiskDevice_Dev0
    ChangerCommand = ""
    ChangerDevice = /dev/null
}

Assuming you have the appropriate Storage resource in your Director’s configuration file that references the above Autochanger resource,

Storage {
     Name = DiskAutochanger
     Address = ...
     Password = ...
     Device = DiskAutochanger
     Media Type = DiskStorage-mnt-bacula
 }

Bacula will then write the archive to the file /mnt/bacula/backups/ where is the volume name of a Volume defined in the Pool. For example, if you have labeled a Volume named Vol-0001, Bacula will write to the file /home/bacula/backups/Vol-0001. You should not rename it or it will become unreadable by Bacula. This is because each archive has the filename as part of the internal label, and the internal label must agree with the system filename before Bacula will use it.

Read more:

Go back to: Backup Policy.