Learn how to develop disaster recovery strategies as well as how to write a disaster recovery plan with these step-by-step instructions.
Formulating a detailed recovery plan is the main aim of the entire IT disaster recovery planning project.
Once this work is out of the way, you’re ready to move on to developing disaster recovery strategies, followed by the actual plans. 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. Once your disaster recovery strategies have been developed, you’re ready to translate them into disaster recovery plans.
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. The following section details the elements in a DR plan in the sequence defined by ISO 27031 and ISO 24762.
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. Business Continuity Planning Process Diagram - Text VersionWhen business is disrupted, it can cost money.
This excerpt from "System Center Operations Manager 2007 Unleashed" helps prepare you for the possibility of a catastrophic failure, and guides you through the process of recovering from a total loss or a downed RMS. Your plan should assume the worst but be able to concisely and efficiently restore Operations Manager at a minimum to the last backup of your databases. There are at two potential scenarios for disaster recovery, discussed in the next sections. Although this is a very simple implementation of Operations Manager, it is intended to show you the steps necessary to recover OpsMgr from a complete hardware failure of the management server.
In addition to deploying log shipping, you will need the RMS and SRS encryption keys for a successful recovery. Part of any successful disaster recovery plan includes understanding your current configuration.
Our unmatched topical depth outlined below matches the very specific information needs of storage pros from Backup Software to Disaster Recovery Planning to Continuous Data Protection and more. As we've been talking to customers at the start of the year, the majority of you are in various states of your event planning for 2013.
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. Then, you’ll need to establish recovery time objectives (RTOs) and recovery point objectives (RPOs). Here we’ll explain how to write a disaster recovery plan as well as how to develop disaster recovery strategies. 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.


This process can be seen as a timeline, such as in Figure 2, in which incident response actions precede disaster recovery actions.
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. 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. A section on plan document dates and revisions is essential, and should include dates of revisions, what was revised and who approved the revisions.
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.
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. You should have a well-documented recovery plan that would work for every conceivable type of disaster that could occur, from hardware failures to a total datacenter loss. You need to not only develop a detailed plan for the various contingencies, but should also practice the various scenarios in a development environment until you (and others on your staff for when you are not available) are comfortable with the process.
This prevents OpsMgr from writing data to this database, which you will be overlaying as part of your recovery process. Your actual plan should contain greater detail, including specific hard drive configurations, the exact installation options, the SQL steps necessary to delete and restore the databases, and so forth. No media outlet – or any outlet for that matter – has so much objective, focused evergreen technical content covering the storage, backup and disaster recovery planning markets. We take main topics like storage networking, backup and disaster recovery and break them down to targeted topics like SSD applications, data deduplication and off-site replication. There are more than 9,000 articles on disaster recovery planning in our storage network, and users take more than 907,316 actions on the topic in 12 months. 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.
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. 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. 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. The more detailed the plan is, the more likely the affected IT asset will be recovered and returned to normal operation. And since DR planning generates a significant amount of documentation, records management (and change management) activities should also be initiated. The appropriate level of service packs and security patches are applied—be sure to be at the same level of software maintenance that you had with your original system.


This event brings IT professionals together with industry experts, analysts and vendors who can help them plan, implement and maximize the best storage initiatives today and well into the future. This section defines the criteria for launching the plan, what data is needed and who makes the determination. Technology DR plans can be enhanced with relevant recovery information and procedures obtained from system vendors. If your organisation already has records management and change management programmes, use them in your DR planning.
Figure 12.23 illustrates a sample disaster recovery solution that includes log shipping for the Operational and Data Warehouse databases. 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.
Check with your vendors while developing your DR plans to see what they have in terms of emergency recovery documentation.
If you need to recover your systems, you would restore database backups, promote the management server to become the RMS, and connect the systems. Therefore, recovery strategies for information technology should be developed so technology can be restored in time to meet the needs of the business. Another approach to use virtualization to provide an off-site disaster recovery solution would be through sending regularly scheduled backups of the virtual hard drives to the disaster recovery location.
In the event of a disaster, the backup copies of the virtual hard drives are activated and IP address changes made to reflect their new physical location. The point in time when a function or process must be recovered, before unacceptable consequences could occur, is often referred to as the “Recovery Time Objective.”Resource Required to Support Recovery StrategiesRecovery of a critical or time-sensitive process requires resources. Completed worksheets are used to determine the resource requirements for recovery strategies.Following an incident that disrupts business operations, resources will be needed to carry out recovery strategies and to restore normal business operations.
This information will be used to develop recovery strategies.Recovery StrategiesIf a facility is damaged, production machinery breaks down, a supplier fails to deliver or information technology is disrupted, business is impacted and the financial losses can begin to grow. Recovery strategies are alternate means to restore business operations to a minimum acceptable level following a business disruption and are prioritized by the recovery time objectives (RTO) developed during the business impact analysis.Recovery strategies require resources including people, facilities, equipment, materials and information technology. An analysis of the resources required to execute recovery strategies should be conducted to identify gaps. Equipping converted space with furnishings, equipment, power, connectivity and other resources would be required to meet the needs of workers.Partnership or reciprocal agreements can be arranged with other businesses or organizations that can support each other in the event of a disaster. Periodic review of the agreement is needed to determine if there is a change in the ability of each party to support the other.There are many vendors that support business continuity and information technology recovery strategies. The availability and cost of these options can be affected when a regional disaster results in competition for these resources.There are multiple strategies for recovery of manufacturing operations.



Training.fema.gov/is/ceus.aspx
How to build empire state building in minecraft


Comments

  1. 21.01.2014 at 16:43:35


    Protected Cheyenne Mountain Complex shop boxed food in tightly closed the threat is organic.

    Author: 050_475_55_05
  2. 21.01.2014 at 11:15:14


    Macondo wellhead began reaching shore.

    Author: Giz
  3. 21.01.2014 at 13:59:13


    Set a net, below ice also, must be a priority zombie Apocalypse Survival Kit.

    Author: Lenardo_dicaprio
  4. 21.01.2014 at 13:46:54


    Important to have backups helpful for interested in what my mom had to say. Aid your young children.

    Author: BRAT_NARKUSA