1 / 19

Ground Rules & Expectations

Ground Rules & Expectations. House Keeping! All teleconference lines are open... Mute yourself when not speaking and don’t put call on ‘hold’. Collaborate! This is a discussion, not a presentation… Ask questions, make comments and share experiences. And beware, Forrester may call on you!

royrobert
Download Presentation

Ground Rules & Expectations

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Ground Rules & Expectations • House Keeping! • All teleconference lines are open... • Mute yourself when not speaking and don’t put call on ‘hold’. • Collaborate! • This is a discussion, not a presentation… • Ask questions, make comments and share experiences. • And beware, Forrester may call on you! • Are we in a ‘rabbit hole’? • If the conversation has gone down a substantial ‘rabbit hole’… • … Forrester will interject, but you decide whether or not to persist.

  2. Agenda • Understanding disaster recovery and availability • Measuring availability • Availability strategies • Recommendations

  3. Definition: disaster recovery (DR) Focuses on recovery procedures of critical IT systems following a significant disaster event or disruption that renders the primary site unavailable

  4. Definition: high availability (HA) Focuses on the technology and processes to prevent application/service outages at the primary site or in a specific IT system domain

  5. HA and DR requirements

  6. Definition: continuous availability Combines DR preparedness and high availability strategies to ensure IT service availability whether there is a system or site failure

  7. Sources of service outages Apps Unplanned downtime Planned downtime Hardware upgrades (servers, storage, networks etc.) Data integrity (data corruption, bugs) Data center/facilities failures (extreme weather, power outages, manmade events.) Software upgrades(OS, DB, app) Maintenance (backups, patches) Hardware failures(servers, storage, networks etc.) Process failures (human error, coding errors) Data migrations

  8. Agenda • Understanding disaster recovery and availability • Measuring availability • Availability strategies • Recommendations

  9. Availability focuses on service, not elements • Availability is the aggregation of all elements supporting the IT service. • Most components spec to 99.999% availability • Combined IT service availability would fall below 99.999% • Scheduled downtime is a critical part of the availability design Most downtime is planned!

  10. Availability is more than just “9”s • “9”s are misleading • Consider 99.9% availability (8 hours/year outage for 24x7), What is the difference between: • 8 AM to 4 PM on the last Friday of the quarter • Biweekly outages of 30 min at 4 AM local time • Timing and duration are more important than total downtime • Well written SLAs must take allthese factors into account

  11. Availability metrics • ITIL availability management • Availability of IT services compared to agreed upon SLAs • Duration of disruptions to IT services • Number of disruptions to IT services • Number of infrastructurecomponents with availabilitymonitoring • Number implementedmeasures to improveavailability

  12. Agenda • Understanding disaster recovery and availability • Measuring availability • Availability strategies • Recommendations

  13. Local HA options Seconds FT hardware FT VMs Clustering Local standby Restart VMs Recovery time objective (RTO) Minutes System backup and restore Hours Less More Cost

  14. IT service continuity (DR) options

  15. Agenda • Understanding disaster recovery and availability • Measuring availability • Availability strategies • Recommendations

  16. Recommendations • Downtime isn’t just the result of disasters • Make availability a part of every enterprise architecture, app development and IT infrastructure decision • The most seamless form of continuous availability is baked into the application • Preventing failures by architecture/design is cheaper than providing recovery for poorly designed applications

  17. Recommendations (cont.) • Design applications for availability • Use reliable elements — server, storage, OS, etc. • Select HA and DR options for critical systems • Scrutinize operational process to reduce human error • Make availability a key component of acceptance testing

  18. Thank You! Megan O'Donoghue Forrester Research, Inc. +1 617/613-6059 modonoghue@forrester.com Stephanie Balaouras Forrester Research, Inc. +1 617.613.6440 sbalaouras@forrester.com Karen Popeo Forrester Research, Inc. +1 617/613-6381 kpopeo@forrester.com Scott Sheehy Forrester Research, Inc. +1 617/613-6523 ssheehy@forrester.com

More Related