Forge Home


Manage Amanda mysql-zrm with Puppet


10,005 latest version

3.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

  • 0.1.4 (latest)
  • 0.1.3
  • 0.1.2
  • 0.1.1
  • 0.1.0
released Mar 26th 2014

Start using this module

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

Add this module to your Puppetfile:

mod 'abstractit-mysql_zrm', '0.1.4'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add abstractit-mysql_zrm
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install abstractit-mysql_zrm --version 0.1.4

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.



abstractit/mysql_zrm — version 0.1.4 Mar 26th 2014


####Table of Contents

  1. Overview - What is the mysql_zrm module?
  2. Module Description - What does the module do?
  3. How it works - The basics of getting started with mysql_zrm
  4. Usage - How to set it up
  5. Implementation - An under-the-hood peek at what the module is doing
  6. Limitations - OS compatibility, etc.
  7. Development - Guide for contributing to the module
  8. Support - Where to get support


Puppet module for setting up Zamanda MySQL-ZRM to backup databases from a MariaDB, Percona or MySQL server.

Module Description

Manages full and incremental backups of selected databases using MySQL-ZRM. It can use a server <-> client setup or the server can be installed directly onto your database server to do backups there. Backupsets can be setup on any node and get exported to the server of your choosing. At this stage it doesn't manage database users to do the backups due to the variety of ways to implement this. This may be implemented in a future release if I can find good modules for each server type.

How it works

what mysql_zrm affects:

  • configuration files for mysql_zrm
  • cron jobs to do the backups
  • expunging old backups


Setting up mysql_zrm

Automatic Client <-> Server mode.

# override these variables if needed.
`$mysql_zrm::params::db_servers` Array of database servers. (defaults to "db.${::domain}")
`$mysql_zrm::params::backup_server` (defaults to "backup.${::domain}")

Setting these variables will automaticlly include the server or client class.

# include this on your database and backup servers.
include mysql_zrm

Manual Client <-> Server mode

# include this on your database servers.
include mysql_zrm::client

# include this on your backup servers.
include mysql_zrm::server

Exporting backupsets for mysql_zrm servers

These will get exported to the

mysql_zrm::backupset { 'testing':
  databases        => 'test',
  fullhours        => ['0','12'],
  backup_db_user   => 'backup',
  backup_db_pass   => 'PASSWORD',
  backup_db_server => $::fqdn,


Name for the backup


Whether to setup the backup set, defaults to present.


Databases to backup.


Hours to run the backup.


Database user to use for the backup.


Password for the backup user.


Database server.


Backupset config files and crons need stored configs on your puppet master. I recommend using PuppetDB for this.


All development, testing and releasing is done by Abstract IT at this stage. If you wish to join in let me know.


Please log tickets on the github issues page