Off-site Backup with Backupninja: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 24: | Line 24: | ||
when = everyday at 05:55 | when = everyday at 05:55 | ||
=== MySQL === | ==== MySQL local backups ==== | ||
* | * As <code>root</code> run the command: | ||
ninjahelper | |||
* create a new backup action | * create a new backup action | ||
* mysql database backup | * mysql database backup | ||
Revision as of 10:16, 25 August 2018
Goal: Setup a remote machine that will be used for incremental backup of critical parts of the LURK servers.
Requirements
This document assumes you already have:
- A configure Linux/BSD machine to work as off-site backup
- A
lurkuser created on the off-site backup that will be used specifically by the backup scripts - Debian based servers (not sure Backupninja will run otherwise without some slight modifications)
- All the machines (servers and the backup machine) on a working Tinc VPN
- Enough space on the off-site backup machine :)
On the Off-site machine
- As
lurkcreate directories for each server
mkdir /media/lurk_backup/douglas /media/lurk_backup/agnesbaxter
On each server
Installation
- As
root
apt install backupninja
Configuration
/etc/backupninja.conf
Some changes:
reportemail = some@where.nice when = everyday at 05:55
MySQL local backups
- As
rootrun the command:
ninjahelper
- create a new backup action
- mysql database backup
- path:
/var/backups/mysql
- all the databases to backup.
- select the debian maintenance user for access
- compress the sql output file
- optional: select the action and test/run/review the config
- leave ninjahelper