Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Businesscontinuityanddisasterrecoverynotes 090729030541-phpapp02


Published on

Published in: Business
  • Be the first to comment

  • Be the first to like this

Businesscontinuityanddisasterrecoverynotes 090729030541-phpapp02

  1. 1. Business Continuity andDisaster Recovery NotesAlan McSweeney
  2. 2. Objectives• To provide outline options for implementing business continuity and disaster recovery• To outline possible solution architectures• To demonstrate experience and competence in business continuity• To identify possible next steps March 18, 2013 2
  3. 3. Agenda• Understanding of Requirements• Business Continuity and Disaster Recovery Information• Business Continuity and Disaster Recovery Options and Technologies• Server Virtualisation and Business Continuity and Disaster Recovery• Implementation Notes March 18, 2013 3
  4. 4. Overall Solution Requirements• Resilience − Reliable underlying hardware and software components• Scalable − Infrastructure that can grow to meet future requirements without significant engineering• Business Continuity and Disaster Recovery − Solution that provides disaster recovery and business continuity• Manageable − Solution that is easily manageable• Secure• Return on Investment• Simplicity − Few components and vendors to reduce complexity and risk• Risk − Solution must incorporate proven technologies March 18, 2013 4
  5. 5. Protecting the Business March 18, 2013 5
  6. 6. Round Up the Usual Statistics• 80% of businesses have no plan − “It won’t happen to me”• 68% of businesses who experience a disaster and don’t have a plan go out of business within 2 years• One in five organisations will suffer a major IT disaster in five years• A company experiencing a computer outage lasting longer than 10 days will never fully recover March 18, 2013 6
  7. 7. Round Up the Usual Statistics• The loss of IT capacity and telecommunications is seen as the worst disruption scenarios for organisations − 48% of managers surveyed admit that their businesses have experienced one or more interruptions within the past year − 57% of business disasters are IT-related• About half of small and medium-sized firms now do perform some sort of data backup, but not always adequately − Large numbers of businesses would be unable to recover business data after a server crash or disaster• It takes 19 days and costs in excess of €14,000 to re-enter just 20 MB worth of sales and marketing data − Retrieving accounting records is even worse; they require over 21 days of work and cost over €15,700 to re-type• 93% of businesses say that data storage is an extremely important part of their organisation but only 20% of those surveyed said that there was a high level of understanding of storage and storage issues within their companies March 18, 2013 7
  8. 8. Reasons for Data Loss Human Error 30% Hardware Failure 42% Hardware Destruction 3% Software Corruption Theft 13% PC Viruses 5% 7% March 18, 2013 8
  9. 9. US Cost of Downtime Survey• 46% said each hour of downtime would cost their companies up to $50k• 28% said each hour would cost between $51K and $250K• 18% said each hour would cost between $251K and $1 million• 8% said it would cost their companies more than $1million per hour March 18, 2013 9
  10. 10. Survival Risk• At what point is the survival of your company at risk? − 40% said 72 hours − 21% said 48 hours − 15% said 24 hours − 8% said 8 hours 9% said 4 hours − 3% said 1 hour − 4% said within the hour March 18, 2013 10
  11. 11. Affects of Outage• Lost revenue and business interruption• Possible litigation• Lost competitiveness and lost business• Loss of company reputation• Financial cost March 18, 2013 11
  12. 12. Specific Business Continuity and Disaster RecoveryRequirements• RTO – Recovery Time Objective − How quickly should critical services be restored• RPO – Recovery Point Objective − From what point before system loss should data be available• How much data loss can be accommodated RPO (Recovery Point RTO (Recovery Time Objective) – Time Since Last Objective) – Time to Recover Good Backup System Loss/Failure Last System Backup/Copy System Restored Overall Recovery Time – From Last Backup to System March 18, 2013 Recovery 12
  13. 13. Components of Effective Business Continuity and DisasterRecovery Operational Business Disaster Continuity and Recovery Disaster And Business Recovery Continuity Facility Plan Business Primary Continuity and Infrastructure Disaster Designed for Recovery Resilience and Processes And Recoverability Procedures March 18, 2013 13
  14. 14. Components of Effective Business Continuity and DisasterRecovery• An operational Business Continuity/Disaster Recovery facility consists of four key components: 1. Facilities and Infrastructure – the underlying IT infrastructure and data must be structured to be resilient and recoverable 2. Processes and Procedures – Business Continuity/Disaster Recovery must be incorporated into standard processes and procedures 3. O perational Business Continuity/Disaster Recovery Plan – there must be an operational and tested plan to recover 4. Business Continuity and Disaster Recovery Facility – there should be a facility from which the recovered systems can run March 18, 2013 14
  15. 15. Stages for Implementing Business Continuity and DisasterRecovery Business Continuity and Disaster Recovery Resilience and Fault Tolerance Data Backup and Recovery March 18, 2013 15
  16. 16. Possible Core Architecture (Virtualised) 1. Core server infrastructure virtualised for resilience and fault tolerance 2. Centralised server management and backup 3. SAN for primary data storage 4. Backup to disk for speed 5. Tape backup 6. Two-way data replication March 18, 2013 16
  17. 17. Resilience • Virtual infrastructure in HA (High Availability) Cluster • Fault tolerant primary infrastructure • Failing virtual servers automatically restarted • Dynamic reallocation of resources • Reduces need to invoke business continuity plan March 18, 2013 17
  18. 18. Business Continuity and Disaster Recovery • Failing servers can be recovered on other site • Virtualised infrastructure will allow critical servers to run without the need for physical servers • Virtualisation makes recovery easier – removes any hardware dependencies March 18, 2013 18
  19. 19. Business Continuity and Disaster Recovery Considerations• Understand what you are protecting against − Hardware failure or damage − Application and data corruption − Site failure or denial of access − Fires, chemical spillages, sickness/epidemic• Define level(s) of service to be provided• Define recovery method(s)• Understand system and application landscape• Understand business requirements and align information technology infrastructure to meet them• Define cost and benefits of implementing levels of resilience and recoverability March 18, 2013 19
  20. 20. Sample Highly Resilient Infrastructure March 18, 2013 20
  21. 21. Data Replication Options• Option 1 – Direct server replication − Each server replicates to a backup server in the other site• Option 2 – Consolidated virtual server backup and replication of server images for recovery − Copies of virtual servers replicated to other site for recovery• Option 3 – Data replication − Replication of SAN data to other site• Option 4 – Backup data replication − Replication of backup data to other site• Each option has advantages and disadvantages March 18, 2013 21
  22. 22. WAN Optimised Accelerated Offsite Backup and Replication forBusiness Continuity and Disaster Recovery Tape Storage Tape Filers Backup Backup WAN SECONDARY DATA PRIMARY DATA CENTRE CENTRE File Servers Mail Servers Filers File Mail Web Servers Servers Servers Transparent WAN Optimisation Unit• LAN-like performance of file sharing from anywhere• Cut backup times by 75% or more• Use 90% less WAN bandwidth in the process• Allows use of lower speed links to saving ongoing costs – for example, 2 Mbps becomes 20 Mbps at least March 18, 2013 22
  23. 23. Server Virtualisation and Disaster Recovery• Server virtualisation assists recovery from disaster − Enables easier testing − Enables successful recovery − Simplifies recovery − Reduces costs of recovery infrastructure − Enables business continuity• Changing disaster recovery requirements − Higher standards are required − More reliability is expected − Faster pace of business generates more critical change − Intense competitive environment requires high service levels March 18, 2013 23
  24. 24. Virtualised Solution RPO and RTO• Low RTO and RPO for immediate recovery• Solution can grow to support additional servers easily and quickly Systems Available Immediately RTO 2 RPO 3 1 Last System System Loss Replica March 18, 2013 24
  25. 25. Business Continuity and Disaster Recovery ImplementationApproach• The System Dynamics approach to implementing effective Business Continuity consists of two phases: 1. Solution Design – your Business Continuity/Disaster Recovery requirements are identified and documented and a solution and an implementation plan are developed 2. Solution Implementation – the previously defined and agreed solution is implemented Solution Solution Implementation Design Business Solution Requirements Implementation Project Risk Design Solution and Plan Testing Initiation Assessment and Implementation Impact Roadmap Documentation Analysis March 18, 2013 25
  26. 26. Maintaining Business Continuity and Disaster Recovery• Once implemented, effective ICT business continuity must Exercise, Test and ICT be regarded as a continuous Maintain ICT Business Continuity process Business Continuity Project Plan• While this imposes an overhead it ensures that business continuity Embed ICT Understand the Critical implementation will continue Business Continuity Systems and Applications to meet the requirements of into ICT the business and meet audit compliance requirements• Good solution design will Develop ICT Develop Strategy minimise maintenance effort Business Continuity for ICT Business as continuity is embedded Plans and Processes Continuity March 18, 2013 26
  27. 27. View of Business Continuity and Disaster Recovery• Vendor independence• Aware of all solution options• Aware of enabling technologies − Server virtualisation − Hardware and software replication − WAN optimisation• Can design the best and most cost-effective possible solution Suits the needs of the organisation rather than the vendor − Assist in vendor selection and negotiation• Focus on entire solution March 18, 2013 27
  28. 28. Structured Approach to Business Continuity and Disaster Recovery Analysisand Design ICT Business Continuity Planning Phase 5 – Draft and Phase 1 – Project Phase 2 – ICT Phase 3 –ICT Phase 4 – Final Report Initialisation and Infrastructure and Business Continuity Information Production and Mobilisation Application Analysis O ptions Consolidation Presentation Analyse and Define and Consolidate Analysis Document ICT Document ICT Draft Report Agree Project Scope and Design Infrastructure and Recovery Presentation Information Applications Requirements Collect Server and Define Business Application Define and Agree Project Continuity Final Report Inventory and Document Recovery Timescales O perations and Presentation Resource Usage Scenarios Architectures Information Produce Financial Business Critical Document Business Agree Project Analysis and Application Owner Continuity Handover Deliverables Implementation Meetings Operation Plans for Options Agree Business Define Application Owner Meeting Recovery Schedule Requirements Define Detailed Agree Project Business Critical Communication Recovery Processes March 18, 2013 28
  29. 29. Structured Approach to Business Continuity and Disaster Recovery Analysisand Design• Structured approach − Phase 1 – Project Initialisation and Mobilisation − Phase 2 – ICT Infrastructure and Application Analysis − Phase 3 – ICT Business Continuity Options − Phase 4 – Information Consolidation − Phase 5 – Draft and Final Report Production and Presentation• Focus is to develop a practical, realistic and cost- effective business continuity plan and to identify pre- requisite and associated work in order to make business continuity more effective• Detailed workplan that will address all areas March 18, 2013 29
  30. 30. What Can be Done• Identify, define and document business continuity and disaster recovery requirements• Design business continuity and disaster recovery solution options• Select the most appropriate solution, technologies and vendors• Assist with development business continuity plan• Assist with and manage implementation• Define total business continuity solution encompassing offerings from various vendors March 18, 2013 30
  31. 31. Benefits of Structured Approach• Practical and results-focussed approach• Detailed knowledge of business continuity implementation• Knowledge and experience of relevant technologies• Complete set of relevant skilled personnel in the area required• Vendor independence and knowledge of likely products and vendors March 18, 2013 31
  32. 32. More Information Alan McSweeney March 18, 2013 32