It 240 Disaster Plan

Disaster Plan

Doreen A. Evans

IT/240

May 22, 2011

Michael Gioffreda

XYZ Computers

The primary step in formulating a disaster recovery plan is accomplishing a thorough risk investigation of the computer systems. All the probable risks need to be jotted down that imperil system uptime and how impendent they are in a particular IT shop should be assessed. Anything that can cause a system outage is a risk, from comparatively common man made threats like accidental data deletions and virus attacks to more uncommon natural threats like fires and floods. Which of the threats are the most probable to happen should be analyzed and prioritized using a simple system: each threat should be ranked in two significant categories, impact and probability. In every category, the risks should be rated as low, medium, or high.

Once the risks are assessed, the common question that is 'what can we do to inhibit them, and how much will it cost?' should be analyzed. Or common problems like “Can I anticipate a risk before it hits? How can I decrease the potency of it taking place? How do I reduce its affects to the business?” For instance, our small California Internet company could enforce an emergency power supply to extenuate its power outage threat and have all its data backed up regularly on RAID tapes, which are stored at a remote site in case of an earthquake. The more preventative methods are set up direct the better. Emerson says, "Dollars spent in prevention are worth more than dollars spent in recovery."

According to Emerson, when formulating a DRP, IT units are blasting in the dark sans those business indications. Both IT and the business units must comply on which information and applications are most vital to the business and require to be retrieved most fast in case of a disaster. The running of our small Internet company, for instance, may resolute they can provide the finance only for the emergency generators and the company will have to presume the threat of an...