IBM Resiliency Services Convergence of High Availability & Disaster Recovery

Transcription

1 Convergence of High Availability & Disaster Recovery March 2015 Introductions Chuck Hinkle IBM GDPS Offering Executive Troy Jassey Delivery Leader 2

2 Cross Industry Resilience Trends Business requirements: As more client-facing applications and methods to access those applications are developed, the demand for higher levels of availability is increasing ( e.g. mobility applications, web presence ) Consolidation of localized services from regional to national services has driven an enterprise view of HA/DR Continuing trend to more and more regulation, driving more stringent IT and HA requirements Complex application chains supporting business processes Objectives and measurements: Enterprises are beginning to measure service availability from the users' perspective Trend to measuring on a 24x7 basis, to include both planned and unplanned outages More robust DR exercises that are increasingly pass/fail Technology and architecture: Reliability of the technology continues to improve, but exception handling skills are decreasing Large Application implementations and availability concerns move to three site solutions that blurs the line between HA and DR Integrated, risk aligned business resilience Convergence of HA and DR solutions Granular application level failover capability Virtualized recovery environments Increased failover/failback capability Increased leverage of DR assets Increased change rate exacerbates weak prod/dr linkages 3 Terminology Level Set 4

3 Converged vs. Diverse HA/DR Overview Characteristics Converged Uses in-region facilities for both HA/DR requirements Uses similar/same infrastructure, replication, processes, support Traditional Active/Active with synchronous replication Internal owned/run solutions Diverse Uses out of region DR Asynchronous unlimited distances Uses different infrastructure, replication, processes, support Emerging Active/Standby or Active/Query with asynchronous application-based replication Internal or external owned/run Pros Aggressive RTO/RPO capability Reduce/eliminate costs for out of region DR Provides fault-tolerant capabilities Provides in-region DR capabilities Region-switch capability Risk aligned RTO/RPO capability Lower costs for traditional asynchronous Provides out of region capability Less potential production impact Cons No out of region DR capability Increased risk of production impact with testing Bundles less critical applications in more expensive solutions Local HA / fault tolerant technologies not possible Region switch more problematic Potential HA audit / regulation issues Asynchronous data loss 5 Taking a Holistic Approach Data Mirror Approach Business Continuity as a comprehensive business recovery solution Determine the optimum Architecture Blend and balance the seven necessary components into a cost-effective solution: Server Management Automation Network management and Physical Infrastructure Data replication management Server management Workload management Automation Network management Education and Services Scalable Skilled People, Solution Design and Implementation 6

4 What are Companies Doing Today? (1 of 4) High Availability Synchronous SITE 1 Site is a logical term Distance apart is typically < 200Km Synchronous Link Can achieve zero RPO Fault-tolerant technologies HA & DR Convergence SITE 2 7 What are Companies Doing Today? (2 of 4) Disaster Recovery Asynchronous SITE 1 Site is a physical term Distance apart is virtually unlimited Can achieve seconds RPO Failure/restart technologies 8 SITE 2

5 What are Companies Doing Today? (3 of 4) High Availability & Disaster Recovery SITE 1 Site is a logical term Distance apart is typically < 200Km Can achieve zero RPO Fault tolerant technologies SITE 2 Synchronous Link (multi-target option) HA & DR Convergence (cascading option) 9 Physical term Unlimited distance SITE 3 RPO Seconds Failure/Restart What are Companies Doing Today? (4 of 4) HA & DR with DR Fault Tolerance SITE 1 Site is a logical term Distance apart is typically < 200Km Can achieve zero RPO Fault tolerant technologies SITE 2 Synchronous Link HA & DR Convergence (multi-target option) (cascading option) 10 SITE 4 Synchronous Link SITE 3

6 CASE STUDY Overview Requirements Challenges Solution Tier 1 Financial Institution Issues: Multiple large I/T complexes with disparate recovery architectures Missing HA & DR SLA s mandated by regulators I/T budget overruns Years of acquisitions resulted in multiple disparate I/T environments, each with differing point solutions for addressing application and infrastructure high availability and disaster recovery requirements. 11 CASE STUDY Overview Requirements Challenges Solution Tier 1 Financial Institution Business Requirements: Higher availability for mission-critical workloads Self services (ATM s) Internet Banking Applications outages needed to be virtually eliminated Quarterly application version upgrades needed to be transparent 12

7 CASE STUDY Overview Requirements Challenges Solution Tier 1 Financial Institution Technical Issues: Major quarterly application upgrades required 3 to 4 hour outages Were scheduled for 3 rd shifts on weekends to minimize impact Still affected customers working from world-wide locations Thousands of application upgrades and database changes All business stopped Required manual coordination across geographic locations to block and then resume routing of connections into the data center Reload of databases elongated outage period Goal was to: Reduce planned outages to these applications down to minutes Enhance overall resiliency of entire operating environment 13 CASE STUDY Overview Requirements Challenges Solution Tier 1 Financial Institution Solution: Instituted I/T-wide Resilience Program Management Business impact of application outages quantified: Business impact analysis identified critical processes and associated costs Hardening of bare metal I/T infrastructure: Synchronously replicate data for zero RPO Asynchronously replicate data for out-of-region DR protection Focus on automation to drive down dependency on people and reduce RTO Enhance critical applications to operate in Active/Active mode: Implement multiple instances of critical applications between primary and outof-region recovery sites In full production achieving: Site-wide out-of-region DR capability within 4 hours with seconds of data loss Local high availability with zero RPO Application maintenance windows reduced from hours to minutes 14

8 Decision Considerations Does the enterprise have a reasonable risk of region wide disaster? Out of region DR is always recommended, and becomes more critical in areas prone to region wide issues (hurricanes, earthquakes) Are RTOs/RPOs very aggressive and are fault tolerant technologies required? Look at how critical applications outage impacts dictate HA coverage, and how much of the environment fits into this category to balance cost/capability Are there industry driven requirements for minimum site separation? Emerging audit and governmental regulations are driving certain industry requirements for minimum site separation Is the company mature in data management & operational processes? Converged infrastructures can be more complex, introducing fault-tolerant technologies that require technically mature infrastructures 15