BACKUPNINJA(1)
πΈ NAME πΈ
okay so, bestie, meet BACKUPNINJA β a lightweight, extensible meta-backup system, and its whole entire tagline is "a silent flower blossom death strike to lost data." π
iconic behavior honestly. this is backupninja(1), section 1 of the manual, and she is here to make your backups not a whole tragedy. π¦
β¨ SYNOPSIS β¨
backupninja [ -h ] [ -v ] [ -d ] [ -n ] [ -t ] [ -f filename ] [ --run
filename ]
ngl the synopsis says-vand the options list below says-Vand i'm literally just the messenger bestie, i copy what the page says, i don't editorialize π₯
π DESCRIPTION π
Backupninja lets you coordinate system backups by dropping a few simple configuration files into /etc/backup.d/. π
Here's the tea: most programs you might use for making backups don't have their own configuration file format. Backupninja is your centralized girl β she configures and coordinates many different backup utilities, all from one place. no cap. π
π¦ FEATURES π¦
- easy to read ini style configuration files. β¨
- you can drop in scripts to handle new types of backups. π«Ά
- backup actions can be scheduled. β°
- you can choose when status report emails are mailed to you: always, on warning, on error, or never. π¬
- the console-based wizard,
ninjahelper, makes it easy to create backup action configuration files. π§ - passwords are never sent via the command line to helper programs. π (we love a security-conscious queen)
- in order to backup a db or sql database, you cannot simply copy database files. backupninja helps you safely export the data to a format which you can backup. π
Backup types include:
- secure, remote, incremental filesystem backup (via
rdiff-backup). incremental data is compressed. permissions are retained even with an unprivileged backup user. π - basic system and hardware information. π₯οΈ
- encrypted remote backups (via
duplicity). π - safe backup of MySQL, PostgreSQL, OpenLDAP, and subversion databases. ποΈ
- burn CD/DVDs or create ISOs. πΏ
π OPTIONS π
-h,--helpβ Show summary of options. your little helper bestie. π-V,--versionβ Show backupninja version number. so you know exactly which queen you're talking to. π-d,--debugβ Run in debug mode, where all log messages are output to the current shell. everything is out loud now. π-f,--conffileCONF_FILE β Use CONF_FILE for the main configuration instead of/etc/backupninja.conf. choose your own adventure. π-t,--testβ Run in test mode, no actions are actually taken. a dress rehearsal, zero commitment. π-n,--nowβ Perform actions now, instead of when they might be scheduled. main character energy, no waiting. π₯--runACTION_FILE β Runs the action configuration ACTION_FILE and exits. one and done. β
π CONFIGURATION π
General settings are configured in /etc/backupninja.conf. In this file you can set the log level and change the default directory locations. See backupninja.conf(5). π«Ά
To preform the actual backup actions, backupninja processes each action configuration file in /etc/backup.d according to the file's suffix. See backup.d(5). ποΈ
π EXAMPLE USAGE π
Backupninja can be used to implement whatever backup strategy you choose. It is intended, however, to be used like so:
First, databases are safely copied or exported to /var/backups. Often, you cannot make a file backup of a database while it is in use, hence the need to use special tools to make a safe copy or export into /var/backups. ποΈβ¨
Then, vital parts of the file system, including /var/backups, are nightly pushed to a remote, off-site, hard disk (using rdiff-backup). The local user is root, but the remote user is not privileged. Hopefully, the remote filesystem is encrypted. π
In order for this to work (ie for diff-backup to run unattended), you must create ssh keys on the source server and copy the public key to the remote user's authorized keys file. For example:
root@srchost# ssh-keygen -t rsa -b 4096
root@srchost# ssh-copy-id -i /root/.ssh/id_dsa.pub
backup@desthost
Now, you should be able to ssh from user root on srchost to user backup on desthost without specifying a password. When prompted for a password by ssh-keygen, just leave it blank by hitting return. The "wizard" ninjahelper(1) will walk you through these steps. π§βοΈ
β EXIT VALUES β
0β success π1β errors or warnings emitted during backup π¬2β one or more backup actions failed π3β syntax or usage error π
π FILES π
/usr/sbin/backupninjaβ main script π/etc/backupninja.confβ main configuration file; general options βοΈ/etc/cron.d/backupninjaβ runs main script hourly β°/etc/logrotate.d/backupninjaβ rotatesbackupninja.logπ/etc/backup.dβ directory for configuration files ποΈ/usr/share/backupninjaβ directory for handler scripts π οΈ/usr/share/doc/backupninja/examplesβ example action configuration files. π
πΈ SEE ALSO πΈ
ninjahelper(1), backupninja.conf(5), backup.d(5), π«Ά
π AUTHOR π
BACKUPNINJA was written by the riseup.net collective. πΉ absolute legends, periodt.
and that's the whole page bestie!! π this one came from the backupninja package, footer says riseup and the date is October 10, 2005 β so yeah, vintage icon behavior, still slaying. go make some backups, ily, bye!! ππ¦β¨
π¦ where this page comes from
- debian bookworm: backupninja 1.2.2-1
- debian trixie: backupninja 1.2.2-1
- epel 10: backupninja 1.2.2-6.el10_0 Β· GPL-2.0-only
- epel 9: backupninja 1.2.2-1.el9 Β· GPLv2
- fedora 43: backupninja 1.2.2-8.fc43 Β· GPL-2.0-only
- fedora 44: backupninja 1.2.2-10.fc44 Β· GPL-2.0-only
- opensuse-leap 16.0: backupninja 1.2.2-bp160.1.9 Β· GPL-2.0-only
- opensuse-leap 16.0: backupninja 1.2.2-bp160.1.9 Β· GPL-2.0-only
- opensuse-leap 16.0: backupninja 1.2.2-bp160.1.9 Β· GPL-2.0-only
- opensuse-leap 16.0: backupninja 1.2.2-bp160.1.9 Β· GPL-2.0-only
- ubuntu jammy: backupninja 1.2.1-1
- ubuntu noble: backupninja 1.2.2-1
- ubuntu resolute: backupninja 1.2.2-1build1
- ubuntu stonking: backupninja 1.2.2-1build1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms