I see many posts asking about what other lemmings are hosting, but I’m curious about your backups.
I’m using duplicity myself, but I’m considering switching to borgbackup when 2.0 is stable. I’ve had some problems with duplicity. Mainly the initial sync took incredibly long and once a few directories got corrupted (could not get decrypted by gpg anymore).
I run a daily incremental backup and send the encrypted diffs to a cloud storage box. I also use SyncThing to share some files between my phone and other devices, so those get picked up by duplicity on those devices.
Restic using resticprofile for scheduling and configuring it. I do frequent backups to my NAS and have a second schedule that pushes to Backblaze B2.
Another +1 for restic. To simplify the backup I am however using https://autorestic.vercel.app/, which is triggered from systemd timers for automated backups.
Backups? What backups?
Ik it’s bad but I can’t be bothered.
wing and a pray baby!
In the process of moving stuff over to Backblaze. Home PCs, few clients PCs, client websites all pointing at it now, happy with the service and price. Two unraid instances push the most important data to an azure storage a/c - but imagine i’ll move that to BB soon as well.
Docker backups are similar to post above, tarball the whole thing weekly as a get out of jail card - this is not ideal but works for now until i can give it some more attention.*i have no link to BB other than being a customer who wanted to reduce reliance on scripts and move stuff out of azure for cost reasons.
Would I be correct to assume you are using Backblaze PC backup rather than B2?
Cross my fingers 🤞
3 2 1 with Restic and B2
I’m paying Google for their enterprise gSuite which is still “unlimited”, and using rclone’s encrypted drive target to back up everything. Have a couple of scripts that make tarballs of each service’s files, and do a full backup daily.
It’s probably excessive, but nobody was ever mad about the fact they had too many backups if they needed them, so whatever.
I back up everything to my home server… then I run out of money and cross my fingers that it doesn’t fail.
Honestly though my important data is backed up on a couple of places, including a cloud service. 90% of my data is replaceable, so the 10% is easy to keep safe.
Irreplaceable media: NAS->Back blaze NAS->JBOD via duplicacy for versioning
Large ISOs that can be downloaded again, NAS -> JBOD and or NAS -> offline disks.
Stuff that’s critical leaves the house, stuff that would just cost me a hell of a lot of personal time to rebuild just gets a copy or two.
I use syncthing to sync files between phone, pc and server.
The server runs proxmox, with a proxmox backup server in VM. A raspberry pi pulls the backups to an usb ssd, and also rclone them to backblaze.
Syncthing is nice. I don’t backup my pc, as it is done by the server. Reinstalling the pc requires almost no preparation, just set up syncthing again
What’s my what lmao?
I run a restic backup to a local backup server that syncs most of the data (except the movie collection because it’s too big). I also keep compressed config/db backups on the live server.
I eventually want to add a cloud platform to the mix, but for now this setup works fine
I have an external hard drive that I keep in the car. I bring it in once a month and sync it with the server. The data partition is encrypted so that even if it were to get stolen, the data itself is safe.
I have a similar 321 strategy without using someone else’s server and needing to traverse the internet. I keep my drive in the pool shed, since if my house was to blow up or get robbed, the shed would probably be fine.
I run all of my services in containers, and intentionally leave my Docker host as barebones as possible so that it’s disposable (I don’t backup anything aside from data to do with the services themselves, the host can be launched into the sun without any backups and it wouldn’t matter). I like to keep things simple yet practical, so I just run a nightly cron job that spins down all my stacks, creates archives of everything as-is at that time, and uploads them to Wasabi, AWS S3, and Backblaze B2. Then everything just spins back up, rinse and repeat the next night. I use lifecycle policies to keep the last 90 days worth of backups.
I like the cut of your jib!
Any details on the scripts?