The case for a disaster recovery strategy for component XYZ

Slides:



Advertisements
Similar presentations
1 The Basics of Business Continuity Presented by Mary F. Sandy, CBCP Business Continuity/Disaster Recovery Class DePaul University ©Mary F. Sandy, 2006.
Advertisements

Creating a Data Disaster Recovery Plan. What is a DR Plan? Is your best solution to: Continuous business services Prompt and smooth recovery Prepare for.
Reliability of the electrical service Business Continuity Management Business Impact Analysis (BIA) Critical ITC Services Minimum Business Continuity Objective.
Oregon Department of Education Business Continuity / Disaster Recovery Program Implementation Mark Tyler Nigel Crowhurst.
Maximizing Uptime and Your Firm's Bottom Line: Understanding risk and budget when evaluating business continuity & disaster recovery protocols Michael.
Module – 9 Introduction to Business continuity
Business Continuity Section 3(chapter 8) BC:ISMDR:BEIT:VIII:chap8:Madhu N PIIT1.
© 2009 EMC Corporation. All rights reserved. Introduction to Business Continuity Module 3.1.
Building a Business Case for Disaster Recovery Planning - State and Local Government Chris Turnley
1 Disk Based Disaster Recovery & Data Replication Solutions Gavin Cole Storage Consultant SEE.
Our Technology Comes with People Disaster Recovery Planning Glenn Lytle, Vice President Sales, Lumos Networks July 28,
Introduction Security is a major networking concern. 90% of the respondents to the 2004 Computer Security Institute/FBI Computer Crime and Security Survey.
Planning for Contingencies
1© Copyright 2011 EMC Corporation. All rights reserved. EMC RECOVERPOINT/ CLUSTER ENABLER FOR MICROSOFT FAILOVER CLUSTER.
Network and Systems Security Security Awareness, Risk Management, Policies and Network Architecture.
Saving Your Business from a Data Loss Randy Clark.
John Graham – STRATEGIC Information Group Steve Lamb - QAD Disaster Recovery Planning MMUG Spring 2013 March 19, 2013 Cleveland, OH 03/19/2013MMUG Cleveland.
Company Program. Disaster Recovery A Disaster Recovery Plan is a plan for business continuity in the event of a disaster that destroys part or all of.
IT Business Continuity Briefing March 3,  Incident Overview  Improving the power posture of the Primary Data Center  STAGEnet Redundancy  Telephone.
Business Continuity and Disaster Recovery Chapter 8 Part 2 Pages 914 to 945.
Human Resources Crisis Management and Contingency Management HL ONLY.
Paul M Kane Director, Issues to think about! APTLD Members’ Meeting in Kuala Lumpur 1 – 2 March 2010 Contingency Planning.
DotHill Systems Data Management Services. Page 2 Agenda Why protect your data?  Causes of data loss  Hardware data protection  DMS data protection.
Network and Systems Security Security Awareness, Risk Management, Policies and Network Architecture.
By Srosh Abdali.  Disaster recovery is the process, policies and procedures related to preparing for recovery or continuation of technology infrastructure.
IT Disaster Recovery CAUBO 2008 Information Systems and Technology.
McLean HIGHER COMPUTER NETWORKING Lesson 15 (a) Disaster Avoidance Description of disaster avoidance: use of anti-virus software use of fault tolerance.
Phases of BCP The BCP process can be divided into the following life cycle phases: Creation of a business continuity and disaster recovery policy. Business.
Chapter 16 Presented By: Stephen Lambert Disaster Recovery and Business Continuity.
Key Terms Business Continuity Plan (BCP) – A comprehensive written plan to maintain or resume business in the event of a disruption Critical Process –
The Importance of Proper Controls. 5 Network Controls Developing a secure network means developing mechanisms that reduce or eliminate the threats.
Lecture5 : Contingency planning Lecturer: Kawther Abas 25/12/ CS – Management of Programming Projects.
DISASTER RECOVERY PLAN By: Matthew Morrow. WHAT HAPPENS WHEN A DISASTER OCCURS  What happens to a business during a disaster?  What steps does a business.
Disaster Recovery Planning (DRP) DRP: The definition of business processes, their infrastructure supports and tolerances to interruptions, and formulation.
Dr. Gerry Firmansyah CID Business Continuity and Disaster Recovery Planning for IT (W-VI)
Dr. Gerry Firmansyah CID Business Continuity and Disaster Recovery Planning for IT (W-I)
Business Plan – how the business will operate and how you are going to make it succeed Objective: Explain the Nature of Business Plans.
MANAGEMENT of INFORMATION SECURITY, Fifth Edition.
Managed IT Solutions More Reliable Networks Are Our Business
Technology and Business Continuity
IT Service Transition – purpose and processes
Utilizing Your Business Continuity Plan.
Business Impact Analysis
CompTIA Security+ Study Guide (SY0-401)
Module – 9 Introduction to Business continuity
DISASTER RECOVERY INSTITUTE INTERNATIONAL
Business Continuity / Recovery
Business Continuity Plan Training
Develop and Document a Disaster Recovery Plan for the Small Enterprise
Alabede, Collura, Walden, Zimmerman
Fundamentals of a Business Impact Analysis
Audit Plan Michelangelo Collura, Folake Stella Alabede, Felice Walden, Matthew Zimmerman.
Audit Planning Presentation - Disaster Recovery Plan
Storage & Digital Asset Management CIO Council Update
Director of Database Administration with Paymetric, Inc. 
CompTIA Security+ Study Guide (SY0-501)
Software Quality Engineering
Management. Management What is a risk? A risk is simply a probability that some adverse circumstance will actually occur.
Disaster recovery.
Mark Tyler Nigel Crowhurst
Business Continuity Plan
Cyber Security in a Risk Management Framework
IT SERVICE CONTINUITY PLAN
PAYROLL DISASTER RECOVERY PLAN
DATA DISASTER RECOVERY PLAN
SaaS DISASTER RECOVERY PLAN
APPLICATION DISASTER RECOVERY RESPONSE
IT DISASTER RECOVERY PLAN
Presentation transcript:

The case for a disaster recovery strategy for component XYZ Proposal by: Feodor Georgiev, Role ..., Team ...

Content Background information on component XYZ Current disaster recovery strategy and risk to business Proposed disaster recovery strategy and benefits to business Estimated required resources for proposed changes (cost)

Background on component XYZ Name and sub-components or hosted applications: Location (if relevant) and team reponsible: Purpose/ Importance to business: Highlight what data is stored on the server and what it is worth to the business (i.e. vital for external financial reports, client billing etc) Highlight business groups using it and if this is their only source for this data Highlight the business’ key metrics or expectations (if known) regarding Recovery Point Objectives (RPO*) and Recovery Time Objective (RTO**) should a disaster occur * the maximum tolerable period in which data might be lost from an IT service due to a major incident ** the time duration and a service level within which a business process must be restored after a disaster or disruption in order to avoid unacceptable consequences *

Current disaster recovery strategy/plan and risk to business Highlight current DR strategy (if any) Highlight what the impact would be to the business should the component break down partially or completely (i.e. Could the business get the data elsewhere and with what delay and manpower? What would be the negative impact of the business – inability to do billing? Delayed reaction to market changes? Bad experience for end customers? etc)

Proposed disaster recovery strategy/plan and benefits to business Highlight proposed DR changes IT disaster recovery control measures can be classified into the following three types: Preventive measures - Controls aimed at preventing an event from occurring. Detective measures - Controls aimed at detecting or discovering unwanted events. Corrective measures - Controls aimed at correcting or restoring the system after a disaster or an event. Highlight what the benefits would be to the business with the new changes to the DR strategy should the server break down partially or completely

Estimated required resources for proposed changes (cost) Hardware: Software: Estimated duration: IT staff required: Impact on business (if any downtime etc): Impact on IT staff workload (if any, which team): etc