How I do backups
I updated my backup strategy and this page in 2022.
Until 2019, my backup strategy was not very sophisticated: I occasionally made backups of my notebook on an external hard drive, using the command line tool
rsync. It was a manual process, and I didn’t have a regular schedule, which meant that I basically only made a backup “when I thought of it” (often several months apart). If my notebook had been stolen, I would’ve lost a lot of work.
In 2019, I set up automated backups using borg, borgmatic, and rsync. My server had a backup of my notebook on it, and the other way around. If one of them exploded, I could’ve restored it using the other. This worked well, but eventually, my server ran out of disk space, and adding more storage would’ve been rather expensive.
In 2022, I switched to restic, another great open source de-duplicated backup solution, which felt a bit simpler and faster compared to borg. The only downside is that it needs more storage space, because it doesn’t compress the backups.
For storing the (encrypted) backups, I’m using Backblaze. They charge 5 USD to store 1 TB of data for a month, that seems very fair to me. I currently pay around 2 USD per month. I’d like something self-hosted even better, but I also badly needed to make automated backups happen again.
This page is documenting how I set up my backups, and how to restore them, mostly for myself. :P
- Register a Backblaze account, and create a bucket.
- Then, follow this guide.
- If your notebook explodes, get a new machine, and install restic.
- Log into backblaze.com using my main email account. You’ll need the Backblaze password.
- At “Account -> App Keys”, create a new application key, and write down the keyID and the actual keyphrase.
- Set the environment variable
B2_ACCOUNT_IDto the keyID, and
B2_ACCOUNT_KEYto the keyphrase.
restic -r b2:blinry-restic mount directory/to/mount/to, you’ll need the password of the blinry-restic backup for this step.
- Copy out all of what you need.
I store all my passwords in a password manager called gopass. It’s a minimalist command line tool, and a reimplementation of the classic password manager pass. The passwords are stored as GPG-encrypted files in
~/.password-store/ on my notebook.
To install and set up gopass, basically follow the instructions on gopass.pw.
To access the passwords, you need physical access to your notebook and the passphrase for your GPG key. If you don’t have access to your notebook, you’ll need the password for the user account on your server, the keyfile (see below) and the passphrase for the backup of your notebook, and the passphrase for your GPG key.
So I put some more thought into it. My backup strategy revolves around two devices: my notebook “thinkerbell” and my server “morr.cc”. At this point, Internet connections are fast, and online storage is cheap, so I just store a backup of my server on the notebook, and a backup of my notebook on the server, using a combination of
gopass. The backups are fully automated and run once per day.
The motivation for this post is threefold: first and foremost, I wanted to write documentation for myself on how I do backups, and how to restore them. Second, I want to give you all the resources you need to set up a similar system for yourself. And third, this might be useful information in an emergency – some people I trust have access to my secrets listed below.
I do daily, nonincremental, unencrypted backups of all files on my server to my notebook, using
rsync. Most projects which are deployed on my server I have locally versioned in Git anyway, so a single copy of the server’s files seems sufficient. I mostly care about configuration and log files, and it wouldn’t be catastrophic if I lost them.
Make a copy of the
backup-server script. It uses
rsync to make a full copy of the remote host, excluding some irrelevant directories, and especially excluding the directory where the notebook backup is stored, avoid cyclic backups (see below). Modify it to your liking. The script uses gopass to read the root password of the remote host, and stores the backup locally in
Set up a systemd timer to run the
backup-server script each day. Copy the two
backup-server.* files from my dotfiles repo to your local
~/.config/systemd/user/ directory, and run this command:
systemctl --local enable backup-server.timer
Alternatively, you could use a cronjob.
If your server explodes, you still have a snapshot of all files on your notebook, which you’ll need physical access to. Get a new server, and either install a base system and copy back the files you need. Or if your hoster has the option to mount the server’s complete emtpy file system, you can try to copy back all the files, I guess?
I do daily, incremental, encrypted backups of my notebook’s home directory to my server using borg. I really care about many files on my notebook!
Install borg (a command line tool for making incremental, encrypted backups) and borgmatic (a wrapper script for borg which simplifies its use). Create a copy of my borgmatic config, and modify it to your liking. Take care to exclude the location of the server backup to avoid cyclic backups. borg supports multiple modes to encrypt backups, we will use the “keyfile” mode, which stores an encrypted keyfile in
~/.config/borg/keys/. My configuration uses gopass to read the passphrase for decrypting borg’s keyfile, so you need to create one before you continue.
borgmatic init --encryption keyfile to initialize your backup. To make actually make a backup, you can use my (pretty trivial) backup script, which basically just runs the command
borgmatic prune create.
Setup a systemd timer to run the
backup script each day. Copy the two
backup.* files from my dotfiles repo to your local
~/.config/systemd/user/ directory, and run this command:
systemctl --local enable backup.timer
Again, alternatively, you can use a cronjob.
If your notebook explodes, get a new machine, and install borg. You’ll need the keyfile, its passphrase, and the password for the remote user on the server who owns the backup directory. Copy the keyfile to
~/.config/borg/keys/. To list the available snapshots, run the following command:
borg list firstname.lastname@example.org:~/permanent/backups/thinkerbell/
To list the contents of an available snapshot, run a command like this:
borg list \ email@example.com:~/permanent/backups/thinkerbell/::thinkerbell-YYYY-MM-DDTHH:MM:SS.mmmmmm
To extract files from an available snapshot, run a command like this, or leave out the filename to extract everything:
borg extract \ firstname.lastname@example.org:~/permanent/backups/thinkerbell/::thinkerbell-YYYY-MM-DDTHH:MM:SS.mmmmmm home/seb/wip/cool-project/
To summarize, the passwords you need to access all of my stuff are the following:
- The password for seb@thinkerbell, the user account on my notebook.
- The password for email@example.com, the user account on my server.
- The passphrase for the GPG key A624F8B6, which is used by gopass to encrypt my passwords.
- The passphrase for the keyfile, which is used by borg to encrypt the notebook backup.
In addition, you’ll need the following two files:
- My GPG private key (for the key A624F8B6) used by gopass to encrypt my passwords.
- The keyfile used by borg to encrypt the notebook backup.
I hope this gives you an idea of how all the components I use for making backups play together. If you try implementing a similar system for yourself, and get stuck at any point, don’t hesitate to ask me for help! :)
Send a message to @firstname.lastname@example.org or drop me a mail at email@example.com. Also, you can support me on Patreon or subscribe to my newsletter!