Achieving Disaster Recovery Success

Transcription

1 Achieving Disaster Recovery Success Ros Schulman Hitachi Data Systems Technical Track, Session March, 0 :-:m About the Seakers Ros Schulman is Director, Data Protection at Hitachi Data Systems with over years exerience in the IT business both on the vendor and customer side including systems rogramming, oerations, technical suort and sales suort. She currently works in the Global Solutions Strategy and Develoment organization with resonsibility for Data Protection Software and Mainframe Management software including Disaster recovery and backu software. She sends much of her time with Customers, discussing their unique Data Protection challenges. She has also co-authored many white aers in the area of Business Continuity. Rebecca M. Levesque is Chief Executive Officer of st Century Software and resonsible for shaing the comany s roduct strategy and vision. She has over 0 years exerience heling hundreds of comanies establish resiliency and recoverability strategies from any disrutive event. Her knowledge and deth of exerience is offered as a seaker at SHARE, IBM Systems Magazine, ACP, and DRJ. She is a ublished author in trade journals, white aers, and industry forums. Additionally, Rebecca has heled executives, storage managers, and technical architecture rofessionals leverage their existing storage technology investments while ensuring efficiencies across the enterrise. About this Session Have you ever questioned if your IT solution maximizes technology, olicies, and rocedures or whether your strategy encomasses continuous data rotection, relication, or traditional DR? Is IT substituting high availability for DR? Are you really getting a real return on investment for the availability solution in lace? This session demystifies long-standing (and often misguided) assumtions made around recoverability and more imortantly time to data. Learn how combining storage-based relication and host-based software lowers your RPO and RTO, delivering robust and effective recovery solutions.

2 Misunderstandings of Mainframe Availability Myth : Distributed systems are down much more often than mainframes Myth : As long as I relicate my critical data, it should be easy to restart my critical alications after a disrution Myth : Storage Systems are bulletroof Myth : A owners & storage folks understand interlay of technology and effect on recovery Myth : HA technologies like GDPS negate the need for other forms of Data Protection Establish Problem Then Aroriate Solution Disaster Recovery solves site/hardware interrution Does not solve oerational recovery issues May not be suitable for smaller local failures High availability does not solve everything Establish RPO s/rto s that match your SLA s Use the right technology Most relication technologies create crash consistent data May be ok for Databases What about oen datasets Non-database alication recoverability requires different aroach for both oerational recovery and DR

3 Data Protection Actual DR events -% It matters less whether the root cause of an oerations disrution is a significant disaster event or minor malfunctioning of one or ieces of data center equiment. The disrutive effect on business oerations is the same. What are we rotecting against? Traditional Recovery Time Slots Industry Requirements RTO RPO SLA (maximum) To Tier Financial Services, Healthcare, Utilities, Telecom seconds hours seconds hours minutes Media, IT, Manufacturing, Federal Government, Financial Services, Retail, Distribution, Biotech hours hours hours Insurance, Transortation, Energy, Education, State & Local Government Hositality, Food & Beverage, Wholesale Distribution, Constructions, Publishing, Nonrofit hours hours - hours > hours - hours hours Data courtesy of Gartner, 0

4 SLA Tiers Determine SLA er alication Tier - continuous availability requirement, maximum four minutes downtime a year Tier - high availability, maximum of one outage er year, maximum four hours outage er year Tier - recovery essential within hours, maximum three outages er year Tier - recovery required within three days, maximum four outages er year Tier - delayed recovery, all other services (Hiles, Continuity Central, 0) Oerational or DR or Both? Continuous availability enables / access to ITenabled business functions, rocesses and alications Continuous availability involves two strategies: high availability (minimizing unlanned downtime) and continuous oerations (minimizing lanned downtime) Sometimes, continuous availability architectures embody disaster recovery strategies IT service rocessing continues desite disaster events Gartner refers to this as "multisite continuous availability (Gartner, Donna Scott, 0)

5 To Down Recommended Achieving 00% or near-00% availability requires a to-down aroach to engineering availability into the alication, infrastructure and oerating architectures. The greater the availability requirements, the more customization and integration are required across multivendor comonents of a solution. Achieving continuous availability is an exensive roosition and has, in the ast, generally been reserved for only the most critical business and IT services. How do legacy as lay in? (Gartner, Donna Scott, 0) Criticality Levels Define IT Resiliency Criteria - BIA & business cost of downtime analysis Criticality User Grou Utime Availability Mission Critical External (customer revenue roducing) / scheduled utime 99.9% ( min/mon) min RTO 0 RPO Critical Internal (ERP, ) /. days er week 99.9% ( min/mon) hrsrto hrs RPO Imortant Internal (financial systems) / days er week 99.% ( hrs/mon) hrs RTO hrs RPO Non-critical Internal (deartmental systems, R&D) / days er week 9% week RTO hrs RPO Data courtesy of Gartner, 0

6 Oerational Resiliency Timeline RTO or SLA? On-Line / Batch Cycle Daily Business & Oerational VTL or traditional Processes tae Recovery Point (RPO) Availability Relication Or Relication Break Point Of Last Backu On-Line / Batch Cycle Triage - Resonse Time Rollover to Side B or Taes, Disk Technology Recovery Process Relocate Business Functions Restore Oerating System(s) Relocate Non-DP Suort Restore Data & Voice Network Restore Alications, Prog. Prod. Traditional RTO Estimate ~ Hours Information Potentially Over Days Old Communication & Notification Restore Data / Information - + Hours - + Hours - Hours - Hours - 0+ Hours ACTUAL RTO In Excess Of Hours (Conservative) Ready To Go?? Business Recovery Process Recreate & Reenter Lost Data Reenter Manually Tracked Data Production? Can Business Use Day + Old Data? Systems Cleanu: Synchronization, Performance, Caacity, Configuration BUSINESS AS USUAL Percentage Utime Achieved Per Year Utime Maximum Downtime/Year % Missed* Six nines %. seconds Five nines % minutes sec Four nines 99.99% minutes sec Three nines 99.9% hours min Two nines 99.0% hours min One nine 90.0% days hours From htt:// % % % *Continuity Software Survey (0/0)

7 *BMC 0 Mainframe Survey Issues with Backu DATA GROWTH Successful backu 9 0 Backu Window Needed Data Recovery Objective 9 0 Available Disaster Strikes 9 0 Data Loss 9 0 Disaster Strikes RTO Data Restored Full backu Incr Incr Incr Incr Incr 0

8 What is your recovery oint? DATA GROWTH Successful backu 9 A 0 A A A 9 Backu Window Needed A A Data Loss 0 A A Data Recovery Objective A A A A A A Available Disaster Strikes Disaster Strikes RTOA Data Restored A Full backu Incr Incr Incr Incr Incr What about the roblems interdeendencies between as cause? 0 Data Protection Technologies and Recovery Time Technology RPO Range RTO Range MAX Downtime/yr SLA Archive Static Deends Hours Traditional Backu to Tae/Disk including VTL or PBBA - hours - hours d 9h 9m.s Hours 99.% Disk PIT/CDP With or without Alication Awareness Minutes hours mins hours Synchronous Relication 0- mins - hours Synchronous Relication with Failover 0- mins -0 mins Asynchronous Relication 0-0 mins hours Asynchronous Relication with Failover 0-0 mins 0 mins hours DC (Sync/HA and Async) 0-0 mins mins hours Hours minutes Hours minutes mins mins hours mins Minutes 99.9% 99.9% 99.99% % 99.9% mins 99.99% hours mins - mins 99.9% %

9 Recovery Classes and Performance Oerational Recovery (restore a file, folder, volume, system) RPO CDP Snashots Backu 0 Secs Mins Hours Days RTO Disk Virtual Tae Tae Disaster Recovery (restore oerations at/from another location) RPO Sync & Async Mirror Backu Relication Off-Site Tae 0 Secs Mins Hours Days RTO Disk Virtual Tae Tae Other Considerations Storage relication, software relication alone doesn t automate and guarantee failover Failover waits for go ahead or automate and roll the dice Corrution Tae/DASD seed differential SLA achieved through aroach What about GDPS? Batch has to be restarted even with GDPS Potential for transactions to have been stranded in the failed site Attemts to aly the stranded changes to the data in the active site may result in an excetion or conflict, as the before image of the udate that is stranded will no longer match the udated value in the active site (IBM Share - August, 0)

10 Balancing Risk, Costs, & Volume of Data Cost of Risk Data Loss Availability Cost of Protection CAPEX OPEX Otimize Risks and Costs Business Data Protection Service Level Service Level Resiliency - Focus on 0% Problem Emhasis on system vs. alication Plenty of data where is generational which data to use? How designed for active/active? Backus for alications where and when Intertwined deendencies are not known High availability solutions are not DR Jobs write at conclusion interrution midstream create unknown status Corrution coied and not detected

11 Different Data Classes Require Different Data Management Mirroring or synchronous relication, and continuous data rotection (CDP) for oint-in-time recovery Storage-based snashots and relication to increase availability (RPO and RTO) Standard backu rocesses (full + incremental) and relication for DR Migrate to archive tier, manage retention, and enable discovery Gartner on Key Challenges of Current Backu Solutions (Dave Russell) The convergence of backu and disaster recovery technologies has occurred largely because snashot, relication and virtualization have made it ossible to recover from a disaster without the need for a traditional data restoration. The methods involved in this convergence seek to minimize storage cost, while also allowing for instant recovery. (Posey, 0)

12 Time to Data is the ultimate determinant of recovery strategy effectiveness The amount of time required to restore alication access to a business is what searates a temorary CRISIS from a full blown DISASTER Slide courtesy of Jon Toigo Questions to Ponder Is the data you recover useable, what does it take to make it useable Are business SLAs achievable currently and do they match your RTO/RPO s? Are you using the right technology to ma to you SLA s What do you test from a recovery standoint DR Data corrution Have you ever tested month end, quarter end, or year end and determined how recoverability was affected

13 Summary - where are the gas? Any tye of availability solution Highly available configurations do not equate to 0 downtime High availability does not relace DR Resiliency is a rocess Recovery of systems (infrastructure) can easily disregard Alications involved Interdeendencies Tye of interrution (crash, corrution, deletion) and effect on data/jobs No single answer Ask us we can hel Cost of Risk Otimize Risks and Costs Data Protectio Business Service nlevel Service Level Cost to Protec t Hitachi Mainframe Business Continuity Portfolio IN-SYSTEM In-System REPLICATION Relication SOLUTIONS REMOTE Remote REPLICATION Relication SOLUTIONS REPLICATION MANAGEMENT Relication SOLUTIONS Solutions Solutions Management Solutions ShadowImage In-System Relication For full volume clones of business data with consistency (ATTIME slit with HUR) Hitachi TrueCoy Synchronous, consistent clones at remote location u to 00km (~0 miles) Hitachi Business Continuity Manager (BCM) Relication management in z/os environments IBM-Comatible FlashCoy Point-in-time volumes and datasets via IBM command set in z/os environment IBM-Comatible FlashCoy/SE Point In Time volumes with virtual volume ool as target vs. whole volumes Hitachi Universal Relicator (HUR) Any distance, unique use of Pull technology and Journal Volumes to accommodate link outages or interrutions IBM-Comatible XRC* Asynchronous remote relication via comatible with IBM XRC in z/os environment * Note: Only available as a migration tool to HUR Hitachi Relication Manager with mainframe BCM Enterrise-wide GUI relication management and monitoring for mainframe and oen systems IBM Basic HyerSwa, GDPS HyerSwa certification and/or integration High-availability storage for z/os environments Relication Assessment, Migration and Imlementation Services Best ractice designs that ensure results and lower risks in imlementation Relication Score Card (Health Check) Services Periodic checkus that ensure continued solution value

14 st Century Software z/os Portfolio Data Resiliency Storage Management & Usage Tae Migration VFI In-System Relication Slashes recovery Solutions time objectives and assures SLAs Erases recoverability gas, ensures resiliency, and reduces storage Enables recovery to job/dataset level through real-time architecture and atent ending software code (InstaSna, InstaRestore, and Timeliner) Focuses on intricate, alicationlevel deendencies Protects InFlight data and maximizes sna coies sync ed to alication backus Cross-alication deendencies Total Storage Remote Relication True knowledge Solutions for storage and management class Insightful reorting for JCL coding to avoid olicies Tier data based uon usage, reference, and criticality (from DR/VFI) Data modeling for new urchase or imroving allocation and utilization SaceFinder Intelligent resource management tools Tae/Assist Migration in Place Relication Management Solutions Reduces cost of managing tae resources while roviding continuous availability Director and high seed coy utilities Backend utility rocesses assure referential data Portability, disaster recovery, and backu coies for data resiliency Consolidation of data Exertise to assist in migration management Recovery Resiliency, Storage Management and Modeling, Tae Migration and Imlementation Services Questions? Thank you!

15 Final Thought The lifeblood of almost every organization is data, and the requirements to rotect, maintain, and access the systems that store that data are absolutely essential to suort business oerations. With the sheer amount and varying tyes of information that must be stored, the comlexity of managing the data can grow as quickly as the amount of data itself. In this fast-moving day and age, businesses cannot afford to wait for anything if they do, they risk, at best, losing sales to the cometition, or, at worst, falling behind the cometition and being ushed out of business. (Storage Economics for Dummies - Hitachi Data Systems, 0) Thank You! For additional Hitachi information, lease contact: Ros Schulman Data Protection Technologies Global Solutions Strategy and Develoment Hitachi Data Systems 9 0 (cell) Ros.Schulman@hds.com For additional st Century Software information, lease contact: Rebecca Levesque st Century Software, Inc. 90 West Valley Road Suite 0 Wayne PA 90 U.S.A x (cell) RebeccaL@csw.com