- 1 Vapor IO Brings OpenDCRE to General Availability
- 2 VMware Takes the Wraps Off vRealize Automation and vRealize Business
- 3 Microsoft Previews Hyper-V Containers for Windows Server 2016
- 4 Mirantis Led FUEL Project Gets Installed Under OpenStack Big Tent
- 5 Red Hat Enterprise Linux 7.2 Adds Security, DR Features
Why You Should Be Concerned With Disaster Recovery Page 7
Implementing and Maintaining the Plan
Implementing a disaster recovery plan is not an typical project. For one thing, the plan must cover more than just the IT concerns of physical protection for servers, data, and communications. If things go wrong -- very wrong -- the effect on people and business processes will be equally profound. So the entire company, from executives to general employees, must be included, and often trained, in their part of a recovery plan.
When it comes to the company's servers, no plan can be allowed to sit in the wiring closet for months (or years) without running the risk of becoming obsolete. Not only must the physical aspects of the plan (e.g., links, storage, and synchronization) be periodically tested, but also the procedures and even the assumptions of the recovery should be regularly updated.
Disaster recovery for servers and related equipment, as well as IT operations in general, must be seen as part of an enterprisewide recovery plan. Developing such a plan can be a major undertaking. Recent current events, however, demonstrate that now is a good time to find general background information and inexpensive advice from resources such as the Web and various publications.Quick Resources:
|Disaster Recovery Journal||www.drj.com|
|United States Disaster Preparedness Council||www.usdpc.org|
|Disaster Recovery Institute International||www.dr.org|
|Disaster Recovery Information Exchange (Canada)||www.drie.org|