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.)

  • Daniel Quinn@lemmy.caEnglish
    5·
    23 hours ago

    Honestly, I’d buy 6 external 20tb drives and make 2 copies of your data on it (3 drives each) and then leave them somewhere-safe-but-not-at-home. If you have friends or family able to store them, that’d do, but also a safety deposit box is good.

    If you want to make frequent updates to your backups, you could patch them into a Raspberry Pi and put it on Tailscale, then just rsync changes every regularly. Of course means that wherever youre storing the backup needs room for such a setup.

    I often wonder why there isn’t a sort of collective backup sharing thing going on amongst self hosters. A sort of “I’ll host your backups if you host mine” sort of thing. Better than paying a cloud provider at any rate.

    • Joelk111@lemmy.worldEnglish
      4·
      21 hours ago

      That NAS software company Linus (of Linus Tech Tips) funded has a feature for this planned I think.

      An open-source standalone implementation would be dope as hell. Sure, it’d mean you’d need to double your NAS capacity (as you’d have to provide enough storage as you use), but that’s way easier than building a second NAS and storing/maintaining it somewhere else or constantly paying for and managing a cloud backup.

      • WhyJiffie@sh.itjust.worksEnglish
        1·
        4 hours ago

        such a system would need a strict time limit for restoration after the catastrophe. Otherwise leeching would be too easy.

        • Joelk111@lemmy.worldEnglish
          1·
          3 hours ago

          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.worksEnglish
            1·
            2 hours 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.