A disaster recovery plan is a documented process to recover and protect a business IT infrastructure in the event of a disaster. Basically, it provides a clear idea on various actions to be taken before, during and after a disaster.
Disasters are natural or man-made. Examples include industrial accidents, oil spills, stampedes, fires, nuclear explosions / nuclear radiation and acts of war etc. Other types of man-made disasters include the more cosmic scenarios of catastrophic global warming, nuclear war, and bioterrorism whereas natural disasters are earthquakes, floods, heat waves, hurricanes / cyclones, volcanic eruptions, tsunamis, tornadoes and landslides, cosmic and asteroid threats .
Disaster can not be eliminated, but proactive preparation can mitigate data loss and disruption to operations. Organizations require a disaster recovery plan that includes formal plan to consider the impacts of disruptions to all essential business processes and their dependencies. Phase wise plan consists of the precautions to minimize the effects of a disaster so the organization can continue to operate or quickly resume mission-critical functions.
The Disaster Recovery Plan is to be prepared by the Disaster Recovery Committee, which includes representatives from all critical departments or areas of the department's functions. The committee should have at least one representative from management, computing, risk management, records management, security, and building maintenance. The committee's responsibility is to prepare a timeline to establish a reasonable deadline for completing the written plan. The also responsible to identify critical and noncritical departments. A procedure used to determine the critical needs of a department is to document all the functions performed by each department. Once the primary functions have been recognized, the operations and processes are then ranked in order of priority: essential, important and non-essential.
Typically, disaster recovery planning involves an analysis of business processes and continuity needs. Before generating a detailed plan, an organization often performs a business impact analysis (BIA) and risk analysis (RA), and it establishes the recovery time objective (RTO) and recovery point objective (RPO). The RTO describes the target amount of time a business application can be down, typically measured in hours, minutes or seconds. The RPO describes the previous point in time when an application must be recovered.
The plan should define the roles and responsibilities of disaster recovery team members and outline the criteria to launch the plan into action, however, there is no one right type of disaster recovery plan, nor is there a one-size-fits-all disaster recovery plan. Basically, there are three basic strategies that feature in all disaster recovery plans: (a) preventive measures, (b) detective measures, and (c) corrective measures.
(a) Preventive measures: will try to prevent a disaster from occurring. These measures seek to identify and reduce risks. They are designed to mitigate or prevent an event from happening. These measures may include keeping data backed up and off-site, using surge protectors, installing generators and conducting routine inspections.
(b) Detective measures: These measures include installing fire alarms, using up-to-date antivirus software, holding employee training sessions, and installing server and network monitoring software.
(c) Corrective measures: These measures focus on fixing or restoring the systems after a disaster. Corrective measures may consist keeping critical documents in the Disaster Recovery Plan.
The Plan should include a list of first-level contacts and persons / departments within the company, who can declare a disaster and activate DR operations. It should also include an outline and content staging the exact procedures to be followed by a disaster. At least 2-4 potential DR sites with hardware / software that meets or exceeds the current production environment should be made available. DR best practices indicate that DR sites should be at least 50 miles away from the existing production site so that the Recovery Point Objective (RPO) / Restoration Time Objective (RTO) requirements are satisfied
The recovery plan must provide for initial and ongoing employee training. Skills are needed in the reconstruction and salvage phases of the recovery process. Your initial training can be accomplished through professional seminars, special in-house educational programs, the wise use of consultants and vendors, and individual study tailor to the needs of your department. A minimal amount of training is necessary to assist professional restorers / recovery contractors and others having little knowledge of your information, level of importance, or general operations
An entire documented plan has to be tested entirely and all testing report should be logged for future prospect. This testing should be treated as live run and with ample of time. After testing procedures have been completed, an initial "dry run" of the plan is performed by conducting a structured walk-through test. The test will provide additional information regarding any further steps that may need to be included, changes in procedures that are not effective, and other appropriate adjustments. These may not become evident without an actual dry-run test is performed. The plan is subjectively updated to correct any problems identified during the test. Initially, testing of the plan is done in sections and after normal business hours to minimize disruptions to the overall operations of the organization. As the plan is further polished, future tests occur during normal business hours.
Once the disaster recovery plan has been written and tested, the plan is then submitted to management for approval. It is top management's ultimate responsibility that the organization has a documented and tested plan. Management is responsible for establishing the policies, procedures, and responsibilities for comprehensive contingency planning, and reviewing and approving the contingency plan annually, documenting such reviews in writing.
Another important aspect that is often overlooked is the frequency with which DR Plans are updated. Yearly updates are recommended but some industries or organizations require more frequent updates due to business processes evolve or because of quicker data growth. To stay relevant, disaster recovery plans should be an integral part of all business analysis processes and should be revisited at every major corporate acquisition, at every new product launch, and at every new system development milestone.
Your business does not remain the same; businesses grow, change and realign. An effective disaster recovery plan must be regularly reviewed and updated to make sure it reflects the current state of the business and meets the goals of the company. Not only should it be reviewed, but it must be tested to ensure it would be a success if implemented.
When things go awry, it's important to have a robust, targeted, and well-tested disaster recovery plan. Without a Disaster Recovery (DR) plan, your organization is at exceptional risk of loss of business, hacking, cyber-attacks, loss of confidential data, and more.
Source by Shawn Millar