Backups are important ok? I know that. You should know that. So, why don't most people do
proper backups of their computers?
Because most of the ways to do backups are either inconvenient or useless.
So, here's how the solution I have implemented that makes backups convenient and useful.
The backup tool itself
I use restic because it kicks ass. It works, it's fast,
it's space efficient, and it's easy.
You just need to write a short script like this one:
# Where to backup?
if [ -d $BACKUPDIR ]
# Backups are password protected
# What to backup
restic -r $BACKUPDIR --verbose backup \
--exclude ~ralsina/.cargo \
--exclude ~ralsina/.local/share/Steam/ \
--exclude ~ralsina/.cache \
--exclude ~ralsina/.config/google-chrome/ \
--exclude ~ralsina/.rustup \
--exclude ~ralsina/.npm \
--exclude ~ralsina/.gitbook \
# Keep at most one backup for the last 7 days that have backups
restic -r $MOUNTDIR/backup-pinky forget --prune --keep-daily=7
restic -r $MOUNTDIR/backup-pinky prune
# Make really sure things are stored
sync; sync; sync; sync
Backup rule 3-2-1
The 3-2-1 rule:
- 3 copies of the backup data (1 primary, 2 copies)
- 2 different media
- 1 must be offsite
In my case, these are:
- Primary backup is to disk
- Secondary backup is to a disk in another machine (similar script, using sftp)
- Tertiary backup is to a pen drive (different media) I then put in my pocket (offsite).
To perform the primary and secondary backups, it's just two slightly different versions of that script (actually, it's just one script with arguments, left as
an exercise for the reader).
The tertiary backup is a bit more complicated, because I wanted it to be convenient
The Convenient Way To Backup to a Removable Drive
My user story was this:
As a person that needs an offsite backup but don't want to transmit all that data, I want to plug a pen drive into the machine and have it AUTOMATICALLY start backing the data into the pen drive.
Then, once the backup is finished, at some point, I can just unplug it and take it with me.
Let's just say that finding a way that works took me a few hours and I am pretty sure my solution is more complicated than it needs to be. But hey, it works, so it's good enough.
This being Linux and the year being 2022 ... this solution involves systemd. And because it's systemd, it's complicated.
First part is we need to mount the pen drive automatically in a well known location. For this we need two things. An automount service, so systemd will automatically mount something in
And a mount service so it knows what to mount in
/backup and how:
The interesting parts are:
backup.service is going to be a systemd service that actually runs the backup script. We want it to run, and to run AFTER the device is mounted.
What: Where is the mountpoint, and What is the pen drive's UUID as shown by
Enable and start the automount service, no need to do anything to the mount one.
Then of course we need the backup service itself. Just a "oneshot". When it's started, it runs the backup script:
Enable but don't start this service. Since it's "Wanted" by the mount, that means when the device is effectively mounted the backup will start.
OR THAT WOULD IT DO IF THINGS MADE SENSE.
Sadly, the device is only mounted when, after being inserted, something tries to use the mountpoint. So, with these three services installed nothing happens unless, after you plug the pen drive you go and do something like
ls /backup, which triggers the
mount, which triggers the backup script.
So, how does one fix that? No idea. My workaround was to add TWO MORE SERVICES, so that
ls /backup runs every minute.
Description=Try to run backup
And with that, yes, I can just plug the pen drive when I get to the office in the morning and unplug it later, knowing there is a backup in it.