• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How to protect your data guide

taltamir

Lifer
A common misconceptions is that if you have a backup or redundancy scheme of any sort your data is safe.
Backup and redundancy are different things, and neither protects against everything.
To properly protect your data you must list all the possible ways in which data can be lost, and then address each and every one of them (or the ones you think are pertinent & are within your budget)

Here are a list of common disasters and the ways to protect against them:
1. Fire - offsite backup, DO NOT use a firesafe as they are meant for paper documents (350 internal temp max... which will ruin your data, but not your paper documents)
2. Flood - offsite backup, waterproof media?
3. Swatting: Swatting comes from the term SWAT, SWATting is when someone places an anonymous call to the authorities, and lies, claiming that you traffic in illegal materials such as illegal gun trading or CP.
Even if you are completely innocent, your computers and drives will be held as evidence for years afterwards. Offsite backup is the only protection against this (as it will surely cause your business to fail otherwise). Note that this isn't advice to circumvent the law, if you are guilty they will likely go after your offsite backups as well. But if you are innocent this can save you. (I have read stories of people who run small software business from home having that happen to them, there was never any evidence found of any wrongdoing on their part, but the FBI kept their computers and data)
4. bit rot - use checksumming. The only HDD/SSD Checksumming filesystems currently are the googleFS (trade secret of google), ZFS (publically available), and BTRFS (almost done).
For optical media you can use http://dvdisaster.net/en/index.html
For individual files or folders containing important data you can use parchive recovery records http://en.wikipedia.org/wiki/Parchive
5. Cosmic rays bit flipping - see bit rot for solutions. add ECC ram and using robust software that can "verify written data" properly.
6. Drive failure - use redundancy (raid 1,5,6, 10/1+0/01/0+1 etc); or backup. Or if the data is important enough use both and even multiple backups. Note that neither RAID 0 nor JBOD are redundant and will not help.
7. Controller failure - use a storage scheme that allows you to replace the controller or does not require one. Any motherboard raid other then RAID1 is likely to result in dataloss in case of mobo controller failure. RAID1 should be fully portable though (but worth verifying before trusting with your data) and high end independent controllers can be swapped out with identical models.
8. A controller failure where your replaceable controller can no longer be found on the market - Upgrade your storage to ensure you are using controllers still available on the market or switch to a system that allows you to switch to other "controllers" (aka, OS based software raid like in linux, solaris, windows server, or open nas; or use controllers from a company that historically makes newer versions support older controller made arrays).
9. Theft - offsite backup OR/AND worthless media backups (DVD-R). they will take your fileserver, iphone, external drive, and flash drives. but unlikely to take your burned DVD-R collection.
10. Virus - NOD32 antivirus 😛. Joking aside. For a simple virus that just deletes all data have an external backup that you turn off / unplug except for when you manually connect it / turn it on to perform a backup. But those viruses are rare. To avoid silent corruption of data you should look at multiple rolling backups off of write once media (aka optical media)
11. Silent data corruption on HDD (due to a bad drive or PSU) - use a checksumming filesystem (only ZFS at the moment) AND redundancy (RAID1, 5, 6, etc). using only RAID will leave you with corrupt data as it has no way of knowing which copy of readable data is corrupt and which is correct. Using only checksumming filesystem will let you know it is corrupt, but without a non corrupt copy to recover from.
12. Sabotage - offsite rolling backup; internal corporate security.
13. Lightening strike - backup to optical media (CD/DVD/Bluray), or backup to an external drive that you physically unplug from both the power AND the PC when not in use AND doesn't sit on a metal surface. If it is sitting on the PC case, or if it is plugged into the PC via a USB cord, that is enough to fry it!
Also, use surge protectors on your PC / Server / External drive (not as safe as unplugging it, but it might save your data and hardware)



Also, please note that whatever method of data protection you use, it is CRITICAL that you:
1. Check to see that the backups are happennig as expected. (is it really backing up daily? or did a careless employee disable it 9 months ago and nobody noticed and turned it on since? did someone switch off the external HDD that is the target of the backup software? both cases are real examples I have seen)
2. Check that the backups are readable (is the CD you burned corrupt? corrupt beyond the ability of DVDisaster to repair?).
3. Check that all needed files are being backed up (for example, your firefox bookmarks cannot be backed up while the program is running. If you leave it on all the time then it will never get backed up)



Terms explained:
Rolling Backup: Rolling backup is what you have multiple backups from different time periods. For example, you have a complete backup of all your files from 1 week ago, 1 month ago, 2 months ago, 3 months ago, and 1 year ago.
Parchive: http://en.wikipedia.org/wiki/Parchive
ZFS: http://en.wikipedia.org/wiki/ZFS
 
Last edited:
9. Theft - offsite backup OR/AND worthless media backups (DVD-R).

Use raid 1 with a removable hard drive caddy so you could stash that extra drive somewhere if you are gone. I don't know if this would work but its crossed my mind as something I'd like to try.

Also that is assuming you want your machine on while you are gone. You could also just shut it down and remove the main drive if you just wanted protection from thieves.

1. Fire - offsite backup, maybe a firesafe with backups (for small fires)

Use mozy for your most important irreplaceable files. They give you up to 2gb for free and "unlimited" backups are like $5 bucks a month. http://mozy.com/
I've been using it for about 6-8 months and I love it. Its helped me out in the event that I needed a file and I could do a single file restore from a different computer. Also you could use http://www.carbonite.com/ which is a paid service. I've heard good things about both.

Those are the main things that come to mind for me. Also with the advent of huge (8 gb and on up) flash drives you could easily back up certain files and encrypt them and take it with you in the case of theft etc.
 
NEVER rely on a firesafe to protect data! These safes are designed to protect PAPER documents. 1700°F outside for one hour - 350°F inside. Put a hard drive, DVD-R, DLT, etc. in your oven preheated to 350° for an hour and let me know the results after it has cooled down. 😉

Remote backups is the only safe way. A USB drive carried offsite is also effective providing you KNOW the backups are good and a RESPONSIBLE person is assigned to take it offsite and is handling it properly.
 
thank you rubycon, I will add it.

krwilsonn, it is a neat a idea, I personally wouldn't try HIDING expensive items and hope the thieves don't find it though, that is kinda what they do...
Thanks for the link, that is exactly the kind of "offsite backup" the average joe needs. (since his "site" is home)
 
Thanks QuixoticOne.

I made some changes:

11. Drive erroring (due to a bad drive or PSU) but still writing - use a checksumming filesystem (only ZFS at the moment) AND redundancy (RAID1, 5, 6, etc). Usingly only RAID will leave you with corrupt data as it has no way of knowing which copy of readable data is corrupt and which is correct. Using only checksumming filesystem will let you know it is corrupt, but without a non corrupt copy to recover from.
13. Lightening strike - backup to media, or backup to an external enclosure that you UNPLUG from both the power AND the PC when not in use. Also, use surge protectors on your PC / Server (not as safe as unplugging it, but it MIGHT save your data and hardware)
 
Although it doesn't exactly fit into your format, it wouldn't hurt to mention that, no matter what backup solution is used, it's critical to do ongoing TESTS of the backups to ensure that:
a) The backups are happennig as expected
b) The backups are readable
c) All needed files are being backed up

I can't count how many times I've had folks tell me they have backups, only to discover that the backups are not completing or the media is unreadable or important files are missing from the backup set because they are in an unexpected location on the original drive.
 
Speaking of corrupt / partly unreadable backups and silent checksum errors...

ECC FTW! If you store ECC data about / alongside your data whether those data are backup files, CDs/DVDs, individual files, whatever, you will be able to detect and REPAIR corruption to them. I could, for instance, copy a set of files over 4 DVDs and spread ECC data around among the DVDs also. Then I can throw one DVD away or burn it or scratch it whatever until it is gone and yet be able to recover ALL my data from the remaining 3 DVDs as an example. The same can be done for tape, hard disc, floppy, whatever.


* http://en.wikipedia.org/wiki/Dvdisaster
* http://www.dvdisaster.com/

* http://en.wikipedia.org/wiki/Par2

And failing ECC, you should at least hash so you'll *know* you're screwed instead of just suspecting it systematically:

Microsoft's free FCIV hasher / checker:
http://support.microsoft.com/kb/841290
http://www.microsoft.com/downl...1686c08&DisplayLang=en

Sha1sum for broken/lacking OSs (windows):
http://lists.gnupg.org/piperma...nce/2004q4/000184.html
ftp://ftp.gnupg.org/gcrypt/binary/sha1sum.exe (20k)
ftp://ftp.gnupg.org/gcrypt/binary/sha1sum.exe.sig
ftp://ftp.gnupg.org/gcrypt/binary/sha1sum.c (9k)
ftp://ftp.gnupg.org/gcrypt/binary/sha1sum.c.sig

MD5sum for windows:
http://etree.org/md5com.html

Of course to protect against accidental or intentional file corruptions / alterations you can use IDS (intrusion detection system) tools to check the integrity of your files (among other things):
http://en.wikipedia.org/wiki/H...usion_detection_system
http://en.wikipedia.org/wiki/Intrusion_detection_system
http://en.wikipedia.org/wiki/OSSEC
http://la-samhna.de/samhain/
http://osiris.shmoo.com/
http://sourceforge.net/projects/aide


 
Doing hash based file integrity checking manually under UNIX is simplicity itself --
one can just do something like --

find / -type f -print0 | xargs -0 sha1sum > /ALL_MY_FILES_SHA1_HASHES.txt

then any time to verify if anything has changed or become lost / corrupt:
sha1sum --check < /ALL_MY_FILES_SHA1_HASHES.txt
voila.

 
Originally posted by: QuixoticOne
Speaking of corrupt / partly unreadable backups and silent checksum errors...

ECC FTW! If you store ECC data about / alongside your data whether those data are backup files, CDs/DVDs, individual files, whatever, you will be able to detect and REPAIR corruption to them. I could, for instance, copy a set of files over 4 DVDs and spread ECC data around among the DVDs also. Then I can throw one DVD away or burn it or scratch it whatever until it is gone and yet be able to recover ALL my data from the remaining 3 DVDs as an example. The same can be done for tape, hard disc, floppy, whatever.

Amen! I use Ghost 2003 (bootable DOS floppy, I made a bootable USB drive to do it too), I image my partitions to a different partion, split the files to 690MB, generate ECC files with QuickPAR (PAR2), and then burn the files to DVD using Japan-made discs, using verify mode for the writing, spreading the ECC around on the different discs.

I then sometimes boot the system using Ghost and do a test on the backups. I don't do a full test-restore.

 
you know what, i think this should be stickied. Every person visiting the memory and storage forum should read and understand that raid =! back... and that neither by itself will protect you against everything
 
ok, so i was thinking... a combination of redundant storage (say, raid1) and online backups (doesn't amazon or google offer such a service now?)... Can anyone think of a SINGLE situation that will cause dataloss in such a scenario? (your house AND the online server burning down the same day doesn't count)
 
you need to also protect your data. AES-256 with a long password. use restricted rights to prevent a hacker from being able to delete/tamper with backups. that might include physical unplug rotation of backup disks.
 
So, I was thinking this needs resurrecting...
I was told this needs some cleanup before it would be good as a sticky, but I had no idea what they are talking about and was rather busy at the time and just let it be as is.
Can someone who is better than me at making thing clear to the less technical put forth suggestions on how to make this more accessible and thus sticky worthy?
 
So, I was thinking this needs resurrecting...
I was told this needs some cleanup before it would be good as a sticky, but I had no idea what they are talking about and was rather busy at the time and just let it be as is.
Can someone who is better than me at making thing clear to the less technical put forth suggestions on how to make this more accessible and thus sticky worthy?

I think maybe just a bit of formatting would make this sticky worthy.
I'll try it some time later this week. I am a newbie at data protection, but i think i can handle improving the formatting.
 
For most people who don't own a business, Mozy/Carbonite with a local USB drive will do. If you're paranoid about data theft, encrypt the local backup drive using TrueCrypt.

The local backups are mainly for your RTO (Recovery Time Objective) so you don't spend a week recovering your data online.
 
Last edited:
For most people who don't own a business, Mozy/Carbonite with a local USB drive will do. If you're paranoid about data theft, encrypt the local backup drive using TrueCrypt.

I looked these up and they limit you to 1GB... Carbonite specifically sells "unlimited storage", with small print saying "abuse of the unlimited storage will result in termination of your account" and "abuse is over 1.something GB"
Services that allow you as much storage as you want, metered, are ridiculously expensive... as in 50 cents per month per GB expensive.
 
I got tired of not having a serious online backup option. I decided I will create one myself and as part of the preliminary work I researched the market heavily... and managed to find one that does what I intended.
Offer a reasonably priced bulk backup service that does not inflate prices by giving you unnecessary stuff like hosting bandwidth or processing power. So I will not be creating this service after all.

http://www.backblaze.com
Currently I have 2TB on their servers. And to show my sincerity, notice that I am NOT linking this via their commission deal.
 
I got tired of not having a serious online backup option. I decided I will create one myself and as part of the preliminary work I researched the market heavily... and managed to find one that does what I intended.
Offer a reasonably priced bulk backup service that does not inflate prices by giving you unnecessary stuff like hosting bandwidth or processing power. So I will not be creating this service after all.

http://www.backblaze.com
Currently I have 2TB on their servers. And to show my sincerity, notice that I am NOT linking this via their commission deal.

I've heard of backblaze and will look into them more due to your post; thanks.

What do you do for local storage? Or DO you do anything for local storage anymore?
 
Back
Top