this post was submitted on 15 Sep 2023
455 points (96.1% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
53969 readers
315 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
💰 Please help cover server costs.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
if your that passionate about NASs, may I ask how does one negate data loss if a lighting were to strike? or fire?
I get Raid an all that, but I don't care how many times my data got burnt if it ever will.
Same with lightning, lightning rods are a thing, so maybe that? Idk what would be dmged if an entire lightning passes thru your house in a wire or not, like electromagnetic fields are a thing.
Off-site backup is the proper answer to your question. All this really depends on your own tolerance or comfort with the possibility of losing data. The rule of thumb is that there should be at least three different copies of your data, each in a different physical location. For each of them, there should be redundancy of some kind implemented to guard against hardware failure. Redundancy is typically achieved by using mirrored drives or by using RAID of some kind. Also, if you'd like to know, using RAID in which you can only lose one disk in the array is not typically considered a sufficient level of protection because of the possibility of a cascading drive failure during replacement of a failed disk. It should be at least two.
"cascading drive failure" the what now? How do drives die in a domino effect?
three locations seem a bit much, but I totally understand it. Safe storage is tedious, huh.
The calculations necessary to rebuild a failed drive from parity data stored on the other drives means that for the duration of the time that the array is being rebuilt (aka "resilvered"), you'll have high activity on the other drives. So during that time there's an increased chance that a drive that was already on the brink of failure is pushed over the edge. If that happens, your data is gone. Like I said it depends on your risk tolerance. You may not feel like it's worth it in your situation. I personally only run a raidz1. I accept the risk that entails, just as people who use raidz2 accept the increased risk that entails over raidz3. There's no limit to the amount of redundancy you can add. The level of redundancy that's needed is a decision that only you/your organization can make.
well, I never tought of data loss prevention in this way. Thanks.