Disaster Recovery, Research Paper Example

The software and the hardware used in running crucial business applications are covered under a disaster recovery plan (DRP), as well as the associated processes to smoothly transition in the unexpected occurrence of a human error or natural disaster. It is therefore important prior to creating a full disaster plan, to first assess the mission critical business processes and associated applications in order to plan effectively. Furthermore, it is pertinent to assume a certain amount of risk, often by estimating how much data might be lost in the occurrence of a disaster. In addition to minimizing the disruptions of operations and ensuring some level of organizational stability and recovery after a disastrous event, a DRP ensures security, minimizes delay risks, ensure reliability of back-up systems, and minimizes decision-making in the event of a disaster.

The planning process of a disaster recovery plan is composed of a number of stages. First, the top management should commit by supporting the initiative and be involved in the development of the DRP. In addition to taking full responsibility in ensuring the coordination of the plan within the organization, the management should ensure its effectiveness, by allocating adequate financial and personnel resources and time (Harney, 2004).

Secondly, the development and implementation of the plan should be delegated to a planning committee; composed of representatives from the organization’s functional areas. Committee members such as the processing manager and the operations manager should also participate in defining the scope.  Thirdly, the committee should conduct a business impact analysis and risk analysis with primary focus on such likely disasters from technical, natural or human threats. To determine the potential consequences and impact associated with unlikely disaster occurrences, analysis should be conducted in every functional area of the organization. In order to cater for greatly unexpected disasters, the plan should consider a ”worst case” scenario, such as complete destruction of the premises. As such, assessment should be conducted on the possible consequences and impacts from loss of services and information, as well as costs resulting thereof (Hoffer, 2001).

Fourth, the plan should establish operations and processing priorities by evaluating the critical needs of each functional, personnel, documentation, processing services, and vital records areas. At this stage, disasters can be classified as natural or man-made, and further as either rapid onset or slow onset. Additionally, scenario development and impacts analysis are vital in categorizing the threat level of the potential disaster. Therefore, a DRP is regularly tested to ensure its effectiveness while the plan should ensure clear delegation of responsibilities; clear establishment of priorities; execution of alert roster and notification of personnel in charge; action steps to minimize the impact; documentation of the disaster; and alternative implementations for various systems components (Harney, 2004).

Confidentiality should be ensured while dealing with customer or external stakeholder information. Loss of the same should be reported so that the recovery team should take utmost care to avoid the pertinent information falling in the wrong hands. However, instances of data loss can be mitigated by ensuring obsolete and redundant software are either updated or completely replaced. This way, fraudulent individuals or “hackers” are restricted from accessing pertinent information (Hoffer, 2001).

Additional physical security measures include server facility fire suppression that protects back-up files and information. This feature is also vital during a fire breakout as information can be salvaged. Similarly, security on the information especially where online data is involved can be secured using data encryption.

References

Hoffer, J. (2001). “Backing Up Business – Industry Trend or Event.” Health Management Technology.

Harney, J. (2004). Business continuity and disaster recovery: Back up or shut down. AIIM E-Doc Magazine, 18(4).