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

Changed lots of text and wording

Browse Source
This commit is contained in:
Joshua Boniface
2017-02-22 01:03:24 -05:00
parent 9f5fc95070
commit 1e1faa01ea
4 changed files with 16 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
content/3.md
View File

@ -5,7 +5,6 @@ weight = 2
type = "post"
+++
There exists a number of file and storage systems with some advanced, RAID-like features. These include ZFS, btrfs, and Ceph. On the surface, these might give you the illuson of protection, but don't be deceived. You can still trash your whole system (or cluster, for Ceph). You can still `rm` files or other destructive commands. A fire can still destroy your whole rack.
Like RAID, ADVANCED FILESYSTEMS STILL AREN'T BACKUPS!
There exists a number of file and storage systems with some advanced, RAID-like features. These include ZFS, btrfs, and Ceph. On the surface, these might give you the illuson of protection, but don't be deceived. You can still trash your whole system (or cluster, for Ceph). You can still `rm` files or run other destructive commands accidentally. A fire can still destroy your whole rack. A malicious user could overwrite your database. Even the smartest most advanced storage engine is still susceptable to at least one, and almost always several, fatal failure modes.
Like RAID, ADVANCED FILESYSTEMS STILL AREN'T BACKUPS! Just make another copy of the data, okay!?