Someone on Lemmy posted a phrase recently: “If you’re not prepared to manage backups then you’re not prepared to self host.”

This seems like not only sound advice but a crucial attitude. My backup plans have been fairly sporadic as I’ve been entering into the world of self hosting. I’m now at a point where I have enough useful software and content that losing my hard drive would be a serious bummer. All of my most valuable content is backed up in one way or another, but it’s time for me to get serious.

I’m currently running an Ubuntu Server with a number of Docker containers, and lots of audio, video, and documents. I’d like to be able to back up everything to a reliable cloud service. I currently have a subscription to proton drive, which is a nice padding to have, but which I knew from the start would not be really adequate. Especially since there is no native Linux proton drive capability.

I’ve read good things about iDrive, S3, and Backblaze. Which one do you use? Would you recommend it? What makes your short list? what is the best value?

@xylogx@lemmy.world
link
fedilink
English
11M

I like S3 because I only pay for what I use and it has auto storage tiering.

I’ve been using pcloud. They do one time upfront payments for ‘lifetime’ cloud storage. Catch a sale and it’s ~$160/TB. For something long term like backups it seems unbeatable. To the point I sort of don’t expect them to actually last forever, but if they last 2-3 years it’s a decent deal still.

Use rclone to upload my files, honestly not ideal though since it’s meant for file synchronisation not backups. Also they are dog slow. Downloading my 4TBs takes ~10 days.

3,2,1.

My nas is a Synology with raid.

  1. Backup with versions to a single large HD via USB. This ransomware protection or accidental deletion. (Rsync)
  2. Offsite copy to backblaze b2.One version. (Rsync) (~$6/month) This would be natual disaster protection. flood, fire.
  3. Second not raided cheaper Synology at a friends on the other coast. This has ~3 versions. Sorta the backup to the first two.

3, 2, 1. ❤

Without implementing this, it’s a delusion that some company, regardless of the size and reputation, can be trusted to keep our data safe.

Also don’t forget to restore test, otherwise you may as well not do backups. I have a reminder for once a year to test them, not just if it works but also what the performance is just in case.

@qwexfle@lemmy.ml
link
fedilink
English
41M

This is the part that gets me. I don’t know how to automate this. I periodically retrieve something from the backups, which, so far, has worked. That’s not really good insurance, though. Any suggests or resources, ideally for borg and/restic?

tired_n_bored
link
fedilink
English
11M

How do you do versioning with rsync? I use rdiff.

Maybe it’s diff presented as versions? I use hyper backup on Synology.

Similar to these steps:

https://gist.github.com/mrl22/476d710fea63d71a770d0d44ca54325a

You can get append only backups on backblaze with their lifecycle rules. So that can have ransomware protection too

@peregus@lemmy.world
link
fedilink
English
31M

“Append only backup” what’s that?

@jagged_circle@feddit.nl
link
fedilink
English
3
edit-2
1M

Its a system where you can only apppend, not delete.

https://en.wikipedia.org/wiki/Append-only

Its what’s required for ransomware safe backup system, since the attacker can’t delete your backups because they can only append

@peregus@lemmy.world
link
fedilink
English
11M

Oh, I see, I didn’t know that “nomenclature”. Thanks! Good for some thing, dangerous for other because the stored data keeps growing.

@jagged_circle@feddit.nl
link
fedilink
English
1
edit-2
1M

With backblaze you can set lifcycle rules. For example, any file with the regex “daily” in it automatic gets deleted after 30 days. And any file with “yearly” in it gets deleted after 5 years

I use 2 matching Synology NAS systems. 1 backs up to the other daily. Then one of them backs up to Synology C2 weekly.

I use borgbackup to create backups. I point backups to another home computer and borgbase.com. Borg itself is an amazing tool. I think you should learn how it works even if it doesnt end up being the best fit for you.

One of few ransomware protected solutions

@peregus@lemmy.world
link
fedilink
English
11M

Nobody that uses Wasabi?

Too expensive

@peregus@lemmy.world
link
fedilink
English
11M

When I’ve signed up was the cheaper. I’ve just checked and it’s $6.99/TB/month and Backblaze B2 is actually cheaper ($6/TB/month). Are there other differences that you know of? There must be since everyone is using Baclblaze.

I prefer my local storage. Can’t vouch for any cloud storage.
Upside of Wasabi to my infrastructure: It’s compatible with Veeam.

grimer
link
fedilink
English
31M

My backup plan includes Backrest (restic) up to B2. So far so good!

I’ve been using rsync.net for a while now. It’s been stable, fast, and relatively inexpensive. There’s also the benefit that it’s easy to script automated backups directly to it. For more Dropbox-like functionality, I have a Nextcloud instance that uses rsync.net as external storage. It’s been great so far!

I like that I can interface with it in ways that I already understand (eg rclone, sync, sshfs).

Being able to run some commands on the server meant that I could use rclone to copy my AWS and OneDrive backups directly cloud-to-cloud.

@filister@lemmy.world
link
fedilink
English
11M

They require you to buy a minimum of 800Gb, which for most people is an overkill

@DarkAngelofMusic@lemmy.sdf.org
link
fedilink
English
1
edit-2
1M

Is it? I’m genuinely asking. I haven’t seen statistics on how much storage people looking for cloud backup solutions use, but to me, anything under 1TB seems too small to be worth it, these days.

Shimitar
link
fedilink
English
31M

First copy on offline USB disk on my server itself. Disk is turned on, backup done, disk goes off. Once a day.

Second copy on a USB drive connected to an OpenWRT router of my home, the furthest away from the server (in case of fire, I could be able to grab either of the two).

Third copy offsite on a VPS.

I use restic & backrest with great satisfaction.

I also restic to b2. Found it the best value.

Timely post.

I was about to make one because iDrive has decided to double their prices, probably because they could.

$30/tb/year to $50/tb/year is a pretty big jump, but they were also way under the market price so capitalism gonna capital and they’re “optimizing” or someshit.

I’ve love to be able to push my stuff to some other provider for closer to that $30, but uh, yeah, no freaking clue who since $60/tb/year seems to be the more average price.

Alternately, a storage option that’s not S3-based would also probably be acceptable. Backups are ~300gb, give or take, and the stuff that does need S3-style storage I can stuff in Cloudflare’s free tier.

Yeah, it was $2.5/tb/month, now it’s $4.1/tb/month.
Still cheaper than backblaze’s $6 which seems the only other option everyone suggests, so it’ll have to do for the moment.

@Showroom7561@lemmy.ca
link
fedilink
English
11M

My idrive plan went from just over $100 to $250.

I created another account, paid for another year at a promotional price, and then deleted my old account.

I will eventually have to come up with a more sustainable cloud/off site backup now that i need more than just a few TB.

Since this is really my “last resort” backup, I’m not too concerned, as anything that would require me to actually restore from this backup set would likely be catastrophic in a life-ending way.

@paperd@lemmy.zip
link
fedilink
English
111M

I use restic to backblaze b2.

Yep, Duplicacy to Backblaze B2 for me

@nnullzz@lemmy.world
link
fedilink
English
31M

Same

@brewery@lemmy.world
link
fedilink
English
51M

After some research on here and reddit about 6 months so, I settled on Borgbase and its been pretty good. I also manually save occasionally to proton drive but you’re right to give up on that as a solution!

The hardest part was choosing the backup method and properly setting up Borg or restic on my machine properly, especially with docker and databases. I have ended up with adding db backup images to each container with an important db, saving to a specific folder. Then that and all the files are backed up by restic to an attached external drive at well as borgbase. This happens at a specific time in the morning and found a restic action to stop all docker containers first, back them up, then spin them back up. I am find the guides that I used if it’s helpful to you.

I also checked my backups a few times and found a few small problems I had to fix. I got the message from order users several times that your backups are useless unless you regularly test them.

Boomer Humor Doomergod
link
fedilink
English
61M

I’m still looking for a case that can hold a Pi and a 3.5” drive that I can set up at someone else’s house.

Uninvited Guest
link
fedilink
English
21M

I’m getting this set up at my parents’. Just gotta remind them not to touch the box!

@AtariDump@lemmy.world
link
fedilink
English
61M

Tape/glue the Pi in the case to the HDD.

Done.

pmk
link
fedilink
English
41M

I’ve thought about gutting an old toaster, like for toasting bread, to house a raspberry pi and instead of slices of bread you can stick harddrives into the slots. Two bays. The prime motivation is just to be able to say that I can run Linux on a toaster. Next step would be running Linux on a dead badger I guess.

@mirisgaiss@lemmy.world
link
fedilink
English
31M

I would hope someone has made a toaster drive dock by now, missed opportunity

@Wiz@midwest.social
link
fedilink
English
21M

Yes but can you run Doom on a dead badger

SayCyberOnceMore
link
fedilink
English
11M

For inspiration, take a look at the Nextcloud Devices - just for the hardware ideas.

I’m still running a Nextcloud Box (with the original Western Digital drive) and it’s fine for my needs.

I can recommend Restic with Wasabi S3 as cloud storage backend.

Create a post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

  • 1 user online
  • 238 users / day
  • 644 users / week
  • 1.46K users / month
  • 3.92K users / 6 months
  • 1 subscriber
  • 4.18K Posts
  • 86.9K Comments
  • Modlog