You do have a backup (plan), don't you?

Everybody has probably read a dozen times about how important backups are and how much you are screwed if you don't have a backup (or a wrong/old/incomplete one). So it should be save to assume that at least every IT-Pro makes regular backups.

That was what I thought when a co-worker of mine had a HDD crash some weeks ago. I said to him "You're an IT-Pro so you do have a backup, don't you?" His answer: "Yes, but ..."

This little "but" got me thinking about my own backups. OK, all source code (and important docs) are checked in. It's unlikely that the VC server, its backup and all my clients crash, so it's save enough, for me. But the rest? The weekly, manual backup on an external HDD didn't seem too save when thinking about it. And what about my servers? Damn, I wanted to created a backup plan for the databases and files ... some month before.

After a few thoughts it was obviously my data isn't save, so I started planning. The first step was to make a list of data I wanted to backup and then to decide how to back it up. But that list was just too heterogeneous for a single backup plan. I decided to group the data into categories, depending on importance and size (You can't backup all you VMs in real-time with revisions) and came up with the following:

Local Data

Level 1 (Important Documents, E-Books, Portable Apps)
  • "Real-time" backup/sync using SugarSync
  • When at home: "Real-time" backup to NAS (Synology ds211j with 2TB Raid1)

Level 2 (Documents, Pictures, Videos, Drivers)
  • "Real-time" backup to NAS
  • NAS backup to a cloud storage

Level 3 (Virtual Machines, Software, Games)
  • Weekly, manual update on external HDD

Server Data (Databases, Files)
  • Daily, automated backup to NAS (over sFTP)

I feel a lot better now and really hope I do so rightly.
comments powered by Disqus