Disaster recovery

In the past, disaster recovery has often been thought of in the same way as funeral planning. It isn't pleasant to think about, and everyone thinks that either they don't need it right now or that they have a lot of time to get it done.

The World Trade Center tragedy changed that. In this disaster, we saw that some companies had put in place elaborate disaster recovery plans, but there were others that gave only some thought to it. They took backups offsite, but that was the extent of their disaster recovery plan.

Although these events were very much in the extreme, they point out the importance of a comprehensive disaster recovery plan. Now is a good time to review your disaster recovery plan if you have one, and to put one together if you don't. There are several aspects that must be considered. While there are many business and other logistical issues that must be part of a disaster recovery plan, this article will deal specifically with issues that pertain to network and systems management.

Data management

There is disaster recovery software that manages the backup and recovery of data. Replication and synchronization of data are part of this. But often, critical information is stored in individual databases on employees' computers or mobile devices. Most companies back up their servers, but they may not have a plan in place to regularly back up individual PCs or handhelds, particularly if the employees are mobile.

The danger here is that employees may set up their own " little " databases, such as customer contact lists, for their convenience. Over time, these " little databases " may contain a significant amount of critical data that is at risk of being permanently lost. And more often than not, they are not part of the disaster recovery plan, nor are they controlled.

Alternate site

Having an alternate site for temporarily relocating IT facilities, as well as people, is essential. As part of this plan, important considerations include new network connections, hardware and software replacements, and a way to install all of this. Of course, knowing what's installed is an important piece of this plan, which means that a current inventory of hardware and software should be stored offsite. Going even further, storing current images of desktops offsite would also be wise, to make restoring desktops much quicker and easier. Accurate and current documentation of the IT infrastructure, such as network topology and configurations, must be properly stored on a regular basis.

Redundancy

It's critical that redundancy is built into the system, so that if a site is hit with a disaster, those functions can be quickly restarted at another location. This means that for those systems whose processes are critical to the survival and continuity of the business, there should be redundant systems in place that can take over in the event of a disaster.

People

If operations need to be temporarily relocated to another location, a disaster recovery plan should look at how many people are needed and what their responsibilities should be. Another aspect of the people issue involves automation, particularly where the collective knowledge of the people managing the IT infrastructure is not totally in the heads of those people. Use technologies like policy-based management, root-cause analysis, and knowledge bases to put information within the systems and processes. That way, the organization is less dependent on the knowledge of specific people.

As a part of the disaster recovery plan, keep necessary contacts on hand - your company's regular phone company contact, your hardware and software vendor contacts, etc.

Outsourcers and service providers are also viable alternatives for temporary relocation of functions.

Here are a few more tips for disaster recovery:

* Plan for the worst, so you'll be prepared for every eventuality.

* Revisit your plan and update it on a regular basis, so that it's kept relevant and adjusts to the changes that are normal in most IT organizations.

* Be creative in building a plan that includes a variety of solutions that are executable in a short period of time. The survival of the company may depend upon the speed with which the infrastructure can be rebuilt.

* Document the plan well, and be sure to have copies of the plan stored in geographically dispersed locations.

Although disaster recovery doesn't seem to be relevant to the daily noise and activity that IT managers have to deal with, you'll be glad you have one in place if you need it.

Dennis Drogseth is a director with Enterprise Management Associates, a leading analyst and market research firm based in Boulder, Colorado, focusing exclusively on all aspects of enterprise management. Dennis has extensive experience in network management platforms and products and is researching trends in management software and changing IT roles internationally. His 18-plus years of experience in high-tech includes positions at IBM and Cabletron. He has been quoted in the press and is a speaker at industry events. He can be reached via e-mail.

Audrey Rasmussen is a research director with Enterprise Management Associates in Boulder, Colorado, a leading analyst and market research firm focusing exclusively on all aspects of enterprise management. Audrey has more than 20 years of experience working with distributed systems, applications and networks. Her current focus at EMA is e-business, SMB/SME and MSPs. She can be reached via e-mail.

Enterprise Management Associates in Boulder, Colorado, is a leading analyst and market research firm focusing exclusively on all aspects of enterprise management software and services.

Be impulsive
Network World, 09/24/01

Archive of Network World on Network Systems Management newsletters