This commit is contained in:
Joshua Boniface 2016-09-28 13:30:46 -04:00
parent d6e6cc916d
commit 03db664a84
2 changed files with 4 additions and 3 deletions

View File

@ -12,7 +12,7 @@ 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).
* 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.
The adage is simple: "RAID replicates **everything**, even the stuff you don't want, like the deletion of that file you needed."

View File

@ -9,5 +9,6 @@ Now that you're in the know, get to making and checking a backup of your data, b
More information can be found on the following pages:
* http://www.smallnetbuilder.com/nas/nas-features/31745-data-recovery-tales-raid-is-not-backup
* http://blog.open-e.com/why-raid-is-not-a-backup/
* http://serverfault.com/questions/2888/why-is-raid-not-a-backup