it disaster recovery planning - stark county mental health & addiction recovery · ·...

StarkMHAR.org

IT Disaster Recovery Planning

Aaron KutcherApril 11th, 2017

* The content of this presentation is for informational purposes only and not intended to be legal advice. Specific questions

regarding compliance should be referred to your legal counsel.

StarkMHAR.org/StarkMHAR

Outline

• Disasters• IT Disaster Recovery Plan• Steps to creating a DR Plan• Recovery


Are You Prepared?


Lessons Learned

• Have a DR Plan• Backups• Keep Paper• Make Friends• Be Lucky• Be Supportive• Look Up• Full recovery takes a long time


Disasters

• A disaster is an occurrence that disrupts the functioning of the organization resulting in loss of data, loss of personnel, loss of business or loss of time.


Disasters

• Natural• Tornadoes, hurricanes, or earthquakes

• Man‐made• Fire, industrial incident, riots or civil unrest, vandalism

• Weather‐related• Ice storms, floods, lightning strikes, power outages


Planning

• Business Continuity (BC)• Disaster Recovery (DR)• Business Impact Assessment (BIA)• Recovery Time Objectives (RTO)• Recovery Point Objectives (RPO)


IT DR Planning

• Why?• Who?• What?• Where?• When?


Why

• Reduce stress during a disaster• Detailed review of IT environment• Regulatory requirements• Customers• Good practice


Who

• The business• Systems and technologies• IT staff

• Networking• Platforms• Project management


What


Where


When


IT DR Plan Structure

1. Develop the contingency planning statement

2. Conduct the BIA3. Identify preventive

controls4. Develop recovery

strategies

5. Develop and IT contingency plan

6. Plan testing, training and exercising

7. Plan maintenance


DR Plan Components (Sample)• Information Technology Statement of Intent• Policy Statement• Objectives• Key Personnel Contact Information• Plan Overview• Emergency Response• Disaster Recovery Team• Emergency Alert, Escalation and DRP Activation• Media• Insurance• Financial and Legal Issues• DRP Exercising• Appendices


Steps to a DR Plan

• Meet• Gather Documents• Obtain• Identify Threats


Steps to a DR Plan

• Identify Vulnerabilities• Review History• Identify Critical Assets


Steps to a DR Plan

• Determine Maximum Outage Time• Identify Procedures• Determine Last Test Time• Identify Response Teams


Steps to a DR Plan

• Identify Vendor Capabilities• Compile Results• Management Review• Prepare IT Disaster Recovery Plans


Steps to a DR Plan

• Test• Update• Audit


Keys to Success

• Management Support• Be Serious• Keep it Simple• Review with Business Units• People are the Most Important


Disaster

• Disasters can be broken into 3 types• Minor• Major• Catastrophic


Event Levels

Minor EventAn operational disruption that generally does not require a declaration process. However it does require proper IT incident management. A minor disaster is usually one in which the outage is anticipated to last approximately one day or less. Damage due to a minor disaster is not extensive. It may consist of minor damage to facilities, hardware, software, or equipment from any cause.


Event Levels

Minor Event Examples:• Partial or total loss of hardware for a period of several hours;

• Recoverable loss of critical data – full recoverability in less than twenty‐four hours;

• Loss of an important computer application


Event Levels

Major Event

An Event in which the outage is anticipated to be greater than one day but not more than one week.

Damage due to a major event is more severe than that due to a minor event but not the extent that the operations affected could not be restored within a week.


Event Levels

Major Event Examples:

• Damage to Operations Center facilities;• Damage to the Data Center and/or hardware resulting in downtime of more than 24 hours;

• Loss of service (air conditioning, electrical power, etc.);• Recoverable loss of critical data; full recoverability taking more than twenty‐four hours.


Event Levels

Catastrophic Event

An outage that is anticipated to be in excess of seven days. Damage due to a Catastrophic Event is severe and could involve total destruction of the facilities or data Center, which necessitates major replacement of equipment and/or major renovation of the facility.


Event Levels

Catastrophic Event Examples:

• Loss of operation Center staff due to uncontrollable factors (outbreak of epidemic disease);

• Destruction of operations facilities;• Destruction of the data Center and/or hardware;• Major telecommunications failure;• Unrecoverable loss of critical data.


Responding to an Event

• MTO – Maximum Tolerable Outage: The longest period of time that your organization can be without its technology resources before it has a material affect on the organization’s finance or reputation.

• RTO – Recovery Time Objective: Time that the mission critical business function can survive without Technology resources before it has a material affect on the organization.

• Fix Window: Predetermined amount of time that is allocated to fix an issue before an official disaster is declared.

• Recovery: Processes and tasks invoked to restore critical IT components in a pre‐defined window before serious impact to the organization’s finances, reputation and customers.


Event Level Objectives

• Minor• Escalate• Monitor• Document

• Major/Catastrophic• DR Plan invoked• Escalate• Report• Recover


Recovery Steps

• Event Detection• Fix Window• Declare• Command Center• Communicate


Command Center


Infrastructure

• Backup/Restore Process• Media Management plans• Media Backup History• System Security• Data Center Security• Event Detection and Notification Process• Data Transmission• Networking• Facility Management• All platform System Management• Backup Engineering


Post Mortem

• What Worked• Needs Help• Needs Update• Hardware• Staffing• Objectives


Nextgen

• Hosted or Local• Minor Major Catastrophic• Go Paper• Broadband cards and Hotspots.


Questions?


Contact us

Aaron KutcherSystem [email protected]

330‐430‐3962