A backup plan

After much hemming and hawing I have finally, finally settled on a suitable 3-2-1 backup plan that works for my budget, runs unattended, alerts me when there's a problem, and only uses programs and services that I don't find objectionable. That's a lot to pack into one sentence, so let's break it down. My entire backup strategy is based around Borgmatic. After looking into a number of options, including a custom script, vanilla borg, restic, rclone, and a few others, I determined that Borgmatic was going to be the most configurable and most hands-off solution that would reliably work for my needs. Borgmatic uses a .yaml-based configuration, which is cool with me. In a minimal configuration, you will choose the directories you want to include in your backups ("source directories") and the destinations that the source directories will be backed up to ("repositories"). To achieve a satisfactory level of backup redundancy, you'll want at least two, and so in my setup, I have two…