• 0 Posts
  • 5 Comments
Joined 3 years ago
cake
Cake day: November 23rd, 2023

help-circle
  • Yes, valid points that I didn’t really want to muddy the discussion with. In my experience, most people hear the Redundant in RAID and think that’s sufficient and that their data is safe. Maybe poor choice of words on my part, but that’s what I meant re: “data safety.”

    You’re fully correct that a proper RAID setup can provide additional layers of availability atop a robust backup process, but I’d wager most of the people who are interested in that extra layer are already aware of the limitations of RAID.

    I do run RAIDZ1 on my franken-nas due to limited drive sizes on that machine, the goal being to maximize usable space while providing a sufficient amount of time to address a drive failure. If drive prices ever become reasonable again, I’ll likely rebuild the system with 6-8 drives in a RAIDZ2 configuration just for a little more peace of mind, but as long as my off-site backups are running, I sleep at night just fine.




  • RAID is not a backup.

    RAID is not for data safety.

    RAID is for:

    1. Ensuring availability of data in the face of hardware failure. That means your files don’t disappear when a drive dies and you have some time to swap out for functional hardware and restore redundancy.
    2. Presenting multiple drives as one larger unit. This is what striping does, and to a lesser extent the parity-mode levels.
    3. Improving performance (sometimes). A RAID mirror is generally much faster to read from than any individual drive because reads can be interleaved across drive members. A stripe can be much faster because writes are distributed across drive members. This is less of a bonus today with solid state/nvme drives, but it’s still applicable to spinning rust.

    If your concern is protecting your data, set up a 3-2-1 backup strategy.