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

12
content/4.md
View File

@ -5,12 +5,12 @@ weight = 3
type = "post"
+++
* 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.
* Always back up in _some way_. While a copy of the data on the same array won't protect you against all, or even very many, failure modes, it will protect you against some, and those are usually the most common.
* A _backup on the same server_ is susceptable to the _same failures as the original data_ set (hardware failure, natural disasters, and the like).
* 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.
* _Make backups regularly_, at least once a week, and automate if possible; 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.
* _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.
* A good rule of thumb is _three copies_: the _original_ (RAID or otherwise); one _onsite copy_ on a different, preferrably offline, medium; and one _offsite copy_. Store the offsite copy in the cloud, a data vault, or at a friend's house, just keep it somewhere else.
* _Make backups regularly_, at least once a week, preferrably more, and automate it! Forgetting to back something up and then needing just that backup is never fun, and the more frequently you back up, especially incrementally, the better your recovery resolution.
* _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 and fix any problems. If you never test your backup, you will almost certainly find it doesn't work, right when you need it.
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.
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/) and good ol' fashoned `rsync` for my server and workstation backups.
Do you need to back up everything? Of course not. That's up to you to decide. Some data is replaceable, some isn't. If it isn't, back it up!
Only you can determine what you need to back up, but if you can't replace some data, you should definitely back it up - Murphy's Law applies here as much as anywhere.