Items 1, 2, and 3.
I'm still looking for that perfect solution for small office / home office backup needs. It's amazing to me that there are so many potential solutions out there, but none seem to quite hit the trust + simplicity + speed + cost points that I somehow feel are reasonable. Maybe I'm being unreasonable. Maybe I just haven't looked the right place yet. Or maybe I just haven't defined well enough what I want, so I think I'll start there.
.
1. The starting point - back up locally
Perhaps, above all else, I think a key requirement of backup is that is *start* with a local backup. Client systems, especially notebook users, need to be able to get their data backed up locally, at LAN speeds, without any delays caused by Internet bandwidth. Likewise, when you need to restore something, especially something big (or rebuild a complete machine), having the backup data local is a key. The local backup is ideally some sort of appliance, or mostly-dedicated system, such that you can trust it to be there an on all the time. Barracuda's backup does this, so does Zenith's BDR & ARCA, SonicWall's CDP, and I'm sure many others do as well. Based on other points to follow, this doesn't have to be the most expensive piece of hardware in the world because it's not a single-point system.
2. 3-2-1 rule
This isn't my rule. I learned of the term from the SecurityNow podcast, and they actually got it from Peter Krogh, and it probably has origins even further back. The concept: Data needs to always be [at least] three places, it needs to be on two different types of media, and one of those should be off-site.
3. Off-site SOON, but doesn't have to be NOW
My opinion only! For most SOHOs, near-real-time off-site backup is NOT a requirement. If you have an eCommerce site, that's different, but that's probably not located at your office. If it is, you have a whole different set of problems that I'm not addressing here. If you are getting frequent backups, per #1 above, then if the off-site backup lags by a few hours, to maybe even a full day, you are in a pretty low risk situation. Fire, flood, theft, or other local catastrophe would be bad, but at worst case you'd lose approximately 1 day's worth of data updates. Compared to the rest of your loss, that's not a big deal.
The local backup device should take advantage of unused bandwidth, so it would be nice if it knew how to monitor bandwidth, but simple throttling based on days/hours is probably plenty good for most organizations. What is important is that the off-site backup process is handled by the local backup device, not by the clients. If client machines are turned off overnight, or in the case of notebooks, not on the LAN, the local backup to remote backup process still happens.
Next up: reporting needs, then more.
Recent Comments