Replication for Business Continuity, Disaster Recovery and High Availability


Published on

A review of Replication technologies that can be used for HA, BC and DR.

  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Replication for Business Continuity, Disaster Recovery and High Availability

  1. 1. Replication for Business Continuity,Disaster Recovery and High AvailabilityTony Pearson – IBM Master Inventor and Senior Managing ConsultantMarch 2013 © 2013 IBM Corporation
  2. 2. Everyone Knows: Downtime is Bad! Lost brand equity Loss of goodwill and trust Lost loyalty Lost revenue and market share Lost productivity Causes:2 © 2013 IBM Corporation
  3. 3. 2013: continued Metcalf’s Law: Value of network acceleration of changes increases proportional to square in today’s business world…. of # people on it 5 5 Trust Cross-Industry Value Coalition 4 4 Industry-Centric Value Web 3 3 Extended Value Core Business Chain 2 2 Subsidiary/JV Select ‘Trusted Customer Partners’ 1 1 Partner/Channel Isolated Operations Supplier/Outsourcer Collaboration| 3 3 © 2013 IBM Corporation
  4. 4. The “Business Process” is the Unit of RecoveryBusiness Business Business Business Business Business Business Business process A process B process C process D process E process F process G 3. The loss of both db2Application Application 2 applications affects two http://xyz.xml Web distinctly different Sphere business processes MQseries 2. The error impacts management Application 3 Analytics Application 1 the ability of two or report reports decision more applications to SQL point share critical dataInfrastructure IT Business Continuity 1. An error occurs on a storage device that must recover at the correspondingly corrupts a database business process level 4 © 2013 IBM Corporation
  5. 5. Overlap of valid data protection techniques IT Data Protection 1. High Availability 2. Continuous Operations 3. Disaster Recovery Fault-tolerant, failure-resistant Non-disruptive backups and Protection against unplanned streamlined infrastructure system maintenance coupled with outages such as disasters with affordable cost continuous availability of through reliable, predictable foundation applications recovery Protection of critical Business data Operations continue after a disaster Recovery is predictable and reliable Costs are predictable and manageable5 © 2013 IBM Corporation
  6. 6. Timeline of a Disaster Recovery Recovery Point Objective (RPO). Recovery How much data Time must be recreated? Site Execute hardware, O/S, RPO Assess data integrity recovery Telecom Network Data Management Control Physical Facilities Operating System Outage Production ☺ Operations Staff Network Staff Applications Staff Applications Recovery Time Objective (RTO) Software transaction RPO of hardware data integrity integrity recovery Δ Data Recovery Time Objective (RTO) of transaction integrity Now were done!6 © 2013 IBM Corporation
  7. 7. Technology drives the Recover Point Objective (RPO) For example: Wks Days Hrs Mins Secs Secs Mins Hrs Days Wks Recovery Point Recovery Time Tape Backup Periodic Replication Asynchronous replication Synchronous replication / HA7 © 2013 IBM Corporation
  8. 8. Automation drives Recovery Time Objective (RTO) For example: Wks Days Hrs Mins Secs Secs Mins Hrs Days Wks Recovery Point Recovery Time End to end automated Storage Recovery Time includes: clustering automation Manual Tape Restore – Fault detection – Recovering data – Bringing applications back online – Network access8 © 2013 IBM Corporation
  9. 9. Business Continuity Tiers Balancing recovery time objective with cost / value Recovery from a disk image Recovery from tape copy BC Tier 7 –Server or Storage replication with end-to-end automated server recoveryCost / Value BC Tier 6 –real-time continuous data replication, server or storage BC Tier 5 –Application/database integration to Backup/Restore BC Tier 4 –Point in Time replication to Backup/Restore BC Tier 3 – VTL, Data De-Dup, Remote vault BC Tier 2 – Tape libraries + Automation BC Tier 1 – Restore 15 Min. 1-4 Hr.. 4 -8 Hr.. 8-12 Hr.. 12-16 Hr.. 24 Hr.. Days from Tape Recovery Time Objective (guidelines only)9 © 2013 IBM Corporation
  10. 10. Ideal World for High Availability and Business Continuity (HA/BC)Business processes drive strategies and they are integral to the Continuity of Business Operations. A company cannot beresilient without having strategies for alternate workspace, staff members, call centers and communications channels.Business Prioritization Integration into IT Manage Awareness, Regular Validation, Change Management, Quarterly Management Briefings Resilience Program t d e Management en e at m rr ility im y Ti RTO/RPO Cu ab t p Es ver Ca co business Re risk program Program Strategy program impact Implement assessment assessment Design Design validation analysis of itie s cts • Maturity 1. People bil pa age High Availability a crisis team er ts Im ut Model design 2. Processes uln rea O • Measure 3. Plans ,V h business ks nd T ROI High Availability Ris a resumption Servers 4. Strategies • Roadmap 5. Networks for disaster Storage, Data 6. Platforms Program recovery Replication 7. Facilities high Database and availability Software design Source: IBM STG, IBM Global Services 10 © 2013 IBM Corporation
  11. 11. Data Strategy Defined The role of the basic “Data Strategy” for HA/BC purposes Define major data types “good enough” – i.e. by major application, by business line…. – An ongoing journey Business Strategies You have to For each data type: know your data IT Strategy – Usage – Performance and measurement – Security Data Strategy Data Strategy – Availability – Criticality – Organizational role Enterprise IT Architecture – Who manages – What standards for this data And have a • What type storage deployed on basic strategy • What database • What virtualization for it Be pragmatic IT Infrastructure – Create a basic, “good enough” data strategy for HA/BC purposes People Data Acquire tools that help you know your data Process Technology Structure11 © 2013 IBM Corporation
  12. 12. A basic data strategy tells you how to categorize your data - looks something like this (step by step): Mission Critical Mission – critical data – Mission-critical data that is the highest priority dtaa – Priority = uptime, with high value justification Subset of data that is either mission-critical or supports mission critical – Data that supports business lines – Balanced priorities = Uptime and cost/value Knowledge of user and application data – All data, whether active or not…. – Which eventually needs to be archived, retained – Priority = costLower Virtualized Not easy to know and categorize your data -cost Storage But is the only foundation possible 12 © 2013 IBM Corporation
  13. 13. Then, your basic data strategy allows you to scope your HA/BC – something like this: Mission Critical Continuous Availability (CA) – Finally, create the mission-critical subset with highest level of recovery – RTO = near continuous, RPO = small as possible (Tier 7) – Priority = uptime, with high value justification Rapid Data Recovery (RDR) – Then create separate storage pools as required – RTO = minutes, to (approx. range): 2 to 6 hours – BC Tiers 4, 5 and 6 – Balanced priorities = Uptime and cost/value Backup/Restore (B/R) – Virtualize, optimize cost, lay recovery capability foundation – Provide universal 24 hour - 12 hour (approx) recovery capability – Address requirements for archival, compliance, green energy – Priority = costLower Virtualized Not easy to and categorize your data - data - Know know and categorize yourcost Storage This is where only foundation possible But is the virtualization is the enabler 13 © 2013 IBM Corporation
  14. 14. Rule of Thumb for continuous replication bandwidth Rule of Thumb: – Every 1 TB of mirrored disk storage generates about this much MB/sec of writes: OLTP – 1-2 MB/sec of write bandwidth Sequential/batch – 6-7 MB/sec of write bandwidth Expect minimum 2.5x this to handle peaks Expect normal data compression to be about 2:1 Example - you have 10 TB of disk to mirror: – OLTP: 10-20 MB/sec ROT: – Batch/sequential: 60-70 MB/sec one OC3 line = 15 MB/sec raw Effective transfer rate14 © 2013 IBM Corporation
  15. 15. Short distance synchronous mirroring: 2 site Short distance may not meet DR requirements Ability to utilize server capacity in both sites for single instance of application data Potential/ability for non-disruptive failover S P Additional copy of data might F be provided for testing or testing may be done by Hardware solution gives data regular switch of sites consistency between multiple servers/applications and single management point15 © 2013 IBM Corporation
  16. 16. Long Distance Mirroring: 2 site Longer distance to meet regulatory requirements and protect against regional events Ability to utilize server capacity in both sites for applications with Disruptive failover and less separate/independent potential to use DR data solution for continuous availability 1 0 P 0 0 0 S F 1 0 F S P Additional copy of Asynchronous replication data more likely to be more likely due to provided for testing performance requirements16 © 2013 IBM Corporation
  17. 17. Sync versus Async Server I/O Server I/O 1 1 2 3 4 2 P S P S 4 3 Metro Mirror Global Mirror Asynchronous (any distance) Synchronous <300 km •Write to primary volume•Write to primary volume •The primary site acknowledges to the host application•The primary site initiates an I/O to the secondary site to that the write is complete transfer the data Some later time:•Secondary indicates to the primary that the write is •The primary site initiates an I/O to the secondary site to complete transfer the data•Primary acknowledges to the host application that the •Secondary indicates to the primary that the write is write is complete complete•Round-trip latency added to each Write I/O •Primary and secondary bitmap updated that data is in sync17 © 2013 IBM Corporation
  18. 18. 3-Site Configurations Campus Local-1, Local-2 Local-1 Local-1 Remote-2 Bunker-2 Remote-3 Remote-3 Remote-318 © 2013 IBM Corporation
  19. 19. Tivoli Storage Manager an integrated, end-to-end data protection and unified recovery management solution •DR Operations•Mobile Offices •Remote Office(s) •Data Center Archive / Off Site Critical Applicat Critical VMware Applications Applications File Servers Information Servers Applicat Servers File Servers VMware Servers Archive VMware Servers •FlashCopy •TSM Clients Cloud •FastBack •Manager •TDPs Storage ProtecTIER FastBack for •TSM Clients Workstations •TDPs Tiers of •TSM VE Cloud Storage Gateway FastBack •DR Tiers of •TSM Server Storage •TSM Server WAN WAN • Install / Upgrade • Configuration Centralized Administration • Monitoring • Set Policies • Reporting • Execute Backup / Restore “TSM is the grand-daddy of unified recovery management” -- Lauren Whitehouse, Enterprise Strategy Group 19 © 2013 IBM Corporation
  20. 20. Summary Understand today’s best practices – for IT High Availability and Business Continuity Strategies for: – Requirements, design, implementation – In-house vs. out-sourcing Step by step methodology – Essential role of virtualization – IBM technologies for replication and replication management20 © 2013 IBM Corporation
  21. 21. 21 © 2013 IBM Corporation
  22. 22. Resources and Information IBM Redbook: Business Continuity Planning Guide cts/sg246547.html In particular, chapters 3, 6, 722 © 2013 IBM Corporation
  23. 23. Tony Pearson 9000 S. Rita Road Bldg 9032 Room 1238About the Speaker Master Inventor, Tucson, AZ 85744 Senior Managing Consultant Mr. Tony Pearson +1 520-799-4309 (Office) Master Inventor, IBM System Storage™ Senior Managing Consultant IBM System Storage Tony Pearson is a Master Inventor and Senior managing consultant for the IBM System Storage™ product line. Tony joined IBM Corporation in 1986 in Tucson, Arizona, USA, and has lived there ever since. In his current role, Tony presents briefings on storage topics covering the entire System Storage product line, Tivoli storage software products, and topics related to Cloud Computing. He interacts with clients, speaks at conferences and events, and leads client workshops to help clients with strategic planning for IBM’s integrated set of storage management software, hardware, and virtualization products. Tony writes the “Inside System Storage” blog, which is read by hundreds of clients, IBM sales reps and IBM Business Partners every week. This blog was rated one of the top 10 blogs for the IT storage industry by “Networking World” magazine, and #1 most read IBM blog on IBM’s developerWorks. The blog has been published in series of books, Inside System Storage: Volume I through V. Over the past years, Tony has worked in development, marketing and customer care positions for various storage hardware and software products. Tony has a Bachelor of Science degree in Software Engineering, and a Master of Science degree in Electrical Engineering, both from the University of Arizona. Tony holds 19 IBM patents for inventions on storage hardware and software products.23 © 2013 IBM Corporation
  24. 24. Additional Resources Email: Twitter:Øtony Blog:Ø Books:Ø_tony IBM Expert Network:Øtony 242424 © 2013 IBM Corporation
  25. 25. Trademarks and disclaimersAdobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. ITInfrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce. Intel, Intel logo, IntelInside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or itssubsidiaries in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, Windows NT, andthe Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. ITIL is a registered trademark, and a registered community trademark of the Officeof Government Commerce, and is registered in the U.S. Patent and Trademark Office. UNIX is a registered trademark of The Open Group in the United States and other countries. Javaand all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Cell Broadband Engine is a trademark of Sony Computer Entertainment,Inc. in the United States, other countries, or both and is used under license therefrom. Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBMCorp. and Quantum in the U.S. and other countries.Other product and service names might be trademarks of IBM or other companies. Information is provided "AS IS" without warranty of any kind.The customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs andperformance characteristics may vary by customer.Information concerning non-IBM products was obtained from a supplier of these products, published announcement material, or other publicly available sources and does not constitute anendorsement of such products by IBM. Sources for non-IBM list prices and performance numbers are taken from publicly available information, including vendor announcements andvendor worldwide homepages. IBM has not tested these products and cannot confirm the accuracy of performance, capability, or any other claims related to non-IBM products. Questionson the capability of non-IBM products should be addressed to the supplier of those products.All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.Some information addresses anticipated future capabilities. Such information is not intended as a definitive statement of a commitment to specific levels of performance, function or deliveryschedules with respect to any future products. Such commitments are only made in IBM product announcements. The information is presented here to communicate IBMs currentinvestment and development activities as a good faith effort to help with our customers future planning.Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experiencewill vary depending upon considerations such as the amount of multiprogramming in the users job stream, the I/O configuration, the storage configuration, and the workload processed.Therefore, no assurance can be given that an individual user will achieve throughput or performance improvements equivalent to the ratios stated here.Prices are suggested U.S. list prices and are subject to change without notice. Starting price may not include a hard drive, operating system or other features. Contact your IBMrepresentative or Business Partner for the most current pricing in your geography.Photographs shown may be engineering prototypes. Changes may be incorporated in production models.© IBM Corporation 2013. All rights reserved.References in this document to IBM products or services do not imply that IBM intends to make them available in every country.Trademarks of International Business Machines Corporation in the United States, other countries, or both can be found on theWorld Wide Web at ZSP03490-USEN-0025 © 2013 IBM Corporation