joshuaboniface
/
raidisnotabackup
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Tweaked failures into 4 bullet points as I was repeating myself needlessly

This commit is contained in:
Joshua Boniface 2016-09-28 18:54:53 -04:00
parent 6b38dea946
commit 8f13a880bf
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
content/2.md
View File

@ -11,10 +11,11 @@ RAID protects you against one and only one thing: a disk failure. It does **not*
* Multiple disk failures beyond the RAID level chosen (e.g. both disks in a mirror, or 3 disks in a RAID-6).
* Failure of the RAID controller itself (especially when using hardware RAID), the computer itself, or the environment (a flood, or fire, perhaps).
* Data corruption on-disk (except for ZFS, and especially for BTRFS) from cosmic rays, or minor hardware or firmware failures.
* File corruption from bad writes or bit rot (except for ZFS), including whole-volume corruption from administrative mistakes (e.g. `mkfs` on an existing filesystem).
* Malicious or accidental deletion or modification of data by yourself or another party, including viruses.
* Data corruption on-disk from filesystem bugs, cosmic rays, or minor hardware or firmware failures.
* Malicious or accidental deletion or modification of files by yourself or another party, including viruses, bad application writes, or administrative mistakes (e.g. `mkfs` on an existing filesystem).
The adage is simple: "RAID replicates **everything**, even the stuff you don't want, like the deletion of that file you needed."
For these reasons and more, RAID IS NOT A BACKUP!
ZFS is an interesting case: while it does protect from corruption, it is still susceptable to the other failure modes and hence is still NOT A BACKUP!