MentalEdge comments on How do you effectively backup your high capacity (20+ TB) local NAS?

How do you effectively backup your high capacity (20+ TB) local NAS? (lemmy.world)

submitted 8 months ago by NekoKoneko@lemmy.world to c/selfhosted@lemmy.world

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

[–] MentalEdge@sopuli.xyz 1 point 8 months ago* (last edited 8 months ago) (8 children)

With what?

That self hosting admins on lemmy probably care about their backups not being accessible to third parties?

I don't think you can claim that they wouldn't.

You can claim that YOU don't mind. But that's a sample size of one. And I'm not denying there are people who don't care.

I just don't think they're the type to be self-hosting in the first place.

And that still doesn't answer why the fuck you set out on this series of "well achuallys"?

It seems to me, you're still looking for something to correct me on.

permalink

fedilink

source

parent

hideshow 8 child comments

[+] FreedomAdvocate@lemmy.net.au 0 points 8 months ago* (7 children)

[deleted]

permalink

fedilink

source

parent

hideshow 7 child comments

[–] MentalEdge@sopuli.xyz 1 point 8 months ago* (6 children)

...

Sure they can. How else do they enable providing access to the content without the user password?

The data is secured against unauthorized access, but unlike zero-knowledge setups where the chain of custody is fully within user control, the user is not the only one authorized. And even if you are supposed to be, you cannot ensure that you actually are.

OF-FUCKING-COURSE the physical drives, and network traffic are encrypted. That's how you prevent unauthorized physical access or sniffing of data in-flight. That's nothing special.

But encryption is not some kind of magic thing that just automatically means anyone who shouldn't have access to the data, doesn't.

For that to actually be the case, you need solid opsec and known chain of custody. Ways of doing things that means the data stays encrypted end-to-end.

The personal backup plan doesn't have that.

permalink

fedilink

source

parent

hideshow 6 child comments

[+] FreedomAdvocate@lemmy.net.au 0 points 8 months ago* (last edited 8 months ago) (5 children)

[deleted]

permalink

fedilink

source

parent

hideshow 5 child comments

[–] MentalEdge@sopuli.xyz 1 point 8 months ago* (4 children)

...

Explain to me how they couldn't. Without simply stating "it's encrypted".

On the B2 plan you can use open source solutions like Kopia, and literally look at the code, to KNOW that data is encrypted on your system with keys only you have, before Backblaze ever sees it.

Explain to me, how the personal plan using their closed source application achieves the same.

Linking to a page where they say "it's secure" is not sufficient. Elaborate. In detail. To at least an equal extent I already have.

permalink

fedilink

source

parent

hideshow 4 child comments