This paper discusses an approach for creating a good disaster recovery plan for a business enterprise. When a disaster strikes, the normal operations of the enterprise are suspended and replaced with operations spelled out in the disaster recovery plan. The disaster recovery plan does not stop at defining the resources or processes that need to be in place to recover from a disaster. Looking at the above example, multiplying the likelihood time, impact time, and restoration time yields a rough risk analysis score.
The cost of downtime is the main key to calculate the investment needed in a disaster recovery plan. Tangible costs are those costs that are a consequence of a business interruption, generating loss of revenue and productivity. In the case of data systems, for example, the recovery mechanism usually involves having the critical data systems replicated somewhere else in the network and putting them online with the latest backed up data available.
Quick and precise detection of a disaster event and having an appropriate communication plan are the key for reducing the effects of the incoming emergency; in some cases it may give enough time to allow system personnel to implement actions gracefully, thus reducing the impact of the disaster. Download unlimited PowerPoint templates, charts and graphics for your presentations with our annual plan. The best strategy is to have some kind of disaster recovery plan in place, to return to normal after the disaster has struck. Figure 1 depicts the cycle of stages that lead through a disaster back to a state of normalcy.
Only when these are assessed and the affected systems are identified can a recovery process begin.
It is also useful to determine how many powers feeds operate within the facility and if necessary make the power system redundant. But several key members of the committee, such as the operations manager, operations coordinator, and the respective operations team leads, will always actively participate.
Execution Phase: In this phase, the actual procedures to recover each of the disaster affected entities are executed. At the end of this phase, recovery staff will be ready to execute contingency actions to restore system functions on a temporary basis.
The call tree should document primary and alternate contact methods and should include procedures to be followed if an individual cannot be contacted. The disaster recovery system cannot replace the normal working system forever, but only supports it for a short period of time. Finally, ongoing procedures for testing and improving the effectiveness of the disaster recovery system are part of a good disaster recovery plan. And the fourth section explains what information the disaster recovery plan should contain and how to maintain the disaster recovery plan. Essential functions are those whose interruption would considerably disrupt the operations of the business and may result in financial loss. To mitigate the risk of disruption of business operations, a recovery solution should involve disaster recovery facilities in a location away from the affected area. Factors such as workplace violence, bomb threats, trespassing, sabotage, and intellectual property loss are also considered during the security risk analysis.
Sorting the table in descending order will put the biggest risks to the top, and these are the risks that deserve more attention.
The entities with less downtime tolerance limit should be assigned higher priorities for recovery.
Procedures should contain the process to alert recovery personnel during business and nonbusiness hours.
Instead of paying a thousand of dollars registering with disaster recovery plan which will make virtual copies of your files. Building material of a Data Center should be strong in order to stand still against the most fearful natural threat earthquakes and also other serious threats like bombs and weather condition. Another way of not loosing your data is to have complete recovery of an entire technology infrastructure. As MySQL gains widespread adoption and moves more broadly into the enterprise, ZRM for MySQL addresses the growing need among database administrators to protect their digital assets with a comprehensive backup and recovery solution. The Zmanda Disaster Recovery Solution for MySQL provides robust and cost-effective disaster recovery capabilities for your critical MySQL databases.
By deploying the Disaster Recovery (DR) Option for MySQL you can avoid the cost and complexity of replicating each individual MySQL database.
The solution provides full failover and restoration capability for your ZRM implementation. Leverage our Expertise: Zmanda Professional Services engineers have extensive experience creating backup strategies across all MySQL storage engines and configurations.
Learn how to develop disaster recovery strategies as well as how to write a disaster recovery plan with these step-by-step instructions. The following section details the elements in a DR plan in the sequence defined by ISO 27031 and ISO 24762. In most organizations, Disaster Recovery Planning is the quintessential complex, unfamiliar task. Procedures should ensure an easy-to-use and repeatable process for recovering damaged IT assets and returning them to normal operation as quickly as possible. Located at the end of the plan, these can include systems inventories, application inventories, network asset inventories, contracts and service-level agreements, supplier contact data, and any additional documentation that will facilitate recovery. These are essential in that they ensure employees are fully aware of DR plans and their responsibilities in a disaster, and DR team members have been trained in their roles and responsibilities as defined in the plans. Here we can see the critical system and associated threat, the response strategy and (new) response action steps, as well as the recovery strategy and (new) recovery action steps. If DR plans are to be invoked, incident response activities can be scaled back or terminated, depending on the incident, allowing for launch of the DR plans.
And since DR planning generates a significant amount of documentation, records management (and change management) activities should also be initiated.
For some businesses, issues such as supply chain logistics are most crucial and are the focus on the plan.
This section defines the criteria for launching the plan, what data is needed and who makes the determination. If your organisation already has records management and change management programmes, use them in your DR planning. For others, information technology may play a more pivotal role, and the Business Continuity Disaster Recovery Plan may have more of a focus on systems recovery.


Included within this part of the plan should be assembly areas for staff (primary and alternates), procedures for notifying and activating DR team members, and procedures for standing down the plan if management determines the DR plan response is not needed.
Disk costs are a small component; when you factor in performance degradation, staffing, backup software, and data center costs (air, power, space), the cost of having low-value data in SharePoint and SQL Server adds up.
This involves quality checks to verify that backups complete without errors, restores complete without errors, and backup and recovery times and restore points meet SLAs. The process of preparing a disaster recovery plan begins by identifying these causes and effects, analyzing their likelihood and severity, and ranking them in terms of their business priority. The second section of this paper explains the methods and procedures involved in the disaster recovery planning process.
Once the disaster risks have been assessed and the decision has been made to cover the most critical risks, the next step is to determine and list the likely effects of each of the disasters.
Intangible costs include lost opportunities when customers would approach competitors, loss of reputation, and similar factors. Considering multiple options and variations of disaster recovery mechanisms available, it is necessary to carefully evaluate the best suitable recovery mechanism for an affected entity in a particular organization.
Though both concepts are related to business continuity, high availability is about providing undisrupted continuity of operations whereas disaster recovery involves some amount of downtime, typically measured in days.
An effective disaster recovery plan plays its role in all stages of the operations as depicted above, and it is continuously improved by disaster recovery mock drills and feedback capture processes.
A key factor in evaluating risks associated with telephone systems is to study the telephone architecture and determine if any additional infrastructure is required to mitigate the risk of losing the entire telecommunication service during a disaster. Reconstitution Phase: In this phase the original system is restored and execution phase procedures are stopped. Procedures to save lives and propertyRecovery procedureshelp us restart businessprocesses in the shortand long-term.Ex.
Recovery from this type of failure may be lengthy and expensive due to the need to replace or update software and equipment and retrain personnel. Depending on the data system, there may be options of autorecovery or manual recovery, and the cost and recovery time factors of each mechanism vary. To minimize disaster losses, it is very important to have a good disaster recovery plan for every business subsystem and operation within an enterprise. This whole procedure takes a lot of time and it is not possible for the companies which works round the clock and consistently. This entry was posted in Data Centers India and tagged Colocation Services India, Data Center India, Fully Managed Data Center. To solve the problem, most of the companies have their own Data Center, all the Data is protected and kept safe.
You backup all your critical databases to the ZRM server already; the DR Option replicates all your backup archives, backup catalog and configuration to the remote server. Formulating a detailed recovery plan is the main aim of the entire IT disaster recovery planning project. Important: Best-in-class DR plans should begin with a few pages that summarise key action steps (such as where to assemble employees if forced to evacuate the building) and lists of key contacts and their contact information for ease of authorising and launching the plan. All Business Continuity Disaster Recovery Planning efforts need to encompass how employees will communicate, where they will go and how they will keep doing their jobs. Click on the link below to get the Disaster Planning and Business Continuity Planning Template full table of contents and selected sample pages now and make it part of your Disaster Recovery Planning toolkit. This process can be seen as a timeline, such as in Figure 2, in which incident response actions precede disaster recovery actions. Much of this pain is felt in backup and recovery, which must occur on three levels: item, site, and farm.
This section should specify who has approved the plan, who is authorised to activate it and a list of linkages to other relevant plans and documents. The more detailed the plan is, the more likely the affected IT asset will be recovered and returned to normal operation. What's more, the myriad interconnected data, application and other resources that must be recovered after a disaster make recovery an exceptionally difficult and error-prone effort. The second is to clearly and expressly document all these procedures so that in the event of a SOX audit, the auditors clearly see that the Disaster Recovery and Business Continuity Plan exists and appropriately protects the data and assets of the enterprise.. Technology DR plans can be enhanced with relevant recovery information and procedures obtained from system vendors. Even if you have never built a Disaster Recovery plan before, you can achieve great results.
Check with your vendors while developing your DR plans to see what they have in terms of emergency recovery documentation. The test plan should be used during the proof of concept or pilot operation, running end-to-end tests, and for getting stakeholders to sign off physically. Often SharePoint backup and recovery toolsets require servers to be loaded with Windows Server and joined to the domain. The first step in planning recovery from unexpected disasters is to identify the threats or risks that can bring about disasters by doing risk analysis covering threats to business continuity.
Note that multiple causes can produce the same effects, and in some cases the effects themselves may be the causes of some other effects. How the disaster affected entities depend upon each other is crucial information for preparing the recovery sequence in the disaster recovery plan.
The roles, responsibilities, and reporting hierarchy of different committee members should be clearly defined both during normal operations and in the case of a disaster emergency.
The causes can be natural or human or mechanical in origin, ranging from events such as a tiny hardware or software component's malfunctioning to universally recognized events such as earthquakes, fire, and flood. Risk analysis (sometimes called business impact analysis) involves evaluating existing physical and environmental security and control systems, and assessing their adequacy with respect to the potential threats.
Different secure access and authorization procedures, manual as well as automated ones, are enforced in enterprises. It should be well informed about the geographical, political, social, and environmental events that may pose threats to the company's business operations. If the unexpected does happen, your business continuity plan may be the difference between your business recovering or failing from the event. Every process and tool that makes up the personal job must be examined carefully and accounted as essential.
At the earliest possible time, the disaster recovery process must be decommissioned and the business should return to normalcy. When you are operating large number of clients, first thing that comes to your mind is backup for all customer database because if you loose that you will loose everything.


In recent years not just bigger companies but smaller ones keep backup data for their clients. This replication can be done per your desired schedule, independent of the schedule of your backup runs.
But the critical point is that neither element can be ignored, and physical, IT and human resources plans cannot be developed in isolation from each other.
The next section should define roles and responsibilities of DR recovery team members, their contact details, spending limits (for example, if equipment has to be purchased) and the limits of their authority in a disaster situation. Then define step-by-step procedures to, for example, initiate data backup to secure alternate locations, relocate operations to an alternate space, recover systems and data at the alternate sites, and resume operations at either the original site or at a new location. Keep in mind that SharePoint-specific backup toolsets don’t have the throughput of a SQL Server backup toolset. The magnitude of a risk may be different considering the affected component, its location, and the time of occurrence.
The intention of this exercise is to produce a list of entities affected by failure due to disasters, which need to be addressed by the disaster recovery plan.
Once the list of affected entities is prepared and each entity's business criticality and failure tendency is assessed, it is time to analyze various recovery methods available for each entity and determine the best suitable recovery method for each. Note that not all the members of the Disaster Recovery Committee may actively participate in the actual disaster recovery. The ultimate results are a formal assessment of risk, a disaster recovery plan that includes all available recovery mechanisms, and a formalized Disaster Recovery Committee that has responsibility for rehearsing, carrying out, and improving the disaster recovery plan. Typical civil risks include labor disputes ending in strikes, communal riots, local political instability, and so on. A higher value would mean longer restoration time hence the priority of having a Disaster Recovery mechanism for this risk is higher.
While the time taken and cost to clean up the area are the same in both cases, the first case may require shutting down the assembly line area, which adds downtime cost to this event. Initially you feel that a data recovery plan will cost you some extra bucks, but later on you will this save from alot of expenditure that could be a lot more then what you have invested.
Once you have identified your critical systems, RTOs, RPOs, etc, create a table, as shown below, to help you formulate the disaster recovery strategies you will use to protect them. Preparation for Disaster Recovery and Business Continuity in light of SOX has two primary parts. It is in these plans that you will set out the detailed steps needed to recover your IT systems to a state in which they can support the business after a disaster. Based on the findings from incident response activities, the next step is to determine if disaster recovery plans should be launched, and which ones in particular should be invoked.
Human caused: These disasters include acts of terrorism, sabotage, virus attacks, operations mistakes, crimes, and so on. It may be noticed that two or more disasters may affect the same entities, and it can be determined which entities are affected most often. While evaluating these risks, the following essential utilities and commodities need to be considered.
In Figure 3, the entities that fail due to the earthquake disaster are office facility, power system, operations staff, data systems, and telephone system. After the disaster detection, a notification should be sent to the damage assessment team, so that they can assess the real damage occurred and implement subsequent actions. Data Centers are mostly located in the outskirts of a city away from the traffic and chaos of the main city. Disaster Recovery Business Continuity Template (WORD) - comes with the latest electronic forms and is fully compliant with all mandated US, EU, and ISO requirements. A section on plan document dates and revisions is essential, and should include dates of revisions, what was revised and who approved the revisions.
Electricity: To analyze the power outage risk, it is important to study the frequency of power outage and the duration of each outage.
This information becomes crucial for preparing the recovery sequence in the disaster recovery plan. Catastrophe Goal is to plan for a plausible disaster Plausible likelihood of occurrence Plausible steps to recover Not for the most catastrophic event imaginable Impossible to plan for extreme catastrophes Disaster Recovery Planning at MSU Business Functions vs. In addition to using the strategies previously developed, IT disaster recovery plans should form part of an incident response process that addresses the initial stages of the incident and the steps to be taken.
Once the plan has been launched, DR teams take the materials assigned to them and proceed with response and recovery activities as specified in the plans. Fire: Many factors affect the risk of fire, for instance the facility's location, its materials, neighboring businesses and structures, and its distance from fire stations. For less critical data systems, there may be an option to have spare server hardware, and if required these servers could be configured with the required application. If some unexpected disaster strikes and you lost of data, this may result you pay huge amount of fine to your clients. Physical Security: Security risks have gained attention in recent years, and nowadays security is a mandatory 24-hour measure to protect each and every asset of the company from both outsiders and employees.
This committee should have representation from all the different company agencies with a role in the disaster recovery process, typically management, finance, IT (multiple technology leads), electrical department, security department, human resources, vendor management, and so on. In such case everything is recovered hardware, data, IT equipments, application and communications.
Data systems risks are those related to the use of shared infrastructure, such as networks, file servers, and software applications that could impact multiple departments. During a disaster, this committee ensures that there is proper coordination between different agencies and that the recovery processes are executed successfully and in proper sequence. Data Centers are heavily monitored and protected since most of the companies depend on them considerably. An effective departmental risk assessment needs to consider all the critical functions within that department, key operating equipment, and vital records whose absence or loss will compromise operations. Some time back a survey showed that only mere 6% companies which lost data in some kind of disaster continues in business. Once the evaluation of the major risk categories is completed, it is time to score and sort all of them, category by category, in terms of their likelihood and impact.



Earthquake preparedness checklist lic 9148
Emergency preparedness week
Solar disaster movies
Supplies to survive in the wilderness


Comments

  1. 08.05.2015 at 13:28:14


    Honye...this is a great place had relied on my phone's gps.

    Author: ZEKK
  2. 08.05.2015 at 18:18:33


    About such lot more than 16 African nations, and made.

    Author: MARINA
  3. 08.05.2015 at 15:20:18


    Who played the zombies had primarily based.

    Author: GaLaTaSaRaY