IBM Advanced Technical Support Americas IBM DS 8000
IBM Advanced Technical Support - Americas IBM DS 8000 Data Replication Best Practices Bob Kern – bobkern@us. ibm. com Jim Sedgwick – jsedgwic@us. ibm. com Hank Sautter – sautter@us. ibm. com © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Agenda § DS 8000 Copy Services - Best Practices § DS 8000 Data Replication Technology – Key Concepts – Selecting the Right Solution to Match your Clients Business Needs § Planning for Data Replication – Configuration – Data Collection – Band. Width Studies – Automation § Case Studies – What you do not want to do…. . 2 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas DS 8000 Copy Services - Best Practices § Map solution to Customer’s Business Requirements (RTO/RPO) – – – Pi. T Solution vs Continuous Mirror, Sync vs Async For several small customers doing PTAM -> a Pi. T Inc FC + GC can be attractive. High Availability z/OS Basic Hyper. Swap or GDPS Hyper. Swap Mgr, Dist. System – Software Dual Write across 2 Luns Metro Mirror on Same Data Center Floor -> outage, re-ipl minimizes outage time. § Configuration Guidelines for Primary & Secondary – Balance Primary & Secondary Performance (subsystems/cache/drives/etc. ) – 1: 1 or 2: 1 Configurations tend to be simpilier to configure & Manage. – Be careful reusing “old” technology boxes as targets. – Ability to Test D/R while Maintaining D/R Protection. • Standard for most customer. • Emerging Standard -> Test the Way the Recover & Recover the Way they Test. – Failover/Failback Functionality • Site Toggle can perhaps reduce D/R Test costs. Run 6 months in each site. § Bandwidth Analysis -> Data Collection – Use Tools: Disk Magic, RMF Magic etc. – Analysis is VERY Important to understand BW for MB/Sec Update rates. – MB/SEC Update Rates can also help customer Manager his business. Understand activity 24 X 7… – Planning for Capacity Growth • Initial Deployment should have some capacity Growth planned into Solution. • Customer needs to understand how to do this as the years go by, workloads change etc. § Review - D/R Lessons Learned – White Paper: IBM Storage Infrastructure for Business Continuity – Updated This year – http: //www. ibm. com/support/techdocs/atsmastr. nsf/Web. Index/PRS 2511 § Management Software -> TPC-R or GDPS – DSCLI can be made to work, but can be very complicated. – Best Implementations involve TPC-R or GDPS Software. 3 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Map the Right Solution to the Clients Business Requirements 4 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Aspects of Availability High Availability Fault-tolerant, failureresistant infrastructure supporting continuous application processing Continuous Operations Non-disruptive backups and system maintenance coupled with continuous availability of applications Protection of critical business data Recovery is predictable and reliable 5 Disaster Recovery Protection against unplanned outages such as disasters through reliable, predictable recovery Operations continue after a disaster Costs are predictable and manageable © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Business Continuity Tiers Tier 4 - Point in Time disk copy Tier 3 - Electronic Vaulting Tier 2 - Hot Site, Restore from Tape 15 Min. 1 -4 Hr. . 4 -8 Hr. . 8 -12 Hr. . 12 -16 Hr. . 24 Hr. . Recovery Time Objective Days SERVICES D/R AUTOMATION TAPE Tier 5 –Software replication NETWORK Cost Tier 6 - Disk mirroring (with/without automation) DISK Tier 7 – Site Mirroring with automated recovery MANAGEMENT SW Recovery from tape copy REPLICATION SW Recovery from a disk image Tier 1 – Restore from Tape Best Business Continuity practice is to blend solutions in order to maximize application coverage at optimum cost 6 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Data Replication Enabling Core Technologies Flash. Copy Pi. T Incremental Flash. Copy Internal Copy + Metro Mirror Available on: Available on: DS 6000, DS 8000, ESS DS 6000, DS 8000, ESS SAN Volume Controller, XIV, DS 4000, DS 5000, Copy data command issued Copy is immediately available Source Target Time Write Read Primary Prod Pi. TCopies Pi. T Incrementa l Flash. Copy Read and write to both source and copy possible Global Copy (Asynchronous ) WAN Optional background copy 7 When copy is complete, relationship between source and target ends REMOTE PPRCXD Secondar y Flash. Cop y Pi. T Incremental Copy © 2009 IBM Corporation
IBM Advanced Technical Support - Americas IBM Copy Services Technologies Global Mirror Metro / Global Mirror Metro Mirror Flash. Copy § Asynchronous mirroring § Three site synchronous and § Synchronous mirroring § Point in time copy asynchronous mirroring § Available on: § DS 8 K Hyper. Swap § DS 8 K FCSE § Available on: § DS 8000, DS 6000 § DS 8000 § SAN Volume Controller § DS 8000, DS 6000, ESS § DS 8000, DS 6000, SAN § N Series Volume Controller § DS 4000/DS 5000 § SAN Volume Controller § DS 4000/DS 5000 § N Series § XIV Within Storage System Primary Metro distance Primary Metro Site A <300 km Site A Site B Out of 8 Region Out of Site Region B Site C © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Configuration Guidelines 9 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Configuration Guidelines for Global Mirror § Whitepapers: – Global Mirror http: //w 3 -03. ibm. com/support/techdocs/atsmastr. nsf/Web. Index/WP 100642 – GM Secondary http: //w 3 -03. ibm. com/support/techdocs/atsmastr. nsf/Web. Index/WP 101105 § TPC for Replication or GDPS – Required – Managing GM with dscli scripts is not a realistic customer option § Do not undersize the GM Secondary § Solution Planning Considerations – Asymmecrical. vs symmetrical – Volume size and layout • LH, RJ (A, B, C) are exactly the same size – Failover & failback considerations • More on layout later – LSS Considerations – balance resources • Dedicate two LSS(s) per DS 8000 to an application, one even, one odd – Tends to group volume numbers in ranges – easily recognizable ranges of volumes – Management is easier with fewer LSSs – Performance evaluation & Bandwidth Sizing between sites – Use dedicated PPRC link ports, 2 minimum, on separate host adapters § Testing !! 10 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Global Mirror Prerequisite –> Performance at the Primary Site § Global Mirror Primary Performance must be good on volumes to be replicated – Rank Performance • Backend response times • Frontend Write response times ≤ 2 ms • No cache issues – Host Port Performance – Good I/O balance across Ranks, Host Adapters – Performance Tools: • TPC for Disk • RMF Magic § Plan and Monitor for Growth – Workloads increase – Additional replication requirements • New applications 11 Global Mirror Local Site Remote Site Global Mirror Primary Global Mirror Secondary © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Global Mirror Secondary - Performance Capacity Ok. Recommende d max number of GMir volumes Recommended max number of GMir volumes DS 8000 LIC Release 3. 0 or later ESS 800 1000 N/A DS 6800 350 N/A DS 8000 / 16 GB 1500 4500 DS 8000 / 32 GB 1500 4500 DS 8000 / 64 GB 3000 9000 DS 8000 / 128 GB 6000 18000 DS 8000 / 256 GB 12000 36000 § Equal to or Greater than the performance capacity of the primary § Global Mirror places more write performance stress on the secondary – More storage capacity – Flash Copy processing § Cache required per volume count § Do not undersize the Secondary Global Mirror Primary Global Mirror Secondary ESS 800 with Arrays Across Loops DS 8100 DS 8300 DS 8100 model 921 DS 8100 model 931 DS 8300 any model 12 DS 8300 model 922 DS 8300 model 932 Global Mirror Local Site Remote Site Global Mirror Primary Global Mirror Secondary © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Placement of B and C volumes Secondary Primary A § Same RPM § Same RAID type 13 B C B C § On Secondary – B and C copies on – All ranks contain equal numbers of B same rank results in and C volumes hotspot being – B and C copies for particular volumes concentrated on single kept on separate ranks rank – Activity for busy volumes spread over two ranks – DDM size equal to or one size greater than primary © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Placement of B, C and D volumes 14 B C D B C B C D D D § All ranks contain equal numbers of B, C and D volumes § D volumes placed on separate ranks to keep testing and backup activity separate § B and C copies for particular volumes kept on separate ranks § B and C copies for particular volumes on different ranks § Placement of D volumes as shown above less critical but easier to manage/track/implement § This does reduce available ranks for B & C volumes © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Flash. Copy Source & Target Placement § In general: – – Spread evenly across disk subsystems Within each disk subsystem, spread evenly across clusters Within each cluster, spread evenly across device adapters Within each device adapter, spread evenly across ranks § Place Flash. Copy target in same cluster as source – If using BACKGROUND COPY, target on a different device adapter § Flash. Copy Space Efficient – Use Flash. Copy Space Efficient when economy is more important than performance and for short-lived relationships with low update rate on source volumes • Short Term Flash. Copy relationships • Good for read only applications – Tape Backup, 24 hour online backup, etc 15 Cluster Device Adapter Rank Flash. Copy Establish Performance Same cluster Doesn’t matter Different ranks Background Copy Performance Same cluster Different device Different ranks adapter Flash. Copy Impact to Applications Same cluster Doesn’t matter Different ranks © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Flash. Copy SE Relationships § Full volume only § NOCOPY only in first release – Background copy cannot be initiated to a SE volume by any means § Must specify “SE target ok” at establish § Recommended Usage – Use Flash. Copy Space Efficient when economy is more important than performance and for short-lived relationships with low update rate on source volumes • Short Term Flash. Copy relationships • Good for read only applications – Tape Backup, 24 hour online backup, etc 16 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Data Collection Performance and Bandwidth Studies 17 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Data Collection Essentials § Historical Data – Data selection is critical for obtaining valid results • Single data points or averages are not very useful • Size and duration of peaks are important – Need to identify daily peaks and the workload profile over time • End of month, end of quarter, end of year, etc. – Identify active volumes for workload balancing – Quantify expected growth § Configuration details – Production vs. test data – Temporary data may not be part of Global Mirror – Volume layout by array and storage pool – Network configuration including bandwidth available § Monitoring Performance and Status – TPC Standard Edition – RMF data (enable ESS data collection) – TPC for Replication – Global Mirror Monitor 18 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Data Collection Essentials (2) § Data needed for evaluation – Performance data for 1 week – I/O rates, Data Rates, Response times – Configuration details and event timelines (when are peaks expected) § Data Sources – RMF for z. Series – i. Series PT reports – Total Storage Productivity Center (TPC) reports – iostat reports, windows perfmon reports § Evaluation tools – Disk Magic – RMF Magic – DS 8 Qtool Capacity planning Performance evaluation DS 8000 physical and logical configuration details § Contact IBM ATS for Performance and Bandwidth Studies – add a link to partner world. 19 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Lessons & Automation 20 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Lessons Learned About IT Survival § Repeated Testing before a disaster is crucial to successful recovery after a disaster – – TTWYR – Test The Way You Recover RTWYT – Recover The Way You Test § After a disaster, everything is different – – Staff well-being will be 1 st priority Company will benefit greatly from well-documented, tested, available and – Repeated Testing before a disaster is crucial to successful recovery after a disaster automated (to the extent possible) recovery procedures –TTWYR – Test The Way You Recover § May be necessary to implement in-house D/R solution to meet RTO/RPO –RTWYT – Recover The Way You Test § Plan geographically dispersed IT facilities – IT equipment, control center, offices, workstations, phones, staff, . . . – After a disaster, everything is different – Network entry points –Company will benefit greatly from well-documented, tested, available and § Installed server capacity at second data center can be utilized to meet normal day-to-day needs automated … recovery procedures § Failover capacity can be obtained by – – Prioritizing workloads Exploit new technology: Capacity Back Up (CBU) § Data backup planning and execution must be flawless – – Disk mirroring required for <12 hr RTO (need 2 x capacity) Machine-readable data can be backed up; not so for paper files § Check D/R readiness of critical suppliers, vendors 21 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Automation: Critical for successful rapid recovery & continuity § The benefits of automation: – Allows business continuity processes to be built on a reliable, consistent recovery time – Recovery times can remain consistent as the system scales to provide a flexible solution designed to meet changing business needs – Reduces infrastructure management cost and staffing skills – Reduces or eliminates human error during the recovery process at time of disaster – Facilitates regular testing to help ensure repeatable, reliable, scalable business continuity – Helps maintain recovery readiness by managing and monitoring the server, data replication, workload and the network along with the notification of events that occur within the environment Automate - Automate 22 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Tivoli Storage Productivity Center for Replication (TPC-R) Overview § Replication management solution – Simplified replication management & monitoring – Powerful commands and logic § Multiple Storage subsystems – DS 8000, DS 6000, ESS 800, SVC § Multiple logical volume types – Open systems (FB) LUNs – z/OS (CKD) volumes § Multiple replication types – Flash. Copy – Metro Mirror – Global Mirror – Metro/Global Mirror § High performance and scalability § TPC for Disk, TPC for Data and TPC for Fabric are not required but can coexist on the same server – Shared instance of DB 2 – Shared SNMP port 23 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas TPC Replication Manager • • Setup Copy Sessions Execute Copy Operations Monitor Copy Status Manage/Monitor Consistent Groups Alert Operations on Exceptions / Failures • • TPC For Replication Primary/Source Site DS 8000 DS 6000 Second/Target Site DS 8000 ESS SAN Volume Controller • • 24 DS 6000, DS 8000 support Global Mirror Support Replication Progression Monitoring High Availability Disaster Recovery Automation (failover, failback) DS 6000 ESS SAN Volume Controller Automated copy services configuration Central operations for copy services Operational status on copy services operations Assistance with recovery on failures © 2009 IBM Corporation
IBM Advanced Technical Support - Americas TPC for Replication GUI § My Work hyperlinks on left § Display area for panels on right § Select session, select action (from dropdown list) and GO § Tables with hyperlinks and sortable columns § Health Overview on every panel § Session view – Triangle Indicates application access (active host) – Arrows between roles indicate direction of active replication 25 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas TPC-R Video Series (new on Techdocs) § Series of live demonstrations captured on video managing various environments § Link to Summary of all the videos: – http: //www. ibm. com/support/techdocs/atsmastr. nsf/Web. Index/PRS 3687 § Series includes the following demonstrations: – CLI vs. TPC-R – (2: 13) – adding copysets using CLI and TPC-R – TPC-R 3. 3 GM – (17: 36) – GM setup with FO/FB using TPC-R 3. 3 – TPC-R 3. 4 GM with Practice – (6: 39) – GM with Practice Volumes setup with FO/FB – TPC-R 4. 1 overview – (14: 24) – Overview of TPC-R with MM setup demonstration – TPC-R 4. 1 adding HW – (10: 01) – how to add DS 8000 and SVC to TPC-R – TPC-R 4. 1 MM setup – (19: 20) – using TPC-R 4. 1 to manage MM with FO/FB – TPC-R 4. 1 GM setup – (17: 36) – Using TPC-R 4. 1 to manage GM with FO/FB – TPC-R 4. 1 MM with Practice – (8: 15) Using TPC-R 4. 1 to create practice volumes 26 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas TPC-R Simplification: Starting a Global Mirror Copy Using the DS 8000 Hardware Commands 27 1. Determine where to place Master GM session given the PPRC paths. 2. Establish PPRC links between Master and Subordinate DS 8000’s. 3. Establish PPRC paths between A and B volumes 4. Establish Subordinate sessions on the A volumes of the DS 8000’s 5. Establish a GC relationship between A and B 6. Query A to determine first pass complete 7. Establish Flash copy between B and C with incremental 8. Add A to the subordinate Global Mirror session 9. If first A volume on this DS 8000, then start the Global Mirror Master with new configuration § Monitor the Global Mirror Master with 051 queries and calculate RPO. § Monitor failures and fatal conditions Using TPC-R Commands 1. START © 2009 IBM Corporation
IBM Advanced Technical Support - Americas TPC-R Simplification: Recover a Global Mirror Copy Using the DS 8000 Hardware Commands 28 1. Establish PPRC B to A Failover 2. Query all B to C Flash Copy relationships and determine if they are revertible and have the same sequence number 3. If the sequence numbers are all the same AND at least one relationship is not revertible, issue a “withdraw Flash Copy with commit” to all of the revertible relationships 4. If all of the Flash Copy relationships are Revertible, issue a “withdraw Flashcopy with revert” to all Flashcopy relationships. 5. Issue “establish Flashcopy C to B” with Fast Reverse Restore Using TPC-R Commands 1. RECOVER © 2009 IBM Corporation
IBM Advanced Technical Support - Americas The right level of business continuity protection for your business…. GDPS family of offerings Continuous Availability of Data within a Data Center Continuous Availability / Disaster Recovery Metropolitan Region Disaster Recovery at Extended Distance Continuous Availability Regionally and Disaster Recovery Extended Distance Single Data Center Applications remain active Two Data Centers Systems remain active Two Data Centers Three Data Centers Near-continuous availability to data Automated D/R across site or storage failure No data loss Automated Disaster Recovery “seconds” of Data Loss Data availability No data loss Extended distances SDM A B C GDPS/PPRC Hyper. Swap Manager 29 GDPS/PPRC Hyper. Swap Manager GDPS/PPRC GDPS/GM GDPS/XRC GDPS/MGM GDPS/Mz. GM © 2009 IBM Corporation
IBM Advanced Technical Support - Americas The right level of protection for your business – Distributed Platforms DR at extended distance CA / DR within a metropolitan region Tivoli SA App. Man Platforms: Two data centers - systems remain active; designed to provide no data loss Rapid systems recovery with only ‘seconds” of data loss GDPS/XRC GDPS/PPRC SDM K-sys K-Sys ØIBM System p AIX 5. 2, 5. 3, 6. 1, Linux: SUSE SLES 9, 10 Red. Hat RHEL 4, 5 ØIBM System x Linux: Suse SLES 9, 10, Red. Hat RHEL 4, 5; Windows 2003, 2008 ØIBM System I Linux: Suse SLES 9, 10, Red. Hat RHEL 4, 5 ØIBM System z z/OS V 1. 7+, Linux: Suse SLES 9, 10, Red. Hat 4, 5 ØVMWARE ESX Win Server- Linux: Suse SLES 9, 10, Red. Hat RHEL 4, 5; Windows 2003, 2008 Ref IBM Tivoli System Automation 3. 1 Installation & Customization Guide in the Release notes for a more detailed reference on GDPS DCM Supported configurations. Site-1 VCS or SA App. Man Site-2 GCO VCS or SA App. Man & GDPS DCM Agent Site-1 VCS Site-2 GCO VCS and GDPS DCM Agent Symantec VCS Platforms: IBM System P & p. Hype - AIX 5. 3 IBM System x (Intel / AMD x 86_64) - Suse SLES 9 & RH 4 HP (Itanium / PA RISC) – HP-UX 11. 23. SUN (SPARC) – Solaris 9 & 10. VMWare ESX 3. 0 (Intel / AMD x 86_64) - Suse SLES 9 & RH 4 & Windows AS & Windows 2300. 30 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Case Study #1 Bandwidth Requirements 31 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Data Replication Case #1 - Summary § Global Mirror consistency group formation fails – Drain time exceeded – Suspended volumes – Link incidents (Frame transmission retries <1%) § Configuration Details – – Two 9 Mbit links between sites 80 volumes mirrored 3: 1 compression on links PPRC ports on the same HBA § Operational Details – – – Script written to monitor Out-of-Sync Tracks TPC for Disk used to provide performance data TPC-R used to automate Global Mirror Started with a few mirrored volumes – no issues with Global Mirror Increased number of volumes and workload • Noticed host impact due to slow links • Switched to Global Copy • Large number of OOS Tracks 32 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Data Replication Case #1 - Bandwidth Requirements § The following chart shows the mirrored write MB/s profile with indications of the Link Bandwidth required – 3: 1 Compression and 80% Link efficiency – Exceeding the bandwidth will result in higher RPO § Workload values above the “ 9 Mb” links indicate that the capacity of the link is exceeded – 1 -3 Distance Links do not handle the workload – 4 - Distance Links are sufficient for the current workload • With some longer RPO times during peaks • Should suspend GM during large peaks – 8 -12 - Distance Links would be needed for the 25 MB/s peak § Available bandwidth is 2 links – Not dedicated – Link timeouts occur when over-driven 33 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas 4 Links = min required bandwidth 2 Links = available bandwidth 34 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Data Replication Case #1 – Out-of-Sync Tracks § The 1 st chart shows the PPRC Link activity – – Available Link bandwidth was insufficient Over driving the links resulted in redriving frames (timeout) Delays resulted in full track transfers instead of sending data from cache Full track transfers increased the bandwidth requirement § The 2 nd chart shows the OOS Tracks and suspended volumes – – 35 Peak workload occurred at 2: 00 -3: 00 am on most days Large number of OOS Tracks could not be copied before the next peak OOS Tracks must be low to for Consistency Groups to form OOS Tracks fully copied about 2 times per week © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Full Track Transfers increase required bandwidth Overdriving links causes delays CGs possible only when links are not overdriven 36 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Overdriving links causes OOS Tracks and suspended volumes Cannot “catch-up” before the next peak CGs possible only when OOS Tracks are low 37 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Data Replication Case #1 – Conclusion § Bandwidth equivalent to 4 – “ 9 Mbit” links to handle the workload – Sufficient for the “normal” workload – May need to suspend Global Mirror during large peaks (measured 25 Mb/sec) – Should consider future growth § Follow Best Practices for Data Replication – Links should be dedicated to guarantee required bandwidth and reduce link timeouts. – PPRC Ports should be on dedicated cards and • Do not share cards with host activity • Do not put both links on the same HBA (single point of failure) • 4 links on 2 HBAs would be preferred – Monitor Status and Performance • Use TPC for Disk to monitor link activity and workload growth • Do not ignore TPC-R messages • Test DR procedures 38 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Case Study #2 Performance Requirements 39 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Data Replication Case #2 - Summary § Global Mirror consistency group formation fails – Drain time exceeded – Host performance impacted while GM is active § Configuration Details – – Distance between sites Link information Primary DS 8000 Secondary DS 8000 37 miles / 60 km Gig. E = 100 MB/sec 300 G 15 K Drives Raid 5 § Operational Details – TPC for Disk used to provide performance data – TPC-R used to automate Global Mirror – Increased workload since initial GM Design • Noticed host impact when GM was implemented • Switched to Global Copy 40 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Data Replication Case #2 – Performance & Bandwidth § Bandwidth analysis – Available bandwidth is not the cause of Global Mirror issues – Usually 20 -30 MB/sec short peaks 50, 90 MB/sec – Gig. E Link can handle 100 MB/sec without compression § Current Global Mirror Configuration Follows Best Practices – Volume placement is not the cause of performance issues – PPRC ports are separate from Host ports (good) • Should use every other port on HBA card for best performance – Volumes spread over all Arrays (good) • PPRC volumes share arrays with Flash Copy targets • Do Not have the Flash. Copy source and target in the same array • Target should be in the came cluster § Performance analysis – Primary disk utilization is too high without any Mirror activity – Secondary disk utilization is at the maximum when Global Mirror is active – Flash Copy activity adds to HDD utilization – When Global Copy is active HDD utilization decreases – Raid 10 will reduce the HDD Utilization (double number of arms) 41 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Global Mirror 42 Global Copy © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Part 1 06 -21 14: 20 to 06 -22 13: 40 Global Mirror Warning level 43 Caution level © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Part 2 06 -22 15: 35 to 06 -23 14: 45 Global Copy 44 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Part 1 06 -21 14: 20 to 06 -22 13: 40 Global Mirror GM Flash Copy adds to HDD activity Utilization is too high! 45 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Part 2 06 -22 15: 35 to 06 -23 14: 45 Global Copy 46 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Data Replication Case #2 – Conclusion § Previous Disk Magic Study Showed Good Results – Original workload • 4, 800 I/O per second HDD Utilization 35% – However the workload has grown • 7, 300 I/O per sec HDD Utilization >90% • Other systems were added § HDD Utilization is too high – This condition will cause Host performance issues even without Global Mirror active – Overloaded arrays at remote site causes Host performance issues when Global Mirror is active – Added copy activity at the primary site causes Host performance issues when Global Copy is active § Current workload has reached the limit of the current configuration – Need to spread the workload over more arrays and use Raid 10 – Need to plan for future growth – Continue to use TPC Standard Edition to monitor performance 47 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Further Assistance § DS 8000 Architecture & Best Practices - Replay Ø TIME Given: August 13; 11: 00 a. m. New York, 4: 00 p. m. London, 5: 00 p. m. Paris, 15: 00 GMT Ø IBMers: http: //w 3. ibm. com/sales/support/Show. Doc. wss? docid=Q 824765 C 05775 Z 31&infotype=SK&infosubtype=N 0&node=doctype, N 0|doctype, TLC|brands, B 5000|brands, B 8 S 00&appname=CC_CFSS Ø BPs: http: //www. ibm. com/partnerworld/wps/servlet/Content. Handler/tsee 081309 km § Contact ATS: ØBusiness Partners: PARTNERWORLD CONTACT SERVICES (US & Canada) 1 -800 -426 -9990 or fill out a request online: http: //ibm. com/partnerworld/techline ØIBMer’s: Open Techline Request 48 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Additional References 49 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Data Replication Enabling Core Technologies Flash. Copy Pi. T Incremental Flash. Copy Internal Copy + Metro Mirror Available on: Available on: DS 6000, DS 8000, ESS DS 6000, DS 8000, ESS SAN Volume Controller, XIV, DS 4000, DS 5000, Copy data command issued Copy is immediately available Source Target Time Write Read Primary Prod Pi. TCopies Pi. T Incrementa l Flash. Copy Read and write to both source and copy possible Global Copy (Asynchronous ) WAN Optional background copy 50 When copy is complete, relationship between source and target ends REMOTE PPRCXD Secondar y Flash. Cop y Pi. T Incremental Copy © 2009 IBM Corporation
IBM Advanced Technical Support - Americas DS 8000 Flash. Copy Options § Once Source/Target “Logical” relationship established – Both volumes are available for Read/Write. § Multiple Relationships - Single Source may have up to 12 Targets. § Background Copy Optional – No. Copy to Copy – Background Copy § Persistent & Incremental § Consistent Flash. Copy (across volumes in single DS 8 K or across multiple DS 8 Ks) § Target device may be in any LSS § Space Efficient Flash. Copy (single FC repository for all target volumes) – For Backup typically requires 10 -20% of actual space. § Remote Pair Flash. Copy 51 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas IBM Hyper. Swap Technology -> Higher Availability for Parallel SYSPLEX ! § Ability to swap enterprise class System z Disk Subsystems in seconds. § § § application Hyper. Swap substitutes Metro Mirror secondary for primary device No operator interaction, Designed to scale to multi-thousands of z/OS volumes Includes volumes with SYSRES, page data sets, catalogs Non-disruptive - applications keep using same device addresses Hyper. Swap integration with z/OS yielding Higher Availability for z/OS. Basic Hyper. Swap (GA 2008) UCB • Single site continuous availability function UCB • Unplanned failures • Planned fail over (testing) • Aimed at masking disk failures • IBM Disk Subsystems ONLY (ESS 800, DS 6000, DS 8000) GDPS/PPRC Hyper. Swap Manager (GA 2006) P Metro Mirror • Single site or multiple sites S • Continuous availability and/or Entry level DR solution • Any Vendors disk subsystem that supports the IBM PPRC Architecture (ex. IBM, EMC, Hitachi (HP & SUN) GDPS/PPRC w/Hyper. Swap (GA 2002) • Full function Hyper. Swap across multiple Sites for D/R and High Availability. • Includes Server, Workload & Network Management across sites in addition to Storage • Supports GDPS/Mz. GM and GDPS/MGM environments. • Any vendors disk subsystem that supports the IBM PPRC Architecture. (ex. IBM, EMC, Hitachi (HP & SUN) 52 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas DS 8000 Global Mirror: ŸConcept § Asynchronous long distance copy (Global Copy), i. e. , little to no impact to application writes § Verify End to End Data Integrity § CRC sent & verified w/each changed Block/record. § GM detects dropped FCP Frames § For ECKD devices track format also sent & verified in Metadata. § CG “Marked” at primary, but CG is formed at Target Site, yields continuous BW utilization. § Momentarily pause application writes (fraction of millisecond to few milliseconds) § Create point in time consistency group across all primary subsystems (in OOS bitmap) § New updates saved in Change Recording bitmap § Restart application writes and complete write (drain) of point in time consistent data to remote site § Stop drain of data from primary (after all consistent data has been copied to secondary) § Logically Flash. Copy all data (i. e. , 2 ndary is consistent, now make tertiary look like 2 ndary) § Restart Global Copy writes from primary § Automatic repeat of sequence every few seconds to minutes to hours (selectable and can be immediate) ŸIntended benefit § Long distance, no application impact (adjusts to peak workloads automatically), small RPO, remote copy solution for z. Series and Open Systems data, and consistency across multiple subsystems Global Copy (PPRC-XD) over long distance Host I/O 53 Could require channel extenders Primar y Loca l Sit e FCP links only (Asynchronous) Global Copy Flash. Copy (record, nocopy, persistent, inhibit target write) Secondar y Tertiary Remote Sit e © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Metro/Global Mirror architecture Server or Servers *** 4 normal application I/Os 1 Global Mirror network Global Mirror Flash. Copy asynchronous NOCOPY large distance Metro Mirror 2 A B 3 Metro Mirror network synchronous small distance c D Global Mirror Metro Mirror write Global Mirror consistency group formation (CG) 1. application to Vol. A 2. Vol. A to Vol. B 3. write complete to A 4. write complete to application a. write updates to B volumes paused (< 3 ms) to create CG b. CG updates to B volumes drained to C volumes c. after all updates drained, Flash. Copy changed data from C to D volumes ) Local Site (Site A 54 b a C ) Intermediate Site (Site B Remote Site (Site. C) © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Integrated solutions GDPS/MGM GDPS/PPRC GDPS/XRC GDPS/PPRC Hyper. Swap Manager AIX/HACMP 5. 1 + RCMF/XRC Delivered by IBM Global Services Flash. Copy - Point in time copy available on DS 8000™, DS 6000™, and ESS Features: § Multiple relationships - Single Source may have up to 12 Targets. § § § GDOC Veritas Clusters + IBM MM, GM or EMC SRDF, SRDF/A or VVR GDPS/GM RCMF/PPRC TECHNICAL SALES SUPPORT AMERICAS Background Copy optional No. Copy to Copy – Background Copy Persistent and Incremental Consistent Flash. Copy Metro Mirror Windows Geo. Distance MSCS + Metro-Mirror Scripts Delivered by IBM Global Services Data Replication Options: Metro Mirror - Synchronous mirroring available on DS 8000, DS 6000, and ESS Designed to provide: § No data loss § Industry leading replication performance § High Availability with GDPS™ Hyper. Swap™: §System z™ and open systems data § Ease of use, lower cost Target device may be in any LSS Pi. T Inc Flash. Copy to MM, GC, or GM Primary IB M Optional background copy 55 Read Write Target Source Tim e Read and write to both source and copy possible When copy is complete, relationship between source and target ends DS 6000/DS 8000 Data Replication Host Req (1) Ack (4) • Flash. Copy® (FC) (within Box) • Metro Mirror (MM/PPRC) (Sync Copy) • Global Copy (GC) Async Copy, No Consistency • Pi. T Incremental FC to MM, GC, or GM Primary • Global Mirror (GM) Async Copy • Global Mirror for z. Series® (z. GM) • Metro Global Mirror (MGM) • z. GM + MM/PPRC Multi-Target (Mz. GM) Managed by: • Total. Storage® Productivity Center – Replication Manager (TPC-R) • Geographically Dispersed Parallel Sysplex (GDPS) (See integrated solutions on inside flap. ) Send I/O write (2) VOLUME A Confirm I/O write (3) VOLUME B PRIMARY For more information, please contact your local IBM Representative or IBM Business Partner. May 2008 SECONDARY © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Global Mirror - Asynchronous mirroring available on Metro / Global Mirror – Three-site synchronous and asynchronous mirroring Available on DS 8000 Designed to provide: DS 8000™, DS 6000™, and ESS DS 6 K/DS 8 K/ESS key design to points: § Capability to achieve an RPO of 3 -5 seconds with sufficient bandwidth and resources § Do not impact production applications when insufficient bandwidth and/or resources are available § Scalable; providing consistency across multiple primary and secondary disk subsystems § Allow for removal of duplicate writes within a consistency group before sending data to remote site § Allow for less than peak bandwidth to be configured by allowing RPO to increase without restriction at peak times § Performance, scalability § Metro Mirror, Global Mirror § Satisfy all 3 -site requirements: § Fast failover / failback to any site § Fast re-establishment of threesite recovery, without production outages § Resynchronize any site with incremental changes only* § Ease of use, autonomic, self-monitoring Metro B A Global PRIMARY HOSTS I/O Write REMOTE HOSTS SA N DS 8000, ESS Global Mirror – 56 Mover (SDM) address space(s) running on z/OS. § Supports heterogeneous disk subsystems § Unlimited distances § Time consistent data at the recovery site § RPO within seconds § Supports System z™ and System z Linux® data § Over 200 installations worldwide § 3 -Site GDPS®/PPRC Hyper. Swap and GDPS/XRC “Multi-Target” Supported Designed to provide: • Performance, scalability • Metro Mirror, z. Global Mirror • Satisfy all 3 -site requirements: • HA and CA capability for Metro distance • Out of region DR with fast recovery • Resynchronize any site with incremental changes only* • Ease of use, autonomic, self-monitoring Flash. Copy Native performance SA N § Premium performance and scalability § Data moved by DFSMS™ System Data asynchronous mirroring Available on DS 8000 I/O Write 'A‘ Primary mirroring for System z available on DS 8000 and ESS 800 Designed to provide: Metro / z. Global Mirror Multi-Target (Mz. GM) - Three-site synchronous and § Provide consistency between System z and open systems data and between different platforms on open systems. z/OS Global Mirror -- Asynchronous ‘B’ Global Copy Secondary Consistent Data C © International Business Machines Corporation, 2007. System Data Mover Primary Host IBM, the IBM logo, GDPS, Global Dispersed Parallel Sysplex, Hyper. Swap, z/VM, z/OS, z. VSE, System z, are trademarks of International Business Machines Corporation in the United States, other countries or both. Microsoft, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product and service names may be trademarks or service marks of others. System Data Mover Secondary Host 2 1 Primary DS 8000 3 4 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas DS 6 K/DS 8 K Copy Services Matrix Device Is Metro Mirror or Global Copy Primary Metro Mirror or Global Copy Secondary Global Mirror Primary Global Mirror Secondary Flash. Copy Source Flash. Copy Target Incremental FLC Source Incremental FLC Target Concurrent Copy Source Yes 11 Yes No No Yes 11 No Yes No 5 Yes Metro Mirror or Global Copy Primary Yes No Yes 1 No 6 Yes 1 Yes Yes No 6 Yes Metro Mirror or Global Copy Secondary No No 5 Yes 1 No Yes 8 Yes No Global Mirror Primary Yes No 6 Yes 1 No No Yes Yes Yes Global Mirror Secondary No No 5 Yes 1 No No No Yes 8 Yes 9 No No Flash. Copy Source Yes Yes 3, 4 Yes 3 No Yes Flash. Copy Target No No 5 Yes 2 No No No Yes 4 No No No Incremental FLC Source No 7 Yes Yes Yes 9 Yes No No No Yes Incremental FLC Target No 7 No 5 Yes 2 No No Yes Concurrent Copy Source Yes Yes No Yes Yes Yes May Become GMz 10 (XRC) Primar y (XRC) Secondary No (XRC) Primary GMz 10 (XRC) Secondary 57 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas DS 6 K/DS 8 K Copy Services Matrix Notes 1. 2. Only in a Metro/Global Copy (supported on ESS) or a Metro/Global Mirror Environment (supported on ESS and DS 8000). Flash. Copy V 2 at LIC 2. 4. 0 and higher on ESS 800 (DS 6000 and DS 8000 utilize Flash. Copy V 2 by default). – You must specify the proper parameter to perform this – Metro Mirror primary will go from full duplex to copy pending until all of the flashed data is transmitted to remote – Global Mirror primary cannot be a Flash. Copy target 3. Flash. Copy V 2 Multiple Relationship. 4. Flash. Copy V 2 Data Set Flash. Copy (only available for z/OS volumes). 5. The Storage Controller will not enforce this restriction, but it is not recommended. 6. A volume may be converted between the states Global Mirror primary, Metro Mirror primary and Global Copy primary via commands, but it two relations cannot exist at the same time (i. e. multi-target). 7. GMz (XRC) Primary, Global Mirror Secondary, Incremental Flash. Copy Source and Incremental Flash. Copy Target all use the Change Recording Function. For a particular volume only one of these relationships may exist. 8. Updates to the affected extents will result in the implicit removal of the Flash. Copy relationship, if the relationship is not persistent. 9. This relationship must be the Flash. Copy relationship associated with Global Mirror – i. e. there may not be a separate Incremental Flash. Copy relationship. 10. Global Mirror for z. OS (GMz) is supported on ESS and DS 8000 11. In order to ensure Data Consistency, the XRC Journal volumes must also be copied. 58 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Reference Resources 59 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas References § “Global Mirror Whitepaper”, V 1 -3 – By Nick Clayton, 13/09/2005 – http: //w 3 -03. ibm. com/support/techdocs/atsmastr. nsf/Web. Index/WP 100642 § z/OS DFSMS Advanced Copy Services – SC 35 -0428, January 2006 § DSx 000 Command-line Interface User’s Guide – DS 6000 GC 26 -7922, September 2006 – DS 8000 SC 26 -7916, November 2006 § Device Support Facilities User’s Guide and Reference, Release 17 – GC 35 -0033, March 2005 § Redbooks – www. redbooks. ibm. com or w 3. itso. ibm. com – Search on “DS 6000” & then “DS 8000” • Many choices available – Also search on “copy services” • Again, many choices available 60 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas To COPY or to NOCOPY? …. That is the question! § BACKGROUND NOCOPY is typically the best choice to minimize rank and DA activity within the physical box § But…. You must ask why are you making a copy? And…. What type of application workload do I have? – For example: • Is the copy only going to be used for creating a tape backup? – BACKGROUND NOCOPY should be used and the relationship withdrawn after the tape backup is complete • Is the copy going to be used for testing or development? – NOCOPY again is typically the best choice • Will you need a copy of the copy? – BACKGROUND COPY must be used so that the target will be withdrawn from its relationship after all of the tracks are copied thereby allowing it to be a source in a new relationship > Possibly use NOCOPY to COPY option • Is the workload OLTP (NOCOPY typically is the choice) or are there a large number of random writes and are not cache friendly (COPY may be the better choice) 61 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas References § SC 26 -7916 DS 8000 Command-Line Interface User’s Guide § GC 26 -7922 DS 6000 Command-Line Interface User’s Guide § SC 35 -0428 DFSMS Advanced Copy Services § SG 24 -6788 IBM System Storage DS 8000 Series: Copy Services in Open Environments § SG 24 -6787 IBM System Storage DS 8000 Series: Copy Services with IBM System z § SG 24 -6783 IBM System Storage DS 6000 Series: Copy Services in Open Environments § SG 24 -6782 DS 6000 Series: Copy Services with IBM System z Servers § GC 35 -0033 Device Support Facilities User’s Guide and Reference, Release 17 62 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas References § “Global Mirror Whitepaper”, V 1 -3 By Nick Clayton, 13/09/2005 WP 100642 – http: //w 3 -03. ibm. com/support/techdocs/atsmastr. nsf/Web. Index/WP 100642 § Performance White Paper – http: //w 31. ibm. com/sales/systems/portal/_s. 155/254? nav. ID=f 320 s 260&geo. ID=All&prod. ID=Syst em%20 Storage&doc. ID=ditl. DS 8000 Perf. WPPower 5 § DS 8000/DS 6000 Copy Services: Getting Started WP 100905 – http: //w 3 -03. ibm. com/support/techdocs/atsmastr. nsf/Web. Index/WP 100905 § DS 8000 Disk Mirroring Licensing - Frequently Asked Questions – http: //w 31. ibm. com/sales/systems/portal/_s. 155/? nav. ID=f 220&geo. ID=AM&prod. ID=System%20 Storage&doc. ID=ditl. DS 8000 Mirroring. Lic. FAQ § Redbooks – www. redbooks. ibm. com or w 3. itso. ibm. com • Search on “DS 6000” & then “DS 8000” Also search on “copy services” – IBM System Storage DS 8000 Series: Copy Services in Open Environments, SG 24 -6788 -02 Redbook, published 29 November 2006 – IBM System Storage DS 8000 Series: Copy Services with IBM System z, SG 24 -6787 -02 Redbook, published 14 December 2006 63 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas References § Technical information on IBM Total. Storage Business Continuity Solutions: – IBM ITSO Redbook: Total. Storage Business Continuity Solutions Guide SG 24 -6547 -02 : • http: //www. redbooks. ibm. com/abstracts/sg 246547. html? Open – IBM ITSO Redbook: Total. Storage Business Continuity Solutions Overview SG 24 -6684 : • http: //www. redbooks. ibm. com/redbooks/pdfs/sg 246684. pdf § Technical ITSO Redpapers on Business Continuity Solutions: – REDP 4062 Total. Storage Business Continuity Solution Selection Methodology • This ITSO Redpaper describes an IT Business Continuity Solution Selection Methodology and how to apply it to your computing environment. There are several scenarios which demonstrate the application of this methodology. – REDP 4063 Planning for Heterogeneous Platform BC and DR • This ITSO Redpaper discusses how to plan for IT Business Continuity in a highly heterogeneous platform server and storage installation. Discussion is included of of IBM storage-based tools that can be useful to provide Business Continuity and Disaster Recovery in this diverse environment. • It is a 2005 version of this presentation 64 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas References § Technical ITSO Redpapers on Business Continuity Solutions: –REDP 4064 Small and Medium Business Considerations for IT BUsiness Continuity • Small and Medium Business (SMB) enterprises have IT Business Continuity needs and concerns similar to large enterprises; yet in other ways, SMB companies have key differences. This redpaper discusses those differences, and describes an overview of IT Business Continuity Solution selection in the SMB business environment. –REDP 4066 Networking Tutorial for IT Business Continuity Planners • Confused by terms such switches, routers, bridges, OC 3, DWDM, dark fibre? • This Redpaper is intended to enable the IT Business Continuity planner to better understand many commonly used networking concepts, in order to be able to better evaluate and select the appropriate networking components for your IT Business Continuity solution. 65 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas References § IBM Implementation Services for Geographically Dispersed Open Clusters (GDOC) – http: //www 03. ibm. com/servers/storage/solutions/business_continuity/continuous_availability/technical_details. h tml § IBM Geographically Dispersed Parallel Sysplex: – http: //www 03. ibm. com/servers/storage/solutions/business_continuity/continuous_availability/technical_details. h tml § IBM System Storage Business Continuity Solutions website: § http: //www-03. ibm. com/servers/storage/solutions/business_continuity/ § IBM Global Services Business Continuity and Recovery Services: § http: //ibm. com/services/continuity/ § IBM Business Continuity and Recovery Services – Your local IBM Global Services ITS representative 66 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas System Storage Enterprise Disk Practices Resources System Storage Business Continuity Solutions website § http: //www-03. ibm. com/servers/storage/solutions/business_continuity/index. html System Storage Technology Center § http: //www-03. ibm. com/system/storage/ § Storage Education http: //www-03. ibm. com/systems/education/cust/crossprod/custcp. html System Storage Interoperation Center § http: //www-01. ibm. com/systems/support/storage/config/ssic/index. jsp System Storage Services § http: //www-03. ibm. com/systems/storage/services/index. html Redbooks/Redpapers § http: //www. redbooks. ibm. com/redbooks. nsf/portals/Storage § The IBM Total. Storage DS 8000 Series: Concepts and Architecture (SG 24 -6452 -00) § IBM System Storage Business Continuity Solutions Overview (SG 24 -6684 -01) § IBM System Storage DS 8000 Series: Copy Services with IBM System z (SG 24 -6787 -02) § IBM System Storage DS 8000 Series: Copy Services in Open Environments (SG 24 -6788 -02) § IBM System Storage Solutions Handbook (SG 24 -5250 -06) White papers § 12/5/2020 IBM Storage Infrastructure for Business Continuity Solution § 12/5/2020 Global Mirror Technical Whitepaper 67 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas References § IBM System Storage Business Continuity Solutions website: § http: //www-03. ibm. com/servers/storage/solutions/business_continuity/ § IBM Global Services Business Continuity and Recovery Services: § http: //ibm. com/services/continuity/ § IBM Business Continuity and Recovery Services – Your local IBM Global Services ITS representative 68 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Following are the IBM links to presentations on the Enterprise Disk Mirroring Sales Kit on System Sales Web Site § IBM Three Site Enterprise Disk Mirroring Executive Summary § IBM Three Site Mirroring Competitive Marketing Summary for IBM* § IBM Two and Three Site Enterprise Disk Mirroring Overview § IBM Three Site Disk Mirroring for Open Systems Presentation Guide § IBM Three Site Disk Mirroring for z. Series Presentation Guide § IBM z/OS Global Mirror and Global Mirror Positioning Guide § IBM Two and Three Site Disk Mirroring Technical Presentation Guide § Deep Dive on IBM Global Mirror – from US Storage Symposium 2005 § IBM Disk Mirroring Update – from US Storage Symposium 2005 § IBM DS 8000 DS 6000 ESS Disk Mirroring Link Efficiency TCO Studies* § IBM Two and Three Site Mirroring Competitive Marketing Guide* 69 * IBM Confidential documents © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Trademarks The following are trademarks of the International Business Machines Corporation in the United States and/or other countries. CICS* Clear. Case DB 2* e-business logo FICON* GDPS* Hyper. Swap IBM* IBM e. Server IBM logo* IMS* MQSeries* On Demand Business logo Parallel Sysplex* Rational* System z 9 Tivoli* Web. Sphere* z/OS* z/VM* z. Series* * Registered trademarks of IBM Corporation The following are trademarks or registered trademarks of other companies. Intel is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States, other countries or both. Microsoft is a trademark of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. * All other products may be trademarks or registered trademarks of their respective companies. Notes: Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's 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 improvements equivalent to the performance ratios stated here. IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply. All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics will vary depending on individual customer configurations and conditions. This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without notice. Consult your local IBM business contact for information on the product or services available in your area. All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. Information about non-IBM products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the performance, compatibility, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. Prices subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your geography. 70 © 2009 IBM Corporation
IBM Advanced Technical Support - Americas Disclaimers Copyright © 2009 by International Business Machines Corporation. No part of this document may be reproduced or transmitted in any form without written permission from IBM Corporation. Product data has been reviewed for accuracy as of the date of initial publication. Product data is subject to change without notice. This information could include technical inaccuracies or typographical errors. IBM may make improvements and/or changes in the product(s) and/or programs(s) at any time without notice. Any statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business. Any reference to an IBM Program Product in this document is not intended to state or imply that only that program product may be used. Any functionally equivalent program, that does not infringe IBM’s intellectually property rights, may be used instead. It is the user’s responsibility to evaluate and verify the operation of any on-IBM product, program or service. THE INFORMATION PROVIDED IN THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IBM EXPRESSLY DISCLAIMS ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IBM shall have no responsibility to update this information. IBM products are warranted according to the terms and conditions of the agreements (e. g. , IBM Customer Agreement, Statement of Limited Warranty, International Program License Agreement, etc. ) under which they are provided. IBM is not responsible for the performance or interoperability of any non-IBM products discussed herein. The provision of the information contained herein is not intended to, and does not, grant any right or license under any IBM patents or copyrights. Inquiries regarding patent or copyright licenses should be made, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504 -1785 U. S. A. 71 © 2009 IBM Corporation
- Slides: 71