Selfhosted

I do exactly the same. I do not have a lot of data I feel a need to backup. I have a nightly job that zips and then encrypts my data, then rclones it to off site storage.

I've finally settled on Duplicacy. I've tried several CLI tools, messed with and love rclone, tried the other GUI backup tools, circled back to Duplicacy.

I run a weekly app data backup of my unRAID docker containers, which is stored on an external SSD attacked via USB to the server. The day after that runs duplicacy does a backup of that folder to Backblaze B2. My Immich library is backed up nightly and also sent to B2 via Duplicacy. Currently, those are the only bits of critical data on the server. I will add more as I finalize a client backup for the Win10, Linux, and MacOS devices at home, but it will follow this trend.

I use borg

I am a simple man, and like simple setups that's easy to maintain.

When it comes to my pictures and private data, I have them on one portable disk, that I rsync over to another portable disk on a monthly basis.

When it comes to my application logs and data, I back them up to a S3-compatible bucket with s3-cmd, through the frequency of my choosing as a cron-job. The S3 bucket is configured for "write once, read many" mechanism to avoid alternation of the data. And if the cron-job fails, I get a notification through ntfy.

Quite simple, and robust.

Usb drive

Nightly backups to an on-prem NAS. Then an rsync to a second off-site NAS at my folks house.

For a long time I did 1 hot copy (e.g. on my laptop), 1 LAN/homelab copy (e.g. Syncthing on a VM), and 1 cloud copy ... less a backup scheme than a redundancy scheme, albeit with file versioning turned on on the homelab copy so I could be protected from oopsies.

I'm finally teaching myself duplicity in order to set up a backup system for a webdev business I'm working on ... it ain't bad.

I have a compressed copy of the config files on my server on a separate drive, and every night restic makes a snapshot and stores it in a separate drive attached to a raspberry pi 3.

rsync over ssh (my server is in the next room) which puts the backup on an internal drive. I also have an inotify watch to zap a copy from there to an external USB drive.

zfs send

Backend storage is all ZFS. I have a big external drive plugged in via USB on my ZFS box and that backs up my daily backups.

I have a two old PCs that I run ZFS on as well. One auto turns on every week and ZFS backs up to that. The other PC is completely manual and I just randomly turn that on and backup. Every so often. Usually every 2-4 weeks.

For off-site backups. I use Syncthing and it is running on a server at a families house. Few miles away.

I picked Syncthing over ZFS because I actually a little more than an off-site I wanted a two way sync between our two locations so both locations could have a local copy they can edit and change.

I still need to get it set up, but I'll have 3: One on my NAS, one on a local USB drive, and one offline backup. I'll use rsync for the job.

ZFS

I do a Clonezilla image on an old 3.5'' drive from time to time, most of my documents are stored on the cloud so I'm pretty safe in terms of 'uptodateness'

Illuminated Binary Manuscripts.

The main storage is a Nas that is mounted in read only most of the time and has two drives in raid mirror. Plus rclone to push a remote and client side encrypted backup to backblaze.

I have my data backed up locally on an HDD, though I'm planning on building a server machine to hold more data with parity (not just for backups). Important data I have backed up in Google drive and Proton drive, both encrypted before upload. It isn't that big, I don't back up media or anything in the cloud. Oh and I have some stuff in mega, but I stopped adding to that years ago. I should probably delete that account, thanks for the reminder!

Cheap second NAS that I power up every now and again, then I run a dsynchronize profile which replicates the important stuff (video), and all the stuff I could never replace I put on a usb and keep it elsewhere

Encrypted files sent to Google Cloud Storage (bucket) for long-term archival. Comes out pretty cheap like that.