this post was submitted on 26 Feb 2026
161 points (98.8% liked)

Selfhosted

59999 readers
663 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.

  3. Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.

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

  5. Submission headline should match the article title.

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
161
How do you effectively backup your high capacity (20+ TB) local NAS? (lemmy.world)
submitted 3 months ago* (last edited 3 months ago) by NekoKoneko@lemmy.world to c/selfhosted@lemmy.world
120 comments fedilink hide all child comments
 

I have a 56 TB local Unraid NAS that is parity protected against single drive failure, and while I think a single drive failing and being parity recovered covers data loss 95% of the time, I'm always concerned about two drives failing or a site-/system-wide disaster that takes out the whole NAS.

For other larger local hosters who are smarter and more prepared, what do you do? Do you sync it off site? How do you deal with cost and bandwidth needs if so? What other backup strategies do you use?

(Sorry if this standard scenario has been discussed - searching didn't turn up anything.)

you are viewing a single comment's thread
view the rest of the comments
[โ€“] Joelk111@lemmy.world 1 points 3 months ago* (last edited 3 months ago) (1 children)

That's an incredibly good point. Bad actors are the worst. Some ideas:

  • Maybe you'd need to contribute your storage capacity +10% (or more), to account for your and other's downtime during disasters.
  • A time limit after disasters would be necessary. It's difficult to think of a proper time limit though, as even a month might not be enough time if your entire house burns down.
  • Maybe a payment system could be set up to where, if your server doesn't ping for a week, your credit card is automatically charged (after pinging you with many emails). Sure, that'd suck, but it'd be better than loosing your data, and cheaper overall than paying for cloud backups. I'm not sure where that money would go. Maybe distributed to those who didn't experience a disaster, or maybe to the software project, though that would mean people are profiting from a disaster. Maybe it could go to a charity of your choice or something.

Definitely a difficult problem to solve. I'm sure people smarter than me have ideas beyond mine.

[โ€“] WhyJiffie@sh.itjust.works 1 points 3 months ago

A time limit after disasters would be necessary. It's difficult to think of a proper time limit though, as even a month might not be enough time if your entire house burns down.

and also accounting for low bandwidth connections.. whats more, some shitty providers even have monthly data caps

Maybe a payment system could be set up to where, if your server doesn't ping for a week, your credit card is automatically charged (after pinging you with many emails).

yeah, that would be almost a necessary feature. being able to hold on to the backup when you really can't restore.