HIGH AVAILABILITY DISASTER RECOVERY & AAS Presented by Bill Decker September 16, 2009 - PowerPoint PPT Presentation

farsiris
high availability disaster recovery aas presented by bill decker september 16 2009 l.
Skip this Video
Loading SlideShow in 5 Seconds..
HIGH AVAILABILITY DISASTER RECOVERY & AAS Presented by Bill Decker September 16, 2009 PowerPoint Presentation
Download Presentation
HIGH AVAILABILITY DISASTER RECOVERY & AAS Presented by Bill Decker September 16, 2009

play fullscreen
1 / 14
Download Presentation
HIGH AVAILABILITY DISASTER RECOVERY & AAS Presented by Bill Decker September 16, 2009
0 Views
Download Presentation

HIGH AVAILABILITY DISASTER RECOVERY & AAS Presented by Bill Decker September 16, 2009

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. HIGH AVAILABILITYDISASTER RECOVERY&AASPresented byBill DeckerSeptember 16, 2009

  2. High Availability & Disaster Recovery Services Team • Bill Decker Senior Manager • John Snider Manager • Christopher Kane Lead Analyst • Nancy Fulton Senior Analyst • Tatyana Tsuprun Senior Analyst

  3. Definitions Availability is concerned with sustaining operations Disaster recovery is concerned with the restoration of operations after unplanned interruptions

  4. Common Elements Risk reduction Recovery target expectations. Rapid recovery to Fault avoidance Recovery Time Objectives (RTO) Recovery Point Objectives (RPO) Process improvement Identify gaps in infrastructure Formal documentation

  5. Common Business Classification Requirements Need to categorize our business processes in terms of business impact. Tier I: Critical (production) Tier II Important (non-critical production) Tier III Necessary (non-essential)

  6. Availability Continuum Tier I: Critical (production) Tier II: Important (non-critical production) Tier III: Necessary (non-essential) Unavailable Unavailable Available Highly Available Service Interruption! AAS Planning: Business Impact Analysis Analysis & Design: Rapid Recovery to Fault Avoidance Analysis & Design DR perspective – RTO/RPO

  7. Business Classification Requirements Need to categorize our business processes in terms of business impact for Disaster Recovery Tier I: Critical (production) Tier II Important (non-critical production) Tier III Necessary (non-essential)

  8. DR Recovery Time Requirements

  9. DR Recovery Strategy Overview

  10. AAS & OIA Working Together (SDLC Touch Points) Hardware additions, Removal or changes Software additions or License changes New Projects as defined by PPM System to System Integration Production Support Modifications

  11. Appendix Tier definitions

  12. Application Recovery Classification (Tier 1) • Tier 1 Critical aka Critical Production • Applications that are essential to the ability of the University to provide its services or perform its activities safely & effectively • Safety & Security: application is needed to support a safe and secure environment, physically and/or technologically • Learning, Education & Research: application is needed to carry out or directly support the academic mission of the University • Business Support Services: application allows the University to maintain necessary business operations, safeguard assets and ensure financial viability of the University • Public visibility outside of the University if high • Application generates revenue • May be co-dependent upon other tier 1 applications

  13. Application Recovery Classification (Tier 2) • Tier 2 Important aka non-critical production • Applications that, while not critical, significantly support the ability of the University to provide its services or perform its activities. • Application is heavily used for day-to-day operations but is not “critical” • Application may be dependent on a tier 1 application • Application provides a service to a tier 1 application

  14. Application Recovery Classification (Tier 3) • Tier 3 Non-essential • Applications that are nice to have but can wait for recovery of all critical and important applications • Application operates independent of other applications (no dependencies) • Application test or development environments