Permacomputing

I'm not a fan of backups. They are a special path that is orthogonal to how you use computers, meaning it's additional time and energy you need just for finding relevant hosts, doing the copies regularly and most of all *actually test that the copy went well* (ie test the backup) which gets more and more irportant the longer your system is in place.

I opted for a different strategy: I have a folder for my photos and another folder for my "Documents" (at large). They both exist on my computer and on my phone and are synchronised with syncthing. I also have extra copies on other servers, one of which keeps old versions but I have never had the actual use for it, which is good because I have never checked it works correctly.

Compared to a backup I have the thing that works seamlessly in the background (I don't fiddle with some shell scripts that fail because I put single quotes instead of double quotes), I actually test the oopy works because I use files on two different devices, and the fact that everything is bluntly copied means I am forced to think "is it worth keeping". I aim to keep my folders under 50GB combined, which is a lot for a phone but nothing in the grand scheme of thing. Most of that is actually videos I pre-download to watch them online while on the move but that's another thing.

Syncthing means I can trivially add new devices as life goes on and old ones die

@permacomputing

have 2 flash/hard/whatever drives: A and B

once a month (or at what ever frequency you can sustain)

backup your data to A and next cycle backup your data to B

nothing fancy or technical, just some basic consistent backups.

if you can do that you'll likely be fine. There are nearly infinitely many enhancements you can do if you are more technical or can follow technical instructions.

My typical backup system:

• a computer that needs backing up in on a network
• the computer hosting backups is on that network
• [optional] the backup host is either powered down, or has brought its network connection down (so it's not visible and not hackable)
• at a predetermined time, the backup host wakes (brings its network connection up)
• it checks if the backup source is present, aborting if not
• it logs in via SFTP (an FTP-like protocol built on top of SSH) with public key authentication and pulls the backups down from the source according to a script (SFTP can do a list of tasks basing on a command script)
• after successful download (but not after a failure to download) it searches for too old backups and erases them ¹
• finally the backup host powers down or leaves the network
• optional final step: occasionally, a disk image of the backup host is taken, the memory card is put in a bottle, the cap is screwed on tight and the bottle is hidden under a stone :)

Regarding data protection: ideally, both computers use disk encryption. Especially the backup host, since it's unattended and could be taken by a burglar (or a cop), and holds the private key that can access the backup source.

¹ erasing old stuff is easy enough in Linux/Bash:

for i in `seq 5 10`;
do
     DATE=$(date --date "$i days ago" +%Y%m%d)
     echo "Deleting backups from $i days ago, that is [$DATE]."
     # do something
done

...generates a sequence of past dates ranging from 5..10 days in the past, attempts to delete something for each. Or alternatively, for those who like fancier, shorter and a bit more risky commands...

find ${BACKUP_DIR}/backup*.tgz -mtime +10 -exec rm {} \;

...finds files in directory $BACKUP_DIR named "backup*.tgz" and if modification time is older than 10 days, passes them as arguments to "rm".