Changes between Initial Version and Version 1 of how-to/puppet/backups

Jul 22, 2014, 10:33:26 AM (7 years ago)



  • how-to/puppet/backups

    v1 v1  
     1= backupninja =
     2Puppet uses the m_backupninja class to tell servers how to make backups.  This class is standard for all of our server manifests, and controls rdiff and rsync backups.  In standard manifests, a version of this stanza exists, which changes based on which backup servers the server writes to.:
     5if ( $::fqdn == "" ) or ( $::fqdn == "" ) {                                         
     6  m_backupninja::server::configure_node { "acholonu": }
     10== mysql backups ==
     11In addition servers can backup mysql databases.  By default MOSHes backup all mysql databases, and any server can be required to make daily mysql backups.
     13=== standard mysql backups ===
     14The standard mysql backup requires a single directive in the manifest file that looks like:
     17class { "m_backupninja::mysql": }
     20This stanza says, "Do a full backup of all mysql databases."  However, this is not always ideal as some of these databases can grow quite large due to caching and indexing tables, particularly for Drupal databases.
     22=== truncated mysql backups ===
     23If you need to reduce the size of mysql backups, you can do so by changing the m_backupninja stanza to:
     26class { "m_backupninja::mysql_diet" }
     29This stanza uses a [browser:puppet/modules/mayfirst/files/backupninja/ different backup script] which calls the [browser:puppet/modules/mayfirst/files/mysql-server/mf-mysql-dump mf-mysql-dump script], and this removes caching and other tables from the mysqldump to ease the weight of the actual dump.  If you run into problems with mysql dumps for Drupal sites, this is a good option for avoiding those problems.