If you are having trouble reading this email, read the online version
|
||
| Elements of a Good Disaster Recovery Plan | June 2009 / issue 10 | |
How to Create a Disaster Recovery Plan by Glen Kunene, Senior Editor What would you do if a storm flooded your data center? Or how would you respond if a power outage blacked out your servers? How would you recover your data and keep the business running after an unforeseen disaster? When disasters strike unprepared companies the consequences range from prolonged system downtime and the resulting revenue loss to the companies going out of business completely, yet many IT shops are not prepared to deal with such scenarios. The key to surviving such an event is a business continuity strategy, a set of policies and procedures for reacting to and recovering from an IT-disabling disaster, and the main component of a business continuity strategy is a disaster recovery plan (DRP). In this article, DevX and Cole Emerson, President of Cole Emerson & Associates, Inc., a business-continuity consulting firm, and chairman of the board of DRI International, administrators of a global certification program for business continuity/disaster recovery planners, walk through the basics of creating an effective DRP. Step 1: Risk Analysis For example, a small Internet company (less than 50 employees) located in California could rate an earthquake threat as medium probability and high impact, while the threat of utility failure due to a power outage could rate high probability and high impact. So in this company's risk analysis, a power outage would be a higher risk than an earthquake and would therefore be a higher priority in the disaster recovery plan.
Step 2: Establish the Budget The results of Step 1 should be a comprehensive list of possible threats, each with its corresponding solution and cost. It is imperative that IT presents all of these threats to the business operations units, so they can make an informed decision regarding the size of the disaster recovery budget (i.e., which risks the company can afford to tolerate and which it must pay to mitigate). Emerson believes IT "falls down" in its failure to communicate the real risks for system downtime to the business operations units of their companies. He says, "It's okay for operations to say no; it's not okay for IT not to let them know the risks." A good place to begin is by presenting the cost of downtime to the business. How long can your business afford to be without its computer systems should one of your threats occur? Ultimately, the business operations unit decides which threats the business can tolerate. According to Emerson, when developing a DRP, IT departments are "shooting in the dark without those business indications." Both IT and the business units must agree on which data and applications are most critical to the business and need to be recovered most quickly in a disaster. The management of our small Internet company, for example, may decide they can supply the budget only for the emergency generators and the company will have to assume the risk of an earthquake. |
How to Create a Disaster Recovery Plan (cont'd) by Glen Kunene, Senior Editor Disaster recovery budgets vary from company to company but they typically run between 2 and 8 percent of the overall IT budget. Companies for which system availability is crucial usually are on the higher end of the scale, while companies that can function without it are on the lower end. However, these percentages may be too small. For a large IT shop 15 percent is a best practice rule of thumb according to Emerson Step 3: Develop the Plan
The feedback from the business units will begin to shape your DRP procedures. If, for example, they determine that the company must be up within 48 hours of an incident to stay viable, then you can calculate the amount of time it would take to execute the recovery plan and have the business back up in that timeframe. Emerson suggests that you have the recovery systems tested, configured, and retested 24 hours prior to launching them. He says the set up takes anywhere from 40 hours to days to complete. The recovery procedure should be written in a detailed plan or "script." Establish a Recovery Team from among the IT staff and assign specific recovery duties to each member. The manner in which your team conducts its recovery probably will be no different than its regular production procedures: the chain of command likely won't change and neither will the aspects of the network for which each member is responsible.
Define how to deal with the loss of various aspects of the network (databases, servers, bridges/routers, communications links, etc.) and specify who arranges for repairs or reconstruction and how the data recovery process occurs. The script will also outline priorities for the recovery: What needs to be recovered first? What is the communication procedure for the initial respondents? To complement the script, create a checklist or test procedure to verify that everything is back to normal once repairs and data recovery have taken place. Step 4: Test, Test, Test As your business environment changes, so should your DRP. Reexamine the plan every year on a high level: Do you still need every part of the plan? Do you need to add to it? Will the budget need to be adjusted to accommodate changes to the plan? As applications, hardware, and software are added to your network, they must be brought into the plan. New employees must be trained on recovery procedures. New threats to business seem to pop up every week and a sound DRP takes all of them into account.
|
|
Hot Tips for Keeping Your PC Cool in Summer There are plenty of steps you can take to keep your PC cool during the summer. 1) First, open up your PC from time to time to make sure all internal fans are operating. The onset of hot weather is a good time to tackle this chore. If you're a bit nervous about having to pop open the hood of your computer, don't worry. Usually removing a few easy-to-find screws or a popping a simple latch is all you need to do to inspect the inside of your computer. Most computer manuals tell you how it's done.
| ||
Helpful IT tips 2) Implementing proactive IT management versus reactive management can help catch and eliminate various threats before they have a chance to implicate your IT environment 3) KNOW your IT provider; Many companies imply that their services are top of line with a helpdesk in your area and paint a picture perfect portrait and in the end, you the customer is the one who loses. Check out your provider, visit their facility and meet their helpdesk. You will be surprised as to how many actually are telling the truth. 4) Frequently backup your data; At a minimum it should be done daily 5) If it sounds too good to be true, it might just be. You may be getting a great price initially, but what are you really getting into? Check your IT provider’s references to make sure you make the best decision for your business' future, not just your pocket book |
Click logo above to view video feature Virtual Technology
|
|
![]() |
Happy Birthday Techcess Group!
2009 marks the 5th year anniversary of Techcess Group being in business.
|
|
Copyright © Techcess Group | 832-533-9670 | 3100 Timmons Ln. Suite 350 |
||
| If you wish to cancel your subscription to this newsletter click here | ||