Added real content

This commit is contained in:
Joshua Boniface 2016-09-28 12:17:03 -04:00
parent 514cf19af7
commit a741851211
4 changed files with 43 additions and 1 deletions

20
content/2.md Normal file
View File

@ -0,0 +1,20 @@
+++
title = "So why do I need a backup?"
description = "Because RAID protects you against one and only one specific thing: disk failures."
weight = 2
type = "post"
+++
Having a number of disks in RAID may _seem_ like a backup, especially if you're using a mirror mode. But this is *wrong*!
RAID protects you against one and only one thing: a disk failure. It does not protect you against any of the following things:
1. Multiple disk failures beyond the RAID level chosen (e.g. both disks in a mirror, or 3 disks in a RAID-6).
2. Failure of the RAID controller itself (especially when using hardware RAID), the computer itself, or the environment (a flood, or fire, perhaps).
3. Data corruption on-disk (except for ZFS, and especially for BTRFS) from cosmic rays, or minor hardware or firmware failures.
4. 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).
5. 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."
For these reasons and more, RAID IS NOT A BACKUP!

14
content/3.md Normal file
View File

@ -0,0 +1,14 @@
+++
title = "So how do I back up?"
description = "Backups are a contentions and complicated subject, but these simple rules should help guide you."
weight = 3
type = "post"
+++
1. Always back up in _some way_. While a copy of the data on the same array won't protect you against all problems, it will protect you against some.
2. A _backup on the same server_ is susceptable to the _same failures as the original data_ set (hardware failure, natural disasters, and the like).
3. A good rule of thumb is _three copies_ (the RAID is only one copy for this purpose): the _original_, one _onsite copy_, and one _offsite copy_. Store the offsite copy in the cloud, or at a friend's house.
4. _Make backups regularly_, at least once a week; the day you need a backup is the day you realize you hadn't run it in 6 months and what you need isn't backed up.
5. _Test backups regularly_, at least once a month; _a backup is worthless if you can't restore from it_. Just because you have a backup doesn't mean you're protected; always test them.
There are dozens of backup utilities out there; I'm not going to prosthelytize for any one of them, but I personally use [BackupPC](http://backuppc.sourceforge.net/) for my server and workstation backups.

8
content/4.md Normal file
View File

@ -0,0 +1,8 @@
+++
title = "I've learned something!"
description = "Great!"
weight = 4
type = "post"
+++
Now that you're in the know, get to making and checking a backup of your data, before you lose it!

View File

@ -1,7 +1,7 @@
+++ +++
title = "About us" title = "About us"
description = "raidisnotabackup.com is a PSA created by Joshua Boniface of Boniface Labs" description = "raidisnotabackup.com is a PSA created by Joshua Boniface of Boniface Labs"
weight = 1 weight = 99
type = "post" type = "post"
class="post last" class="post last"
+++ +++