bacula
Version information
This version is compatible with:
- Puppet Enterprise 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
- Puppet >= 4.7.0 < 6.0.0
- FreeBSD, , , windows , ,
Start using this module
Add this module to your Puppetfile:
mod 'puppetfinland-bacula', '4.1.0'
Learn more about managing modules with a PuppetfileDocumentation
Bacula
A puppet module to manage Bacula Directors, Storagedaemons and Filedaemons. Puppet certificates are used for TLS. Optional firewall and monit support is included.
Module usage
The Puppet manifests written for Vagrant show how to use the module:
For those viewing this README through Puppet Forge here is the first one in full:
$email = 'root@localhost'
class { '::monit':
email => $email,
}
class { '::bacula::director':
manage_db => true,
manage_packetfilter => true,
manage_monit => true,
tls_enable => false,
use_puppet_certs => false,
console_host => 'localhost',
pwd_for_console => 'console',
pwd_for_monitor => 'monitor',
sd_host => '127.0.0.1',
sd_password => 'director',
postgresql_auth_line => 'local bacula baculauser password',
bacula_db_password => 'db',
bind_address => '0.0.0.0',
file_retention => '30 days',
job_retention => '90 days',
volume_retention => '180 days',
max_volume_bytes => '100M',
max_volumes => '5',
email => $email,
monitor_email => $email,
}
class { '::bacula::storagedaemon':
manage_packetfilter => true,
manage_monit => true,
director_address_ipv4 => '127.0.0.1',
pwd_for_director => 'director',
pwd_for_monitor => 'monitor',
backup_directory => '/var/backups/bacula',
monitor_email => $email,
filedaemon_addresses_ipv4 => ['192.168.138.0/24'],
}
class { '::bacula::filedaemon':
is_director => true,
status => 'present',
manage_packetfilter => true,
manage_monit => true,
use_puppet_certs => false,
tls_enable => false,
director_address_ipv4 => '192.168.138.200',
pwd_for_director => 'director',
pwd_for_monitor => 'monitor',
backup_files => [ '/tmp/modules' ],
messages => 'AllButInformational',
monitor_email => $email,
}
class { '::bacula::console':
tls_enable => false,
use_puppet_certs => false,
director_hostname => 'bacula.example.org',
director_password => 'console',
}
For further details refer to module entrypoints:
- Class: bacula::director
- Class: bacula::storagedaemon
- Class: bacula::filedaemon
- Class: bacula::console
Windows notes
The ::bacula::filedaemon class supports configuring Bacula Filedaemon on Windows, including poking holes for the Bacula Director into Windows firewall and reusing Puppet's TLS certificates. Monit support is missing.
Use forward slashes in paths you want to backup:
'C:/Program Files/Bacula'
Even though double backslashes seemed to work as well, they made browsing (and hence restoring) the backups using bconsole impossible.
Dependencies
- puppet/windows_firewall (>= 2.0.0)
- puppetfinland/monit (>= 0.5.0)
- puppetfinland/packetfilter (>= 0.5.0)
- puppetfinland/puppetagent (>= 1.1.0)
- puppetfinland/postgresql (>= 0.3.0)
- puppetfinland/os (>= 0.5.5)
- puppetfinland/systemd (>= 0.1.0)
- puppetlabs/stdlib (>= 4.0.0)
Copyright 2018 Samuli Seppänen, 2017 Petri Lammi, 2017 OpenVPN, Inc. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.