btrbk/README.md

399 lines
11 KiB
Markdown
Raw Normal View History

2015-02-07 15:53:21 +01:00
Introduction
============
btrbk is a backup tool for btrfs subvolumes, taking advantage of btrfs
specific capabilities to create atomic snapshots and transfer them
incrementally to your backup locations.
The source and target locations are specified in a config file, which
allows to easily configure simple scenarios like "laptop with locally
attached backup disks", as well as more complex ones, e.g. "server
receiving backups from several hosts via ssh, with different retention
policy".
2015-02-07 15:53:21 +01:00
Key Features:
- Atomic snapshots
- Incremental backups
- Configurable retention policy
2015-02-07 15:53:21 +01:00
- Backups to multiple destinations
- Transfer via ssh
- Resume of backups (if backup target was not reachable for a while)
2015-02-07 15:53:21 +01:00
- Display file changes between two backups
btrbk is intended to be run as a cron job.
Installation
============
btrbk comes as a single executable file (perl script), without the
need of any installation procedures. If you want the package and
man-pages properly installed, follow the instructions below.
Prerequisites
-------------
- [btrfs-progs]: Btrfs filesystem utilities (use "btrfs_progs_compat"
option for hosts running version prior to v3.17)
- Perl interpreter: probably already installed on your system
- [Date::Calc]: Perl module
2015-02-07 15:53:21 +01:00
[btrfs-progs]: http://www.kernel.org/pub/linux/kernel/people/kdave/btrfs-progs/
[Date::Calc]: http://search.cpan.org/perldoc?Date::Calc
2015-02-07 15:53:21 +01:00
Instructions
------------
In order to install the btrbk executable along with the man-pages and
an example configuration file, choose one of the following methods:
### Generic Linux System
Download and unpack the newest stable [btrbk source tarball] and type:
2015-02-07 15:53:21 +01:00
sudo make install
### Debian Based Distros
Download the newest stable [btrbk debian package], and
sudo dpkg --install btrbk_<version>_all.deb
### Gentoo Linux
Grab the digint portage overlay from:
`git://dev.tty0.ch/portage/digint-overlay.git`
emerge btrbk
2015-02-07 15:53:21 +01:00
### Arch Linux
btrbk is in AUR: https://aur.archlinux.org/packages/btrbk/
[btrbk source tarball]: http://www.digint.ch/download/btrbk/releases/
[btrbk debian package]: http://www.digint.ch/download/btrbk/packages/debian/
2015-02-07 15:53:21 +01:00
Synopsis
========
Please consult the [btrbk(1) man-page] provided with this package for a
2015-02-07 15:53:21 +01:00
full description of the command line options.
[btrbk(1) man-page]: http://www.digint.ch/btrbk/doc/btrbk.html
2015-02-07 15:53:21 +01:00
Configuration File
==================
Before running `btrbk`, you will need to create a configuration
file. You might want to take a look at `btrbk.conf.example` provided
with this package. For a detailed description, please consult the
[btrbk.conf(5) man-page].
2015-02-07 15:53:21 +01:00
When playing around with config-files, it is highly recommended to
check the output using the `dryrun` command before executing the
backups:
btrbk -c myconfig -v dryrun
This will read all btrfs information on the source/target filesystems
and show what actions would be performed (without writing anything to
the disks).
[btrbk.conf(5) man-page]: http://www.digint.ch/btrbk/doc/btrbk.conf.html
2015-02-07 15:53:21 +01:00
Example: laptop with usb-disk for backups
-----------------------------------------
In this example, we assume you have a laptop with:
- a disk having a btrfs volume mounted as `/mnt/btr_pool`, containing
a subvolume `rootfs` for the root filesystem and a subvolume `home`
for the user data.
- a backup disk having a btrfs volume mounted as `/mnt/btr_backup`,
containing a subvolume `mylaptop` for the incremental backups.
Retention policy:
- keep snapshots for 14 days (very handy if you are on the road and
the backup disk is not attached)
- keep monthly backups forever
- keep weekly backups for 10 weeks
- keep daily backups for 20 days
/etc/btrbk/btrbk-mylaptop.conf:
snapshot_preserve_daily 14
snapshot_preserve_weekly 0
snapshot_preserve_monthly 0
target_preserve_daily 20
target_preserve_weekly 10
target_preserve_monthly all
snapshot_dir btrbk_snapshots
volume /mnt/btr_pool
2015-03-27 00:57:43 +01:00
subvolume rootfs
2015-02-07 15:53:21 +01:00
target send-receive /mnt/btr_backup/mylaptop
2015-03-27 00:57:43 +01:00
subvolume home
2015-02-07 15:53:21 +01:00
target send-receive /mnt/btr_backup/mylaptop
/etc/cron.daily/btrbk:
#!/bin/bash
/usr/sbin/btrbk -c /etc/btrbk/btrbk-mylaptop.conf run
2015-02-07 15:53:21 +01:00
- This will create snapshots on a daily basis:
- `/mnt/btr_pool/btrbk_snapshots/rootfs.YYYYMMDD`
- `/mnt/btr_pool/btrbk_snapshots/home.YYYYMMDD`
- And create incremental backups in:
- `/mnt/btr_backup/mylaptop/rootfs.YYYYMMDD`
- `/mnt/btr_backup/mylaptop/home.YYYYMMDD`
If you want the snapshots to be created only if the backup disk is
attached, simply add the following line to the config:
2015-02-07 15:53:21 +01:00
snapshot_create ondemand
2015-02-07 15:53:21 +01:00
Example: host-initiated backup on fileserver
--------------------------------------------
Let's say you have a fileserver at "myserver.mydomain.com" where you
2015-02-07 15:53:21 +01:00
want to create backups of your laptop disk, the config would look like
this:
ssh_identity /etc/btrbk/ssh/id_rsa
volume /mnt/btr_pool
2015-03-27 00:57:43 +01:00
subvolume rootfs
2015-02-07 15:53:21 +01:00
target send-receive /mnt/btr_backup/mylaptop
target send-receive ssh://myserver.mydomain.com/mnt/btr_backup/mylaptop
In addition to the backups on your local usb-disk mounted at
`/mnt/btr_backup/mylaptop`, incremental backups would also be pushed
to `myserver.mydomain.com`.
Example: fileserver-initiated backups from several hosts
--------------------------------------------------------
If you're a sysadmin and want to trigger backups directly from your
fileserver, the config would be something like:
ssh_identity /etc/btrbk/ssh/id_rsa
volume ssh://alpha.mydomain.com/mnt/btr_pool
subvolume rootfs
target send-receive /mnt/btr_backup/alpha
subvolume home
target send-receive /mnt/btr_backup/alpha
volume ssh://beta.mydomain.com/mnt/btr_pool
subvolume rootfs
target send-receive /mnt/btr_backup/beta
subvolume dbdata
target send-receive /mnt/btr_backup/beta
This will pull backups from alpha/beta.mydomain.com and locally create:
- `/mnt/btr_backup/alpha/rootfs.YYYYMMDD`
- `/mnt/btr_backup/alpha/home.YYYYMMDD`
- `/mnt/btr_backup/beta/rootfs.YYYYMMDD`
- `/mnt/btr_backup/beta/dbdata.YYYYMMDD`
Example: local time-machine (daily snapshots)
---------------------------------------------
If all you want is to create snapshots of your home directory on a
regular basis:
/etc/btrbk/btrbk.conf:
volume /mnt/btr_pool
snapshot_dir btrbk_snapshots
subvolume home
/etc/cron.daily/btrbk:
#!/bin/bash
/usr/sbin/btrbk run
Note that you can run btrbk more than once a day, e.g. by creating the
above script in `/etc/cron.hourly/btrbk`, or by calling `sudo btrbk
run` from the command line.
Example: multiple btrbk instances
---------------------------------
Let's say we have a host (at 192.168.0.42) running btrbk with the
setup of the time-machine example above, and we need a backup server
to only fetch the snapshots.
/etc/btrbk/btrbk.conf (on backup server):
volume ssh://192.168.0.42/mnt/btr_pool
subvolume home
snapshot_dir btrbk_snapshots
snapshot_preserve_daily all
snapshot_create no
resume_missing yes
target_preserve_daily 0
target_preserve_weekly 10
target_preserve_monthly all
target send-receive /mnt/btr_backup/my-laptop.com
If the server runs btrbk with this config, the latest snapshot (which
is *always* transferred), 10 weeklies and all monthlies are received
from 192.168.0.42. The source filesystem is never altered because of
`snapshot_preserve_daily all`.
2015-02-07 15:53:21 +01:00
Setting up SSH
==============
Since btrbk needs root access on the remote side, it is *very
advisable* to take all the security precautions you can. Usually
backups are generated periodically without user interaction, so it is
not possible to protect your ssh key with a password. The steps below
will give you hints on how to secure your ssh server for a backup
2015-02-07 15:53:21 +01:00
scenario.
btrbk provides a little shell script called "ssh_filter_btrbk.sh",
which only allows sane calls to the /sbin/btrfs command needed for
snapshot creation and send/receive operations. This is how it is used
with ssh:
**Step 1** (client): Create a ssh key dedicated to btrbk, without password protection:
ssh-keygen -t rsa -b 2048 -f /etc/btrbk/ssh/id_rsa -C btrbk@mydomain.com -N ""
**Step 2** (server): Copy the "ssh_filter_btrbk.sh" from the btrbk project to "/root/".
**Step 3** (server): Add contents of the public key
(/etc/btrbk/ssh/id_rsa.pub) to "/root/.ssh/authorized_keys",
restricting access from a single host:
from="192.168.0.42",command="/root/ssh_filter_btrbk.sh" ssh-rsa AAAAB3NzaC1...hwumXFRQBL btrbk@mydomain.com
Now your ssh server allows connections only from 192.168.0.42, and
will only execute commands needed by btrbk. Note that the btrbk
executable is not needed on the remote side, but you will need
"/sbin/btrfs" from the btrfs-progs package.
2015-05-05 12:44:18 +02:00
Restoring Backups
=================
btrbk does not provide any mechanism to restore your backups, this has
to be done manually. In the examples below, we assume that you have a
btrfs volume mounted at `/mnt/btr_pool`, and the subvolume you want to
have restored is at `/mnt/btr_pool/data`.
Example: Restore a Snapshot
-----------------------------
First, pick a snapshot to be restored:
btrbk tree
From the list, pick the snapshot you want to restore. Let's say it's
`/mnt/btr_pool/_btrbk_snap/data.20150101`.
If the broken subvolume is still present, move it away:
mv /mnt/btr_pool/data /mnt/btr_pool/data.BROKEN
Now restore the snapshot:
btrfs subvolume snapshot /mnt/btr_pool/_btrbk_snap/data.20150101 /mnt/btr_pool/data
That's it; your `data` subvolume is restored. If everything went fine,
2015-05-05 12:44:18 +02:00
it's time to nuke the broken subvolume:
btrfs subvolume delete /mnt/btr_pool/data.BROKEN
Example: Restore a Backup
-------------------------
First, pick a backup to be restored:
btrbk tree
From the list, pick the backup you want to restore. Let's say it's
`/mnt/btr_backup/data.20150101`.
If the broken subvolume is still present, move it away:
mv /mnt/btr_pool/data /mnt/btr_pool/data.BROKEN
Now restore the backup:
btrfs send /mnt/btr_backup/data.20150101 | btrfs receive /mnt/btr_pool/
btrfs subvolume snapshot /mnt/btr_pool/data.20150101 /mnt/btr_pool/data
btrfs subvolume delete /mnt/btr_pool/data.20150101
Alternatively, if you're restoring data on a remote host, do something
like this:
btrfs send /mnt/btr_backup/data.20150101 | ssh root@my-remote-host.com btrfs receive /mnt/btr_pool/
If everything went fine, nuke the broken subvolume:
btrfs subvolume delete /mnt/btr_pool/data.BROKEN
2015-02-07 15:53:21 +01:00
Development
===========
Source Code Repository
----------------------
The source code for btrbk is managed using Git. Check out the source
like this:
git clone git://dev.tty0.ch/btrbk.git
How to Contribute
-----------------
Your contributions are welcome!
If you would like to contribute or have found bugs:
2015-03-27 00:57:43 +01:00
- Visit the [btrbk project page on GitHub] and use the [issues
tracker] there.
- Talk to us on Freenode in `#btrbk`.
2015-03-27 00:57:43 +01:00
- Contact the author via email (the email address can be found in the
sources).
Any feedback is appreciated!
[btrbk project page on GitHub]: http://github.com/digint/btrbk
[issues tracker]: http://github.com/digint/btrbk/issues
2015-02-07 15:53:21 +01:00
License
=======
btrbk is free software, available under the [GNU General Public
License, Version 3][GPLv3].
[GPLv3]: http://www.gnu.org/licenses/gpl.html