I’m Michael Hampton, principal author of Homeland Stupidity, a U.S. politics blog. Today I want to address the issue of business continuity, that is, have you planned what to do if a disaster strikes your professional blogging operation?
Over the past few months I’ve had some all-too-common computer emergencies arise, and had to move fast to recover from them. In October, filesystem corruption ate about two weeks worth of e-mail, critical files such as all of my RSS feeds, and a few works in progress. I didn’t have up to date backups, and without them I’m only getting by as best I can without the missing materials.
And late Monday night my computer decided, during a round of system updates, to uninstall my feed reader, and then refused to reinstall it on Tuesday.
These are just two examples of things that can go wrong in pro blogging, but there are others. Have you planned what to do if your Web host suddenly goes down, as TypePad did recently, goes out of business entirely, or is hit by a natural disaster?
It’s one thing to simply address crises as they arise. About eight months ago, when my blog was still a small site running on my home computer, I needed to reinstall the entire operating system due to severe filesystem corruption. I pulled out an old Pentium 166 which I had laying around and pressed it into service as a temporary Web server to host my site while I was making repairs to my main computer. It was incredibly slow, but it served for the nearly full day it took to get the main computer running again.