Protec TIER on IBM i May 2011 Bob

® ™ Agenda – Protec. TIER on IBM i • Product Overview – What does it do? – Deduplication Algorithms – Product Family – Protec. TIER on IBM i – where it fits – Protec. TIER on IBM i – how it attaches – Protec. TIER on IBM i - sizing – Next Steps 2 © 2011 IBM Corporation

® ™ Protec. TIER Product Overview 3 © 2011 IBM Corporation

® ™ Protec. TIER Vision and Design Criteria 1. Data-agnostic factoring of up to 25 times or more 2. Unmatched performance up to 1000 MB/s or more 3. Unequaled scalability: up to 1 PB physical data 4. Enterprise-class data-integrity: Not hash-based 5. Simple, non-disruptive deployment 6. Supported in most hardware and software environments No other dedupe technology meets all these criteria! 4 © 2011 IBM Corporation

® What does Protec. TIER do? ™ Protec. TIER IP Replication IBM i TS 3500 Optional duplication to physical tape Ohio Minimized bandwidth since data is de-dup’d before sending (at local or remote site) New York IBM i Protec. TIER Virtual Tapes C Disk What is De. Duplication? B A C A B A Local Saves to Virtual Tape with De-dup C B A C A B A B C B A A A B 5 © 2011 IBM Corporation

® ™ Hyperfactor Deduplication in Action New Data Stream Hyper. Factor Repository Memory Resident Index Disk Arrays SAN Switch TS 7650 G Existing Data “Filtered” data IBM i Servers 6 © 2011 IBM Corporation

® ™ Deduplication Algorithms - Types Content Aware Hash Based Hash Value • Assumes the best candidate to Text de-dup against is an object with similar attributes (eg file name, file type) • De-dup ratios are lower since even a tiny difference within the boundary causes the match to fail • Sepaton Protec. TIER Hyper. Factor Pointer • Hash table grows as more backup data is stored • As the repository fills, backup speeds decrease since it takes longer to check the bigger table • Eventually the Hash Table can’t fit in memory and backup speeds decrease seriously • Hence this algorithm is only suited to smaller devices: it doesn’t scale well • Data Domain, Falcon. Stor • Very fast algorithm since it processes backup stream to find possible matches then offloads work to disk to confirm the match • Algorithm can index 1 PB of physical disk using a 4 GB index that fits in memory, hence no performance degradation as the repository grows • Hence scalable for large repositories 7 © 2011 IBM Corporation

Production Customers Deployment Results ® ™ 8 © 2011 IBM Corporation

® ™ Deduplication Algorithms – Post vs Inline Post Processing Deduplication • Backups run first without de-dup • Separate de-dup algorithm runs thereafter • Requires extra disk space to hold the interim full-sized copy of the backup • Used when the de-dup algorithm is not fast enough to run inline Inline De-Duplication (eg Hyper. Factor) • De-dup runs as part of backup process • Uses less disk • Once save is done, the entire process is done • Only possible with a fast de-dup algorithm like Protec. TIER Hyper. Factor 9 © 2011 IBM Corporation

® ™ IBM TS 7600 Protec. TIER® Deduplication Family New in July 2010 R c. TIE Prote on 10 TS 76 uplicati s Ded e Expres ianc Appl ER ec. TI Prot ateway 50 G G TS 76 lication p Dedu TIER rotec liance 50 P p TS 76 ation Ap c pli Dedu Good Performance Better Performance Highly Scalable Larger Capacity Highest Performance Largest Capacity Highest Performance Largest Larg Capacity High Capacity Largest Capacity High Availability Flexible Storage Scalable Low cost Good Performance Entry Capacity Very Low cost Ca y an pacit d Single Node Up to 85 MB/sec 5. 9 TB (5. 5 Ti. B) useable 4. 4 TB (4. 0 Ti. B) useable Up to 100 MB/sec 7 TB (6. 3 Ti. B) useable Up to 250 MB/sec 18 TB (15. 8 Ti. B) useable rm P e rf o ance Single Node Up to 500 MB/sec 36 TB (31. 5 Ti. B) useable Single Node Active-Active Cluster Up to 900 MB/sec Up to 500 MB/sec Active-Active Cluster Up to 1500 MB/sec 1 PB useable 36 TB (31. 5 Ti. B) useable Nominal Space Available = “useable” space * Hyper. Factor Ratio 1 TB = decimal TB = 1, 000, 000 bytes or 1, 000 GB (i. e. 10^12 bytes) 1 Ti. B = binary TB = 1, 099, 511, 627, 776 bytes or 1, 024 Gi. B (i. e. 2^40 bytes) 11 © 2011 IBM Corporation

Protec. TIER Details ™ ® LTO-2 & LTO-3 Emulation TS 7650 Appliance Notes: TS 7650 Gateway TS 7610 Appliance (1) IBM i has a max of 32 drives in a virtual library attached to a given server, and 92 drives total in a virtual library (2) IBM i has a max of 4096 cartridge locations in each library (slots + drives + IO slots + grippers) TS 7610 Appliance TS 7650 Gateway # nodes 1 1 -2 Max Throughput 80 MB/sec 100, 250, 500 MB/sec Up to 1500 MB/sec with 2 nodes Repository (Physical) 4. 4 or 5. 9 TB 7, 18, 36 TB Up to 1 PB Max # Virtual Libraries 4 12 16 Max # Virtual Drives 64 256 8, 192 128, 000 500, 000 4 if TS 7610 is the hub 12 if TS 7650 is the hub 12 12 (1) Max # Virtual Cartridges (2) Replication – Max Spokes per Hub 12 © 2011 IBM Corporation

® ™ Customer Profile for each Appliance Configuration § Ideal Customer for 7 TB Protec. TIER Appliance § 1 TB or less incremental backups per day § 1 -3 TBs full backups each week § Experiencing average data growth § Needs a cost effective solution § Ideal Customer for 18 TB Protec. TIER Appliance § 3 TBs or less incremental backups per day § 3 -6 TBs full backups each week § Experiencing rapid data growth § Needs good performance to meet backup window § Ideal Customer for 36 TB Protec. TIER Appliance § 5 TBs or less incremental backups per day § 5 -12 TBs full backups each week § Additional growth expected § Meeting the Backup window is an issue - higher performance needed * Note: These general guidelines are based on the backup workload that best fits each appliance configuration Please use Capacity Planning Tool to accurately size a solution to meet customer’s specific requirements 13 © 2011 IBM Corporation

® ™ IBM’s LTO Technology Roadmap 14 © 2011 IBM Corporation

® ™ Protec. TIER For IBM i 15 © 2011 IBM Corporation

® ™ Protec. TIER on IBM i – Where does it fit? Our Niche – Protec. TIER IP Replication For customers who are moving their tapes offsite via truck today and would like a safer, more automated solution IBM i Protec. TIER Our Niche – Tired of Handling Tapes? IBM i Our Niche – Tiny LPARs Note: If the customer already has an HA/DR solution that replicates his data to his remote site, then that will likely provide a more economical solution for remote tape: • IBM i Software-based Replication (eg i. Cluster, MIMIX, Visions, i. Tera, etc) • External Disk Copy Services • IBM i Geographic Mirroring (formerly Cross Site Mirorring or XSM) For customers where a tape cartridge is much bigger than needed Protec. TIER. . . VIOS / NPIV 16 © 2011 IBM Corporation

® ™ Virtual Tape on IBM i – Questions to Ask Your Vendor Overall Speed and Single Stream Speed Virtual Tape Devices shine when they can run a large number of mediumspeed backup streams. IBM i customers often need a small number of very fast streams. Be sure to understand the single stream performance provided to make sure your Virtual Tape Device will meet your needs IBM i Single Stream performance depends on the VTL disk type/amount Backup Scheduling LPAR 11 pm 11: 30 pm Midnite 12: 30 am 1 am 20 160 200 200 IBM i 01 IBM i 02 Protec. TIER 40 -90 MB/sec per stream TS 7650 Protec. TIER Full box Save capacity is 1500 MB/sec with 2 nodes IBM i 03 IBM i 04 Total MB/Sec Draw a Backup Gantt Chart to check the MB/sec and # streams at your peak Non-Infinite Resources Current Technology Physical Drives run at 60 -280 MB/sec per stream (umix / largefile) Although virtual tape if flexible, remember the resources aren’t infinite 17 © 2011 IBM Corporation

® ™ Protec. TIER on IBM i – Support and Testing Supported with: • IBM i V 5 R 4 onwards • Any IBM i fibre card supported on your server • BRMS is strongly recommended • Tested with the same COMPREHENSIVE Test Buckets used for regular tape drives IBM Protec. TIER is the ONLY External Virtual Tape product that is tested and supported by IBM Rochester 18 © 2011 IBM Corporation

® ™ Protec. TIER Attachment to IBM i - Details § Fibre cards that use an IOP (fc 2765, 5704, 5761) § IBM i V 5 R 4 M 0 onwards § TS 7650 Protec. TIER Code Levels § Min for Local Backups: V 2. 2. 3. 0 § Min for IP Replication: V 2. 3. 0 § Fibre cards that don’t use an IOP (fc 5749, 5774/5276, 5735/5273, 5708 FCo. E + Blades fibre cards) § IBM i V 6 R 1 M 1 onwards with the following PTFs § IBM i 6. 1. 1: MF 49234 + pre-reqs § IBM i 7. 1. 0: MF 49235 + pre-reqs § POWER 6 or POWER 7 system § TS 7650 Protec. TIER Code Level See ions ict estr xt few R e on n ages p § V 2. 4. 1. 0 Server Code § V 2. 4. 3. 0 PT Manager Code (GUI) § BRMS is recommended since TS 7650 presents as a tape library 19 © 2011 IBM Corporation

IBM i IOPless Support for Protec. TIER Restrictions ® ™ Restriction #1: IBM i alt-IPL (reload) Restriction #2: TS 7650 IPL with VIOS (this only applies to IOPless fibre cards, not the older IOP’d cards) VIOS IBM i SAN Switch TS 7650 Node 1 Virt Drive 0 Virt Drive 2 SAVSYS Tape Virt Drive 3 Virtual Library To D-IPL your IBM i, use TS 7650 LUN masking so the adapter card can only see a single virtual drive (the one with the SAVSYS in it) TS 7650 Other Tape in VIOS Zone If TS 7650 is attached to VIOS, remove TS 7650 port(s) from the VIOS SAN Zone before IPLing the TS 7650, otherwise it may disrupt other devices 21 © 2011 IBM Corporation

® ™ BRMS DUPMEDBRM Compaction PTF TS 7650 Virtual Tape Saves are not compacted so take 3 x as much virtual media (gained back with dedup) § Part of June 2010 BRMS PTF § V 5 R 4: SI 38733 § IBM i 6. 1: SI 38739 § IBM i 7. 1: SI 38740 IBM i TS 3500 With the PTF, DUPMEDBRM can request compaction so uses less media With PTF Before the PTF, dups used the same compaction parameter as the source volume, so more physical media was needed § Exposes the COMPACT parameter so you can compact the physical volumes when you dup from Protec. TIER Before PTF § Behavior: § V 5 R 4: control via Data Area § Q 1 ADUPCOMP in QTEMP can be set to *FROMFILE, *YES, *NO § IBM i 6. 1 / 7. 1 § COMPACT(*YES) is available § help text via web § For new IBM i 6. 1 auto-dup feature, need to change command default on DUPMEDBRM to *DEV § Future releases: § COMPACT(*YES) will be available with regular help text 22 © 2011 IBM Corporation

® ™ Sizing Protec. TIER For IBM i 23 © 2011 IBM Corporation

® ™ Protec. TIER on IBM i – Designing / Sizing Get the Protec. TIER on IBM i Introduction and Questionnaire IBMers: Partners: Simple Environment: 1 -2 hours of work http: //w 3 -03. ibm. com/support/techdocs/atsmastr. nsf/Web. Index/WP 101536 http: //partners. boulder. ibm. com/src/atsmastr. nsf/Web. Index/WP 101536 Build a Repository Sizing Spreadsheet Complex Environment: Several days of work Build a Backup Schedule Gantt Chart (to figure out the peak MB/sec) LPAR GB in Save Iterations Kept GB in repository LPAR IBM i 01 200 GB 3 600 IBM i 01 IBM i 02 350 GB 7 2450 IBM i 02 IBM i 03 100 GB 3 300 IBM i 03 IBM i 04 575 GB 12 6900 IBM i 04 10250 Total MB/Sec Total 11 pm 11: 3 0 pm 60 20 mid nite 12: 30 am 1 am 60 60 60 80 80 80 60 60 200 20 80 80 20 160 200 Then ask the Protec. TIER FTSS to tell you how many disk arms you need 24 © 2011 IBM Corporation

® ™ Next Steps 25 © 2011 IBM Corporation

® ™ If you would like to consider Protec. TIER for your shop … Detailed Protec. TIER Presentation Backup Environment Review Attend the Protec. TIER Hands-on Workshop Ask your Protec. TIER team to engage an IBM i / Protec. TIER specialist to review your backup environment with you • Two-Day Hands-on Workshop in Gaithersburg, Maryland. • Runs 1 -2 times per month • No charge to attend Text Invite your local IBM Protec. TIER Sales Team to give you a moredetailed presentation 26 © 2011 IBM Corporation

® ™ Questions? 27 © 2011 IBM Corporation

® ™ Deduplication Market at a Glance DD 880 DEDUP TECHNOLOGY Protec. TIER with Hyper. Factor Rock. Soft Hash-based ! Potential Hash DXi 7500 Rock. Soft Hash-based Deduplication üBlock Level ! Potential Hash ü Byte-level diff ! Post process See Note (3) üBlock Level Ø File Level See Note (4) Deduplication PERFORMANCE collision ü Single node performance 500 MB/s ! 300 MB/s üDual node Cluster performance 1000 MB/s !Clustering not ! 130 MB/s !Clustering not üNo disk staging ! Staging area > available RESOURCE UTILIZATION for a 1 PB repository See Note (1) ! Potential Hash collision üInline üOnly 4 GB RAM needed Delta. Stor üBlock Level comparison area required SIR Hash-based S 2100 -ES 2 üInline ü Byte-level diff üNo disk staging VTL 700 area required available than the size of largest full backup collision üBlock Level ! 188 MB/s See Note (2) comparison ! 160 MB/s See Notes (5 -6) !Clustering with See Notes (7 -8) ! Staging area > See Notes (9 -10) Global Dedupe not available than the size of largest full backup !Over 300 GBs of RAM! Ø Staging area > twice the size of largest full backup ü 24 GB of RAM Not See Note (11) hash based 28 © 2011 IBM Corporation

® ™ Deduplication Market at a Glance Protec. TIER with Hyper. Factor DD 880 Rock. Soft Hash-based PRODUCT STABILITY ü IBM in business for nearly 100 years üProtec. TIER in production since 2006 üOver 25 PBs of in production CAPACITY-SCALABILTY üAcquired by EMC üIn production since 2006 üMany small systems in production ü Single system can scale to 1 PB capacity ! 58 TB Maximum üUp to 16 virtual tape !Limits not published !Limits not libraries üUp to 512 virtual tape drives üUp to 512, 000 virtual tape cartridges useable capacity published MEETS ENTERPRISE REQUIREMENTS? ü YES ! NO DXi 7500 Rock. Soft Hash-based S 2100 -ES 2 VTL 700 SIR Hash-based Delta. Stor ! Over $400 million ! Small struggling Ø Acquisition or ! Post process ! GA October 2008 ! Very few small ! GA May 2008 in debt customers company customers !Limited by rapid hash table growth failure imminent Ø Almost no deduplication in production See Note (12 -13) See Note (14 -15) ! Limited by huge storage requirements üUp to 64 virtual üUp to 128 virtual üUp to 192 virtual tape libraries tape drives üUp to 130, 000 virtual cartridges drives üUp to 64, 000 virtual cartridges tape libraries üUp to 160 virtual üUp to 1024 virtual üUp to 192 virtual ! NO tape drives üUp to 5. 3 million virtual cartridges ! NO 29 © 2011 IBM Corporation