Migration from a TS7740 to a TS7700T considerations

Transcription

1 Migration from a TS7740 to a TS7700T considerations Katja Denefleh Katja.Denefleh@de.ibm.com

2 Why this presentation? As you all know (and will here later) you can do a frame replacement. All data will be migrated by using the physical backend. So, why a separat presentation for this topic? Because there is an easy way... But that will not exploit the full capabilities of the TS7700T Or A more complex way... This presentation will give you an overview what you could consider during the migration to exploit the capabilities. 2

3 The easiest way a 1:1 migration Do a 1:1 migration means that you define one large CP1 after the installation, and all data belongs to the CP1 tape partition. Only PG0 / PG1 will still be used. Very simple, very easy, very quick Result: No CP0 used No premigration possibilities / capabilities are used No second level of cache management is used 3

4 Why to consider a complex way Because the TS7700T offers you capabilities which were not available in the TS but can help to improve your tape production: Tape partions Maybe you are sharing the Grid between different participants with different requirements Production / Development / Test Different customers Different applications like OAM / HSM ML2/ HSM Backup / DB2 or IMS Logs / Dumps / real Batch Delay premigration Second level of cache management to increase read hit Run longer in peak period Supression of backend activity for short lifetime data The following slides show some theoretical example how the exploitation of the TS7700T can change your Read Hit / Recall / Backend behavior. Growth is already included in the numbers. 4

5 Example setup: TS7760T with 4 drawers = approx 125 TB Total volumina all compressed data: Data Total volumina in TB Expectation Total in cache Production OAM 30 Forever 30 Production HSM ML2 50 As much as possible, minimum 20 TB 20 Production DB2 xx At least 14 days ( 1 TB per day) 14 Production rest PG TB daily throughput Development OAM Development HSM ML2 80 As much as possible, minimum 35 TB 35 Development DB2 Xx At least 5 days (1 TB per day) 5 Develeopment Rest PG TB daily throughput Test 30 1 TB dayly throughput Total 125 TB (11 TB PG0 daiy) GB write daily : 21 TB - in the timeline between 20:00 and 03:00 Production 10 TB (5 TB PG1, 5 TB PG0) Development 10 TB (5 TB PG1, 5 TB PG0) Test: 1 TB 5

6 Example: easy way The total throughput of 20 TB a day means that without cache management, the cache is filled up and reused after 6 days. With the existing cache management, this extends for PG1 to 12 days. The overall expectation can not be met: DB2 for 14 days HSM / OAM are both using PG1 so OAM can not be protected Development and Production OAM / HSM will use both PG1 no definitive protection that the requeted minimum are kept In addition, the 21 TB exhausts the FC The timeline of 7:00 hours and the needed throughput capabilities will not allow to run premigration in full speed. 6

7 Example Alternative 1 Data Total volumina in TB Expectation Total in cache Partition Premigration Delay Production OAM 30 Forever 30 0 Na Production HSM ML2 50 As much as possible, minimum 20 TB Production DB2 20 At least 14 days ( 1 TB per day) hours hours Production rest PG TB daily throughput 1 None Development OAM Na Development HSM ML2 80 As much as possible, minimum 35 TB Development DB2 10 At least 5 days ( 1 TB per day) hours hours Develeopment rest PG TB daily throughput 2 none Test 30 1 TB daily throughput Total 125 TB (11 TB PG0 daiy) CP0 PROD OAM / DEV OAM 30/10 40 Prefer keep 45 Partition size CP1 PROD HSM + Prod rest 20+5 PG1 / PG0 25 CP2 DEV HSM + DEV rest 35+5 PG1 / PG0 40 CP3 PROD DB2 14 PG1 14 CP4 DEV DB2 5 PG1 5 Total: 129 7

8 Example: Alternative 1 Pros and Cons Pros: For the most of the applications the requirements can be fullfilled. No application can harm the needs of the others. Delay premigration will allow to run longer on peak. PG0 is not delayed, so that this data will leave the cache as soon Premigration has occured. Cons: During the original sizing, the necessary freespace in the CP0 was not considered. Therefore 5 TB are mising so we can not fulfill all our targets. All tape partitions are exactly on the edge and the CP0 has not enough resources to allow borrowing. So any change in the workload can impact our read hit. CP0 is small so autoremoval needs to be enabled 8

9 Possible other alternatives OAM data is written to CP5: Pro: Possible growth can be handled - no need (and risk) of autoremoval Cons: CP0 still need 3 TB at least to avoid out of conditions CP0 still small borrow not feasible DB2 and HSM in the same partition Pro: Two partition less Cons: HSM and DB2 will compete - requirements will not be met 9

10 Possible other alternatives DB2 and HSM in the same partition but now DB2 is delay premigration to 14 days for PROD or 5 days for DEV. Pro: Two partition less (remember: Tape partitions can not borrowed within each other) Workload changes can be better compensated Cons: DB2 workload only on cache All PG0 workload in 1 big partition: Bad idea, this partition will be empty most of the time. 10

11 How to get a good tape partition plan? 1. Know your environment: 1. RMM or other TMS delivers you the overall amount of stored data for different HLQs. 2. Use SMF or VMA to get an idea for your workload profile 3. Know your requirements for the individual data (especially your READ!) 4. Understand your READ profiles (especially for your own real batch / SMF/ data mining) if you dont have any other tools to analyse your read, use TAPEWISE 5. Know the requirements for your DB2 logs (quick restore...) 2. Invite IBM:...even that means you have to deliver SMF IBM sizing tools allow a deep analysis of the given SMF sentence 2. Dont believe that IBM can work out a sizing without your input 1. Requirements 2. Expectations 3. Copy Modes / Distances / 4. Answer questions (not all workloads are selfexplaining) 11

12 The Does, and the donts Does: Make a plan, but be flexible to adjust Start with smaller CPx and define your usual planned workload growths TB first to the CP0. It is much easiert to enlarge a CPx then to make it smaller. Introduce ALL the planned Tape Partitions in one step best plan before the frame replacement also the changes for the Storage Classes and SMS. If you are uncertain lets discuss. Dont: There is no Step by Step introduction for the amount of Tape partitions. Dont move the old content, let the old content in the CP1. Make the CP1 not to small because the old content is bound to the CP1.??????? Make the CP0 to small borrow is only allowed from CP0. Less is more... Introduce only the number of Tape partitions you need. 12

13

14

15 Disclaimers Copyright 2015 by International Business Machines Corporation. No part of this document may be reproduced or transmitted in any form without written permission from IBM Corporation. The performance data contained herein were obtained in a controlled, isolated environment. Results obtained in other operating environments may vary significantly. While IBM has reviewed each item for accuracy in a specific situation, there is no guarantee that the same or similar results will be obtained elsewhere. These values do not constitute a guarantee of performance. The use of this information or the implementation of any of the techniques discussed herein is a customer responsibility and depends on the customer's ability to evaluate and integrate them into their operating environment. Customers attempting to adapt these techniques to their own environments do so at their own risk. 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. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products in connection with this publication and cannot confirm the accuracy of 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. 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 U.S.A. 15

16 Trademarks The following terms are trademarks or registered trademarks of the IBM Corporation in either the United States, other countries or both. IBM, GDPS, Spectrum Storage, Spectrum Archive, Spectrum Scale, System Storage, System z, Virtualization Engine Linear Tape File System, Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries. Other company, product or service names may be trademarks or service marks of others 16