Forge Home

Modules

Puppet

Resources

PuppetEcosystemPuppet CommunityUpdates

bacula

A bacula module stolen from the Puppet Labs Operations team
Project URLRSS FeedReport issues

38,617 downloads

21,603 latest version

4.6 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 5.8.0 (latest)
  • 5.7.0
  • 5.6.1
  • 5.6.0
  • 5.5.0
  • 5.2.0
  • 4.0.0
  • 3.0.1
  • 3.0.0
  • 2.0.2
  • 1.2.9
  • 1.2.8
  • 1.2.6
  • 1.2.5
  • 1.2.1
  • 1.2.0
  • 1.1.4
  • 1.1.3
  • 1.1.2
  • 1.1.1
released Dec 28th 2020
This version is compatible with:
  • , , , , ,
This module has been deprecated by its author since Nov 4th 2022.

The author has suggested puppet-bacula as its replacement.

Start using this module

Documentation

zleslie/bacula — version 5.8.0 Dec 28th 2020

Bacula

Puppet Forge Build Status

A puppet module for the Bacula backup system.

Supported Platforms

  • OpenBSD
  • FreeBSD
  • Linux (Debian, Ubuntu, RedHat, Centos, Fedora, SLES)

Requirements

This module requires that exported resources have been setup (e.g. with PuppetDB). Including manifests on the Bacula client, assumes that it can export bits of data to the director to end up with fully functional configs. As such, to get the benefits of using this module, you should be using it on at least the director and client, and most likely the storage, though this might be gotten around, if one were so inclined.

Usage

To understand Bacula, the Component Overview in the Bacula documentation is a useful start to begin understanding the moving parts.

A Minimal Setup

What follows here is the bare minimum you would need to get a fully functional Bacula environment with Puppet. This setup assumes that the three components of Bacula (Director, Storage, and Client) all run on three separate nodes. If desired, there is no reason this setup can not be built on a single node, just updating the hostnames used below to all point to the same system.

Defaults

Bacula's functionality depends on connecting several components, together. Due to the number of moving pieces in this module, you will likely want to set some site defaults, and tune more specifically where desired.

As such, it is reasonable to set the following hiera data that will allow many of the classes in this module to use those defaults sanely.

bacula::storage_name: 'mystorage.example.com'
bacula::director_name: 'mydirector.example.com'

When using the default settings from this module, some resources get provisioned. The provisioning of these default resources can be disabled with the following parameter.

bacula::director::manage_defaults: false
Classification

This may be on the same host, or different hosts, but the name you put here should be the fqdn of the target system. The Director will require the classification of bacula::director, and the Storage node will require the classification of bacula::storage. All nodes will require classification of bacula::client.

Prefer hiera data

Users should prefer setting hiera data to set class parameter values where possible. A couple calls in this module rely on hiera data present to avoid scoping issues associated with defined types and default values.

Upgrading from an older version

Users of a previous version of this module should refer to the wiki for upgrading instructions.

Communication Encryption (TLS Setup)

Refer to the TLS Setup page on the wiki for instructions about configuring communication encryption.

Director Setup

The director component handles coordination of backups and databasing of transactions. In its simplest form, the director can be configured with a simple declaration:

class { 'bacula::director': storage => 'mystorage.example.com' }

The storage parameter here defines which storage server should be used for all default jobs. If left empty, it will default to the $::fqdn of the director. This is not a problem for all in one installations, but in scenarios where directors to not have the necessary storage devices attached, default jobs can be pointed elsewhere.

Note that if you expect an SD to be located on the Director, you will also need to include the bacula::storage class as follows.

By default a 'Common' fileset is created.

Storage Setup

The storage component allocates disk storage for pools that can be used for holding backup data.

class { 'bacula::storage': director => 'mydirector.example.com' }

You will also want a storage pool that defines the retention. You can define this in the Director catalog without exporting it, or you can use an exported resource.

  bacula::director::pool { 'Corp':
    volret      => '14 days',
    maxvolbytes => '5g',
    maxvols     => '200',
    label       => 'Corp-',
    storage     => 'mystorage.example.com',
  }

Client Setup

The client component is run on each system that needs something backed up.

class { 'bacula::client': director => 'mydirector.example.com' }

To direct all jobs to a specific pool like the one defined above set the following data.

bacula::client::default_pool: 'Corp'

Data Encryption (PKI Setup)

Refer to the PKI Setup section of the wiki to configure data encryption on clients.

Creating Backup Jobs

In order for clients to be able to define jobs on the director, exported resources are used, thus there was a reliance on PuppetDB availability in the environment. In the client manifest the bacula::job exports a job definition to the director. If you deploy multiple directors that use the same PuppetDB and you don't want each director to collect every job, specify a job_tag to group them.

bacula::job { 'obsidian_logs':
  files => ['/var/log'],
}

This resource will create a new Job entry in /etc/bacula/conf.d/job.conf the next time the director applies it's catalog that will instruct the system to backup the files or directories at the paths specified in the files parameter.

If a group of jobs will contain the same files, a FileSet resource can be used to simplify the bacula::job resource. This can be exported from the node (ensuring the resource title will be unique when realized) or a simple resource specified on the director using the bacula::director::fileset defined type as follows:

bacula::director::fileset { 'Puppet':
  files   => ['/etc/puppet'],
  options => {'compression' => 'LZO' }
}

If you set a job_tag on your bacula::job, make sure to also set the tag of the bacula::director::fileset to the same value.

Available types

bacula::director::fileset

Defines a Bacula FileSet resource. Parameters are:

  • files: string or array of files to backup. Bacula File directive.
  • excludes: string or array of files to exclude from a backup. Defaults to ''. Bacula Exclude directive.
  • options: hash of options. Defaults to {'signature' => 'SHA1', 'compression' => 'GZIP9'}. Bacula Options directive.

bacula::job

Define a Bacula Job resource resource which can create new bacula::director::fileset resources if needed. Parameters are:

  • files: array of files to backup as part of bacula::director::fileset[$name] Defaults to [].
  • excludes: array of files to exclude in bacula::director::fileset[$name] Defaults to [].
  • jobtype: one of Backup (default), Restore, Admin, Verify, Copy or Migrate. Defaults to Backup. Bacula Type directive.
  • fileset: determines whether to use the Common fileset (false), define a new bacula::director::fileset[$name] (true) or use a previously defined bacula::director::fileset resource (any other string value). Defaults to true. Bacula FileSet directive.
  • template: template to use for the fragment. Defaults to bacula/job.conf.erb.
  • pool: name of the bacula::director::pool to use. Defaults to bacula::client::default_pool. Bacula Pool directive.
  • pool_full: name of the pool to be used for 'Full' jobs. Defaults to bacula::client::default_pool_full. Bacula Full Backup Pool directive.
  • pool_inc: name of the pool to be used for 'Incremental' jobs. Defaults to bacula::client::default_pool_inc. Bacula Incremental Backup Pool directive.
  • pool_diff: name of the pool to be used for 'Incremental' jobs. Defaults to bacula::client::default_pool_diff. Bacula Differential Backup Pool directive.
  • jobdef: name of the bacula::jobdef to use. Defaults to Default. Bacula JobDefs directive.
  • level: default job level to run the job as. Bacula Level directive.
  • accurate: whether to enable accurate mode. NB, can be memory intensive on the client. Defaults to 'no'. Bacula 'Accurate' directive.
  • messages: the name of the message resource to use for this job. Defaults to false which disables this directive. Bacula Messages directive. To ensure compatibility with existing installations, the Bacula Messages directive is set to Standard when Jobtype is Restore and the messages parameter is false.
  • restoredir: the prefix for restore jobs. Defaults to /tmp/bacula-restores. Bacula Where directive.
  • sched: the name of the scheduler resource to use for this job. Defaults to false which disables this directive. Bacula Schedule directive.
  • priority: the priority of the job. Defaults to false which disables this directive. Bacula Priority directive.
  • selection_type: determines how a copy/migration job will go about selecting what JobIds to migrate
  • selection_pattern: gives you fine control over exactly what JobIds are selected for a copy/migration job.
  • write_bootstrap: allows you to specify where a bootstrap file should be written after backup.
  • max_full_interval: The time specifies the maximum allowed age of the most recent successful Full backup. Defaults to 0. Bacula Max Full Interval directive

See also bacula::jobdefs.

bacula::jobdefs

Define a Bacula JobDefs resource resource. Parameters are:

  • jobtype: one of Backup, Restore, Admin, Verify, Copy or Migrate. Defaults to Backup. Bacula Type directive.
  • sched: name of the bacula::schedule to use. Defaults to Default. Bacula Schedule directive.
  • messages: which messages resource to deliver to. Defaults to Standard. Bacula Messages directive.
  • priority: priority of the job. Defaults to 10. Bacula Priority directive.
  • pool: name of the bacula::director::pool to use. Defaults to Default. Bacula Pool directive.
  • level: default job level for jobs using this JobDefs. Bacula Level directive.
  • accurate: whether to enable accurate mode. NB, can be memory intensive on the client. Defaults to 'no'. Bacula 'Accurate' directive.
  • reschedule_on_error: Enable rescheduling of failed jobs. Default: false. Bacula Reschedule On Error directive.
  • reschedule_interval: The time between retries for failed jobs. Bacula Reschedule Interval directive.
  • reschedule_times: The number of retries for failed jobs. Bacula Reschedule Times directive.
  • max_full_interval: The time specifies the maximum allowed age of the most recent successful Full backup. Defaults to 0. Bacula Max Full Interval directive

bacula::messages

Define a Bacula Messages resource. Parameters are:

  • mname: name of the Messages resource. Defaults to Standard. Bacula Name directive.
  • daemon: Defaults to dir.
  • director: Bacula Director directive. Note this is not just the name of a director, but director string as found in the documentation for Messages resource under the director option. The message type must be included with the proper formatting.
  • append: Bacula Append directive.
  • Catalog: Bacula Catalog directive.
  • syslog: Bacula Syslog directive.
  • Console: Bacula Console directive.
  • mail: Bacula Mail directive.
  • Operator: Bacula Operator directive.
  • mailcmd: Bacula Mail Command directive.
  • operatorcmd: Bacula Operator Command directive.

bacula::schedule

Define a Bacula Schedule resource. Parameter is:

  • runs: define when a job is run. Bacula Run directive.

bacula::director::pool

Define a Bacula Pool resource. Parameters are:

  • pooltype: Defaults to Backup. Bacula Pool Type directive.
  • recycle Bacula Recycle directive.
  • autoprune: Defaults to Yes. Bacula AutoPrune directive.
  • volret: Bacula Volume Retention directive.
  • maxvols: Bacula Maximum Volumes directive.
  • maxvoljobs: Bacula Maximum Volume Jobs directive.
  • maxvolbytes: Bacula Maximum Volume Bytes directive.
  • purgeaction: Bacula Action On Purge directive. Defaults to Truncate.
  • label: Bacula Label Format directive.
  • voluseduration: Bacula Volume Use Duration directive.
  • storage: name of the Storage resource backing the pool. Defaults to $bacula::storage_name. Bacula Storage directive.
  • next_pool: specifies that data from a Copy or Migrate job should go to the provided pool