this post was submitted on 10 Jan 2025
118 points (96.1% liked)

Selfhosted

41115 readers
528 users here now

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!

founded 2 years ago
MODERATORS
 

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?

(page 2) 36 comments
sorted by: hot top controversial new old
[–] xylogx@lemmy.world 1 points 5 days ago

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

[–] nickiam2@aussie.zone 3 points 6 days ago

I use restic with a wrapper script to automate it on all of my machines. The backend storage can be anything that speaks S3, so B2, or iDrive would both work. I currently use Storj for my backend. It's globally distributed storage, so no single point of failure geographically and it's cheap. Backblaze is also a great company, but I've grown a little skeptical since they went public.

[–] bartvbl@lemmy.world 2 points 6 days ago

I'm a long time user of jottacloud. It's not really meant for 10TB+, but works great for what I need it to do.

[–] dawa@programming.dev 2 points 6 days ago

I'm on Pcloud, server with rsync+rclone to move files from file system to cloud and use it as a unified file system.

The lifetime storage offer from pcloud has been worth it for me and I even upgraded it from 2 to 12 TB

[–] bier@lemmy.blahaj.zone 2 points 6 days ago

If you're talking multiple Terrabytes and are located in the EU you might want to consider AWS Glacier I have like 6Tb on there and pay sub 20€ p.m. If you're in the EU you can request one free migration download by contacting the support. Otherwise you'll pay thousands.

[–] flop_leash_973@lemmy.world 1 points 6 days ago

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

[–] paperd@lemmy.zip 11 points 1 week ago (1 children)

I use restic to backblaze b2.

[–] plasticcheese@lemmy.one 4 points 1 week ago (1 children)

Yep, Duplicacy to Backblaze B2 for me

[–] kevincox@lemmy.ml 8 points 1 week ago (1 children)

I've been using Restic to Backblaze B2.

I don't really trust B2 that much (I think it is mostly a single-DC kind of storage) but it is reasonably priced and easy to use. Plus as long as their failures aren't correlated with mine it should be fine.

[–] sxan@midwest.social 1 points 1 week ago (1 children)

I quadrupal vote for this combination.

You could trust B2 more; maybe dig into their structure. They're solid, and not only that they provide an awesome service with their yearly HD failure rate evaluations, in which they describe the structure of their data centers.

I'm terms of NPS, I'm on their side. Unless something comes out and shady business practices, I'm brand loyal to B2. Been with then for years, and love the service, pricing, and company.

[–] kevincox@lemmy.ml 2 points 1 week ago* (last edited 6 days ago) (2 children)

I think it depends on your needs. IIUC their storage is "single location". Like a very significant natural disaster could take it offline or maybe even lose it. Something like S3 or Google Cloud Storage (depending on which durability you select) is multi-location (as in significantly distinct geographical regions). So still very likely that you will never lose any data, but in the extreme cases potentially you could.

If I was storing my only copy of something it would matter a lot more (although even then you are best to store with multiple providers for social reasons, not just technical) but for a backup it is fine.

[–] sxan@midwest.social 2 points 6 days ago (2 children)

I think I see what you're saying.

B2 has multiple data centers around the world - at least 3 in the US and 1 in EU, that I know of. If you want your data replicated, you have to create buckets in multiple locations and connect them for replication, which they'll do for you (the replication).

If you're saying that they don't automatically store multiple copies of your data in multiple locations for you, for free, you're right. But they do have multiple data centers located around the world, and you can create multiple buckets and configure them for automatic replication so you have redundancy. You have to pay for the storage at each replicated location, though. If you want a bucket in Sacramento, it'll cost you those pennies. If you want it replicated to Rest on, you'll pay double the pennies. If you want it also replicated to Amsterdam, triple the pennies.

I don't think it's fair to say that they're single location that could have a natural disaster and you therefore lose your storage. It's only like that if you set it up that way, and it's pretty trivial to set up global replication - it just costs more.

load more comments (2 replies)
[–] pcouy@lemmy.pierre-couy.fr 2 points 6 days ago

Enabling multi DC redundancy is really easy though. The other providers you mentioned may have it by default, but they're also a lot more expensive.

I love that they let me pick my own redundancy strategy, without forcing me to pay for theirs

[–] schizo@forum.uncomfortable.business 6 points 1 week ago (2 children)

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.

[–] pe1uca@lemmy.pe1uca.dev 1 points 6 days ago

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 1 points 6 days ago

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.

[–] Semi_Hemi_Demigod@lemmy.world 6 points 1 week ago (8 children)

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.

[–] Wxfisch@lemmy.world 6 points 1 week ago

I use Backblaze B2 through my Synology NAS to offsite my important data. Most things though I just backup locally and accept the risk of needing to rebuild certain things (like most of my movie/TV media files since I can just re-rip my physical media, and the storage costs are not worth the couple of days of time in that unlikely case).

I really think this is key when thinking about your backup strategy that is specific to self hosting compared to enterprise operations. The costs come out of our pockets with no revenue to back it up. Managing backups for self hosting IMO is just as much about understanding your risk appetite and then choosing a strategy to match that. For example I keep just single copy in B2, since the failure mode I’m looking to protect against is catastrophic failure of my NAS which holds my main backups and media. I then use Proton Drive and OneDrive to backup secrets for my 2FA setups and encryption for my B2 bucket. This isn’t how I would do it at work (we have a fair more robust, but much more expensive setup). But my costs for B2 are around $15/mo which I am fine with. When I tried keeping multiple copies it had grown to over $50/mo before I cared enough to really rethink things (the cost of the hobby I told myself).

[–] brewery@lemmy.world 5 points 1 week ago

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.

[–] grimer@lemmy.world 4 points 1 week ago

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

[–] 2xsaiko@discuss.tchncs.de 3 points 1 week ago

I use borgbackup, with daily backup to borgbase.

At some point I want to set up a distributed file system between multiple locations as both a backup target and also a network share with automatic snapshots or some other undelete mechanism, but I still need to get the hardware for that and the current setup works well

[–] undefined@lemmy.hogru.ch 3 points 1 week ago (1 children)

I use Storj, it’s been my favorite for years.

[–] jagged_circle@feddit.nl 2 points 6 days ago (1 children)

Do you mine? Always sounded like the best option if you dont have a friend in another georegion to replicate-to

load more comments (1 replies)

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

[–] makingStuffForFun@lemmy.ml 1 points 1 week ago

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

[–] ptz@dubvee.org 1 points 1 week ago* (last edited 1 week ago)

This is actually one of my New Year's resolutions lol. Right now, my backups are local and my offsites are a hodgepodge of cloud services (basically holding encrypted container blobs of my stuff). Not ideal.

I'm looking at signing up for rsync.net since a lot of my backups are done via rsync anyway. Plan is to keep my local backups as-is and rsync them to rsync.net.

load more comments
view more: ‹ prev next ›