Selfhosted

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 have two machines that back up to a local server using Borg. That whole server in turn backs up to Jottacloud using restic with encryption enabled.

By the way, I wouldn't use rclone for backups. Use restic or something similar that does incremental backups. Because if you do rclone and then later discover that some files were corrupted locally, then your files are gone. With incremental backups you would still be able to retrieve them.

Oh, or do you mean backing up the stuff that is on the cloud?

I backup my ESXi VMs and NAS file shares to local server storage using an encrypted Veeam job and have a copy job to a local NAS with iSCSI storage presented.

From there I have another host VM accessing that same iSCSI share uploading the encrypted backup to Backblaze. Unlimited "local" storage for $70\y? Yes please! (iSCSI appears local to Backblaze. They know and have already started they don't care.)

I'm backing up about 4TB to them currently using this method.

Right now just a spare hard drive on a pi that I rsync too, but I'm looking for better options as well.

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.

I use borg

restic to Wasabi.

I miss back in the day. Used to be able to store all my stuff on CD-R's, hell before that it was floppy's. File sizes have grown exponentially, programs/apps all have huge sizes. Pictures and videos is my biggest issue, but I'd also like to backup games that I've downloaded so I don't have to download again. I can backup old games no problem, but modern games? Many are 100+ GB now, and in time they all will be and 200GB will be the standard, then a terabyte and more.

Anyway, until I can afford and find a 20 tb sad I'm just using DVDs for everything but games and large programs. Quick to write, solid, tangeable etc. If I could afford a bunch of flash drives I'd probably do that instead.

If you can afford it and it's important data I'd ofc recommend backing up to a large SSD, THEN to a cloud (or more) as a failsafe.. then also using flash drives/DVD's etc. For an additional failsafe for the super important stuff.

I mean, if it's important backup all you can.

I've got priceless memories in my Google photos library but ofc Google removed being able to view them on my native photos app and download easily.. so instead I either have to backup and save ALL of it in Google drive or download specific albums.. idk so I wouldn't personally recommend google as a true backup as you never know, personally I'd just use DVDs and flash drives for that stuff

ZFS

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.

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!

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

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.

My work is using Google drive for Sync/back up so that is covered by them.

Personal data is automatically synched (syncthing) between three computers in different rooms in my home + some of the files is copied to my phone and tablet. I consider adding also an online server for further redundancy

Backblaze. Easy and cheap. It’s fire and forget for the most part.

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

zfs send

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.

Usb drive

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.

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.

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.

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

Local versioning with btrfs rsync copy to other machine in home network rsync to NAS at my parents home