Implementing a 3-2-1 Backup Strategy with restic and Backblaze B2

In order to follow a proper 3-2-1 backup strategy, you should have three copies of your important data: two local on different media types, and one off site. For local, I have a DAS with two 14TB drives configured in a RAID 1 array1 and a RPI5 with a 4TB drive (my most important data is around 1.5TB). For the off site copy, I opted to utilize Backblaze's B2 Cloud Storage and restic. Backblaze is a cloud storage provider, while Restic encrypts and chunks the files before upload. Restic is responsible for uploading, encryption/decryption, and deduplication. Set up a Backblaze B2 bucket To begin, I had to configure Backblaze. Create a Backblaze account Create a bucket (I called mine restic-ganymede) Under application keys, make a key. Be sure to copy the keyID and applicationkey as they're only shown only once. I keep this in my password manager notes for Backblaze "B2 Account ID and Key". In the bucket, select "Lifecycle Settings" and choose " Keep only the last version of the file" or…