DISASTER AVOIDANCE, BETTER THAN DISASTER RECOVERY #ILTA179

Transcription

1 DISASTER AVOIDANCE, BETTER THAN DISASTER RECOVERY #ILTA179

2 A PROBLEM STATEMENT AND SOME TERMINOLOGY

3 RISK MANAGEMENT Disaster Recovery and Business Continuity are subsets of the business process of Risk Management. In this session, we will discuss a number of availability features. It is important to note that the availability features selected in a design should be chosen to mitigate risk based on the BIA (Business Impact Analysis) performed for those services.

4 A BRIEF HISTORY ON APPLICATIONS Platform 1 (Mainframe) Platform 1 (Mainframe) Platform 1.5 (Peer-Peer) Platform 2 (Client-Server) Platform 2 (Client-Server) Platform 2.5 (Client-Server with Enhancements) Platform 3 (Distributed) Platform 3 (Distributed)

5 TERMINOLOGY Fault Tolerance- The ability of an IT service or component to operate correctly when another related part has failed High Availability A design of the IT service that minimizes or hides the effects of IT component failures to the users of a service Continuous Operation- An approach to eliminate planned downtime of an IT service. (Individual components may be down but the IT service remains available) Continuous Availability- An approach or design to achieve 100% availability

6 Terminology RPO- Recovery Point Objective- The maximum acceptable amount of data loss measured in time. RTO- Recovery Time Objective- The maximum acceptable length of time to bring the system back online. WRT- Work recovery time- The maximum acceptable length of time that is needed to verify the system and/or data integrity MTD- Maximum Tolerable Downtime- The Sum of RTO and WRT

7 Challenges with Protecting Legacy Applications Limited or No Native Application High Availability Limited or No Native Application Fault Tolerance No Native Application functionality to support Continuous Operations No Native Application functionality to support Continuous Availability

8 TECHNOLOGIES AND SOLUTIONS FOR DISASTER AVOIDANCE

9 Infrastructure technologies to shim applications Continuous Availability: vmsc*, vsphere FT**, ADCs/Load Balancers Continuous Operations: vmotion, Storage vmotion, OTV/LISP, VXLAN, NVGRE, vmsc*, ADCs/Load Balancers, Live Volume High Availability: vsphere HA, SQL Clustering Fault Tolerance: Redundant components

10 SQL Clustering SQL 2008 SQL 2012

11 Exchange Database Availability Groups

12 Exchange Database Availability Groups with Automatic Failover

13 ALL OF YOUR APPLICATIONS ARE ONLINE, BUT CAN YOUR USERS ACCESS THEM?

14 Networking is a Requirement for Workload Mobility Physical Layer 2 connectivity OTV VXLAN STT NVGRE L2TP GRE Other Encapsulation protocol

15 SOME PITFALLS OF DISASTER AVOIDANCE The performance impacts of Synchronous replication Rapid point-in-time recovery is still critical for logical corruption, accidental or intentional mass deletion/modification, etc. Understand how a solution actually works and aligns with your requirements. Don t just believe marketing hype.

16 VMSC (PICK A VENDOR) Does anyone know why vmsc with a zero RTO requirement cannot simultaneously meet a zero RPO requirement? Which is more important to you, data integrity or data availability?

17 SQL ALWAYS-ON (AVAILABILITY GROUPS) Availability Groups have functions that behave differently from a traditional SQL cluster Beware that locking may not work the way that you think it will

18 EXCHANGE DAGS Lack sufficient protection against logical corruption. LAGs are supposed to perform this function, but there are challenges Split-brain issues with automatic site failover. Lossless failover (Lower RPO- Higher RTO vs Good availability (Lower RTO- Higher RPO)

19 FUTURE TECHNOLOGIES THAT WILL HAVE A MAJOR IMPACT ON DISASTER AVOIDANCE SDN Hyperconverged Infrastructure

20 ITIL AND LEAN SIX SIGMA RELATIONSHIP Disaster Avoidance strategies should be used in order to meet ITIL OLAs, which in turn support SLAs. Disaster Avoidance strategies should not be used in cases where they do not add business value. The exception to this is if they are cost neutral or their solutions provide other items that add offsetting business value. In general, if a disaster avoidance strategy is not needed to meet OLAs it will not add business value.

21 FINAL THOUGHTS Is your DR/BC plan aligned to your business needs? Your DR/BC plan should ensure you meet the needs of your BIA without incurring unnecessary expense Is your DR/BC plan valid? A successful test should show your ability to solve for the availability needs defined by your BIA Is your DR/BC plan complete? The business cares about functional access to applications. This means 3 key things to the users: Is the application available? (Data, Servers, Application) Is the application accessible? (Network, Security) Does the application perform in a way that allows the user to perform their job functions? (Performance, Application support, Functional testing) Is your DR/BC plan tested? If you don t test, you will find out what doesn t work in a real disaster.

22 QUESTIONS? #ILTA179