Blogging service JournalSpace has been completely wiped out after the drives that housed their entire database were overwritten.
The problem was that their backups weren’t actually backups at all. The servers were set up with a mirrored RAID system so that if the primary drive should fail the secondary drive would be used to recover the primary. This alone is risky business, as it only protects you from the failure of one drive. In the case of JournalSpace, the drive didn’t fail but instead the data was overwritten/erased on one drive leading the other drive to follow suite and clear itself. A data recovery team was unable to retrieve the database.
Here’s a quick 1 line script to automate backups so this doesn’t happen to you…
rsync -r -t -v -h --progress --delete --ignore-errors -c -l -z /home/username/ /backup/
Then just save that as a bash script (e.g., backup.sh) and setup a cron job (crontab -e) to run it daily, weekly, or monthly.
Related Posts: On this day...
- D.Veloped - Work:Party mashup - 2012
- Asus loads shotgun with tablets large and small - 2011
- Brilliant scheme by Delta... I think students of economics will appreciate this - 2011
- Windows 7 "GodMode" - 2010
- New airport scanners break kiddie-porn laws - 2010
- Celebrity Twitter Accounts Hacked - 2009
- Ron Paul Supporters Stage Internet Coup - 2009
- Legally download every single Beatles song ever released for free - 2009
- Linux phone to Debut upgrade at CES - 2008
- The Most Hated Company In the PC Industry - 2008