Forge Home

rsnapshot

Setup rsnapshot

5,831 downloads

139 latest version

3.1 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

  • 4.4.0 (latest)
  • 4.3.1
  • 4.3.0
  • 4.2.0
  • 2.0.0
  • 1.0.1
released Sep 7th 2023
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

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'puppetfinland-rsnapshot', '4.4.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add puppetfinland-rsnapshot
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install puppetfinland-rsnapshot --version 4.4.0

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download

Documentation

puppetfinland/rsnapshot — version 4.4.0 Sep 7th 2023

rsnapshot

A Puppet module for managing rsnapshot.

Module usage

First you need to create a public/private SSH keypair for rsnapshot, for example with 'ssh-keygen'. Then add the private and public key to Hiera. Then you can include the rsnapshot class and give it the parameters you want:

classes:
    - rsnapshot

rsnapshot::private_key_content: 'your-private-key'
rsnapshot::snapshot_root: '/backup/rsnapshot'
rsnapshot::backups:
    - '/etc/': 'backup.domain.com/'
    - '/var/backups/local/': 'backup.domain.com/'
    - 'root@server.domain.com:/etc/': 'server.domain.com/'
rsnapshot::retains:
    - daily: 7
    - weekly: 4
    - monthly: 6
rsnapshot::crons:
    daily:
        minute: 0
        hour: 10
    weekly:
        minute: 0
        hour: 12
        weekday: 3
    monthly:
        minute: 0
        hour: 14
        monthday: 1

Another example from a Puppet profile:

$private_key_content = lookup('profile::rsnapshot::private_key_content', String)
$backups = lookup('profile::rsnapshot::backups')    

class { '::rsnapshot':
    private_key_content => $private_key_content,
    snapshot_root       => '/var/backups/rsnapshot',
    retains             => [  { 'daily'   => 7 }, { 'weekly'  => 4 }, { 'monthly' => 7 }, ],
    crons               => {  'daily'   => { 'minute' => 30, 'hour' => 6, },
                              'weekly'  => { 'minute' => 30, 'hour' => 5, 'weekday'  => 6 },
                              'monthly' => { 'minute' => 30, 'hour' => 4, 'monthday' => 1 }, },
    backups             => $backups, 
}

The "backups" variable in Hiera would be in the same format as above, for example

rsnapshot::backups:
    - '/etc/': 'backup.domain.com/'
    - '/var/backups/local/': 'backup.domain.com/'
    - 'root@server.domain.com:/etc/': 'server.domain.com/'

Note that the titles of the rsnapshot::cron resources need to match those given for retains in the main class - here "daily", "weekly" and "monthly". Also note that the "retain" parameters need to be determined in the correct order, or rsnapshot will start "eating" its own backups; the more frequent backups (e.g. "daily") should be defined earlier than and also run before the less frequent ones (e.g. "monthly). Aping the above configuration is probably the safest bet.

Use the rsnapshot::allow class to allow connections to hosts to be backed up:

classes:
    - rsnapshot::allow

rsnapshot::allow::host: '10.122.49.4'
rsnapshot::allow::key: '<rsnapshot's public key as a string>'

The value of host string is added to SSH authorized_keys from option, so that the given key is only valid if the connection matches the host pattern. For example to allow access from multiple IPv4 addresses:

rsnapshot::allow::host: '10.201.5.8,10.122.49.4'

Finally run "rsnapshot daily" or such manually, and accept the SSH keys as needed. Later this manual procedure should be replaced with exported SSH host keys (sshkey type) that are collected on the rsnapshot host.

Monitoring backups

rsnapshot::marker

This module contains a class rsnapshot::marker that can be used to add "backup marker files". The idea is that cron updates the timestamp of the marker file, by default on a daily basis, and that marker file gets backed up.

Example usage:

include rsnapshot::marker

To customize settings:

class { 'rsnapshot::marker':
  path    => '/etc/.my-marker',
  hour    => 5,
  minute  => 0,
  weekday => '1,3,5',
}

rsnapshot::prometheus_metrics

On the rsnapshot server side the timestamps of the marker files allow gathering metrics about backup age, e.g. with Prometheus Node Exporter's Textfile Collector. If marker files are too old, the most likely cause is that backups are failing and an alert should be sent.

The rsnapshot::prometheus_metrics class provides an easy way to generate Prometheus metrics from rsnapshot backups that have marker files. The class builds on top of the prometheus-rsnapshot-metrics script.

Example usage:

include rsnapshot::prometheus_metrics

To customize settings:

class { 'rsnapshot::prometheus_metrics':
  metrics_file            => '/var/lib/node_exporter/textfile_collector/rsnapshot.prom',
  latest_backup_directory => '/backup/daily.0',
  marker_name             => '.my-marker',
  max_backup_age_days     => 4,
  max_depth               => 3,
  hour                    => 6,
  minute                  => 0,
  weekday                 => '1,3,5',
}

Reference

For more details on module usage refer to these source files: