The New and Improved DS8880 Family

Transcription

1 The New and Improved DS8880 Family Nick Clayton IBM Systems Development

2 Agenda DS8880 Family Review and new DS8888 DS8000 2Q 2016 Announcement zsynergy Enhancements Small Extents and Thin Provisioning for z/os FlashCopy to Thin Provisioned Volumes Other Enhancements 2

3 The DS8880 family New! 3 DS8884 Fast Hybrid-Flash Block Storage Lowest entry cost for midrange enterprises Hybrid Flash 256 GB Cache (DRAM) 64 16Gb FICON or FCP Ports 768 HDD/SDD flash cards 19 Rack Single phase Power DS8886 Faster Hybrid-Flash Block Storage High performance for large enterprises Hybrid Flash 2 TB Cache (DRAM) Gb FICON or FCP Ports 1536 HDD/SDD s flash cards 19 Rack Single / three phase Power DS8888 Fastest All-Flash Block Storage Industry s fastest T1 Subsystem All-flash 2 TB Cache (DRAM) Gb FICON or FCP Ports 480 Flash cards 19 Rack Three phase Power

4 DS8880 R8.1 and R8.1.1 Announcements DS8888 All Flash Array - Model 982 and 98F Expansion Unit Up to 2.5M IOPS and ~200 microsecond latency for typical workloads Three phase power option Supported on DS8886 (single/three phase) and DS8888 (three phase) DS8000 Copy Services Manager (CSM) feature on the HMC RAID 10 support for High Performance Flash Enclosures (HPFE) New drive capacity options for DS8870, DS8884 and DS TB 10K rpm HDD 6 TB 7.2K rpm HDD 800 GB Flash Cards (R8.1.1) Functional enhancements Small Extents Thin Provisioning for CKD devices SuperPAV DB2 Castout Accelerator SSD Home Tier and Warm Promote for Easy Tier 4 Native LDAP support via CSM KMIP support for Encryption Key Management Event notification via syslog User interfaces for PE package and statesave offload Alternative remote access solution - RSC Media error recovery enhancements for PPRC secondary devices

5 zsynergy : SuperPAVs 5 Today Alias devices can be shared only within an LSS which means that the number of aliases must be sized individually for each LSS. SuperPAVs will enable alias devices to be shared among multiple LSS so long as The devices are assigned to the same DS8000 server (odd/even LSS) The devices share a path group on the z/os system Using SuperPAVs will provide benefits especially with a large number of LPARs or many LSS sharing a path group Any existing IOSQ peaks should reduce as a larger pool of aliases are available Existing LSS can have more capacity added without increasing the number of aliases New LSS can be planned to have a larger amount of capacity per alias There is still a need for at least one base device per LSS so with this release it is not possible to define an alias only LSS

6 zsynergy: DB2 Cast Out Accelerator DB2 writes long chains of discontiguous pages when it performs castout processing which typically contain multiple imbedded locate record domains. Prior to the DB2 Cast-out Accelerator each IO in the chain is synchronized individually affecting both simplex and Metro-Mirror performance. The DB2 Cast-out Accelerator function eliminates the synchronization between each Locate Record domain. Therefore, it provides significant performance and efficiency for DB2 castout write processing both in the DS8880 as well as the zsystems Channel Subsystem. This is a zhpf only function available with R8.1 on all DS8880 models. z/os Media Manager support is provided in APAR OA49684 for z/os 1.13 onwards Other Media Manager applications such as ZFS that do long chains of discontiguous writes can also benefit from this code enhancement. 6

7 DB2 Castout Accelerator Performance without Replication For a typical DB2 castout write operation that transfers 64 discontiguous 4k pages, internal lab experiments show as much as a 46% reduction in response time with a complimentary increase of 81% in throughput when compared to performance of the same IO prior to the DB2 Cast-out Accelerator function. 7

8 DB2 Castout Accelerator Performance with Replication Even more impressive is Metro-Mirror (MM) performance behavior for same IO operation. Lab experiments for Metro-Mirror revealed a 83% reduction in response time at 10km while delivering 510%(5.1x) more throughput compared to the performance of the same IO without the DB2 Castout Accelerator function. 8

9 Small Extents Provides an option for a smaller extent size on DS8000. Larger memory sizes on next generation systems allow for smaller extent allocation without performance penalties Required for more efficient thin provisioning implementation and optimised for z/os Also improves efficiency of tiering functionality and copy services Improves balance among rank resources even at very short time intervals improving performance stability even for very bursty workloads Allows for use of Space Efficient FlashCopy with Global Mirror with improved performance compared to the current Track Space Efficient FlashCopy Significant reduction in cost for high performance Global Mirror environments 9 IBM Confidential

10 Small Extent Implementation An extent pool can be defined as having either large or small extents The extent size cannot be changed once the pool is created but ranks removed from one pool will be reformatted when added to a pool with a different extent size Volumes cannot be migrated between pools of different extent sizes FlashCopy targets can be deleted and redefined in a new pool to migrate them For Global Mirror journals and testing FlashCopy this may be the most appropriate method Data Type Large Extent Size Small Extent Size Small extents per large extent CKD 1113 cylinders 21 cylinders* 53 FB 1GB 16MB *CKD Extent size is the same as the dataset allocation unit on EAV

11 DS8880 scalability with large and small extents Using small extents results in higher memory requirements for metadata and as a result overall DS8880 scalability is reduced when using small extents especially when combined with a smaller cache size When using a mix of large and small extents the large extent volumes will use a small proportion of the available extents. Only 8Mi extents are needed to support 8PiB of capacity which is the DS8000 physical capacity limit prior to small extents System Memory Maximum number of physical extents Maximum number of volume extents Max physical size small extents (FB/CKD) Max virtual size small extents (FB/CKD) <= 256GiB 32Mi 64Mi 512 / 560TiB 1024 / 1120TiB >= 512GiB 128Mi 256Mi 2024 / 2240TiB 4096 / 4480TiB 11

12 Choosing Large or Small extents Thin provisioning will be significantly more efficient with small extents and so clients interested in this for host volumes or FlashCopy should choose small extents Maximum capacity of a DS8880 is reduced with small extents although not in most practical scenarios Some specific workloads could perform better with large extents although most realistic production workloads will be equal or better with small extents Workload will be spread at a more granular level with small extents so bursty workloads and small numbers of sequential streams will likely be better spread Sequential destage will be somewhat less efficient with small extents so individual rank sequential write throughput will be somewhat reduced ~10-15% expected The expectation is that the use of small extents will become the standard 12

13 Easy Tier enhancements for Small Extents The number of small extents that can exist means that it is not practical to monitor each extent individually as Easy Tier does today For Small Extents we introduce the concept of a Track Group which is a contiguous LBA range of small extents. For R8.1 the track group size is equivalent to a large extent Easy Tier will contain statistics for each Track Group and for every tier that the Track Group is present on In order to further optimize efficiency Easy Tier will also keep track of Idle Extents at the Small Extent level. These are extents which have not had any IO within a defined time period. The Idle Extents in a Track Group will not be promoted with the rest of the Extents The Idle Extents for all Track Groups will be demoted first 13

14 Easy Tier Example with Small Extents Idle extents with no IO are tracked and will be treated differently from the other extents within the extent group Migration decisions are made on the basis of all extents in an extent group that are on a particular tier. For fully provisioned volumes nonidle extents will tend to be on a single tier n n n n n Hot Extent group Warm Extent group Cold Extent group Idle Extent tracked separately Easy Tier aggregates performance counters to a single entry for each tier that is being used by an Extent Group. These are incorporated into the Easy Tier history statistics with one entry per tier.. n n n 14 Extent Group The DS8000 maintains performance counters for each small extent on a volume. If the volume is thin provisioned not all extents may exist

15 Other Easy Tier enhancements 15 SSD Home Tier As the price of Flash/SSD reduces clients are configuring larger percentages of Flash in tiered environments. Given a larger percentage of Flash the initial allocation of extents on the Enterprise tier does not make sense SSD Home tier will change Easy Tier behaviour in the following ways Extent allocation will be performed on tier0 then tier1 then tier2 Cold Demotion will be performed from tier0 to tier1 Additional space will be reserved on tier0 for thin provisioned volume allocations Warm Promote Environments using Nearline drives have occasionally seem problems where there is a significant amount of data on Nearline that suddenly becomes active. The same could also apply with larger Enterprise drives especially with a larger percentage of Flash/SSD Warm Promote will act in a similar way to Warm Demote and if the 5 minute average performance shows a Nearline (or Enterprise) rank is overloaded will immediately start to promote extents until the condition is relieved. As the Nearline performance profile is somewhat conservative this is quite likely to occur if there is any significant activity on Nearline ranks but for Enterprise ranks is less likely

16 Thin Provisioning for ECKD in DS8000 Once allocated provides the same performance as fully provisioned devices for both random and sequential workloads Allocating writes require metadata updates as each extent is allocated A001 DB1234 A002 SPARE Unallocated extents do not have to be copied with replication functionality or migrated with Easy Tier 1 Storage Pool Allow for sharing of spare storage capacity across sysplexes or between storage groups SSD drives Simplify configuration by standardizing device sizes without wasting space Unused/unallocated devices can be included in replication configuration avoiding frequent changes GB drives 4 300GB drives 16 3TB drives

17 z/os Software Support for Thin Provisioning DFSMS pool utilization alerts for extent pools (OS48710, OA and OA48709) With z/os 2.2 DFSMS also provides storage group utilization alerting TDMF can migrate from thick to thin volumes using the FASTCOPY option and will use FASTCOPY by default if the target device is ESE (OA50453) ICKDSF will perform space release of a thin provisioned volume when the volume is initialized (PI47180) IDCAMS reports enhanced to show thin provisioning statistics (OA47811) DSS Move will request that DS8000 pre-allocates extents when using FlashCopy for the move to prevent data loss if the storage pool runs out of extents (OA48707) 17

18 TDMF for thick to thin migration TDMF provides online data migration capabilities at the volume level FASTCOPY option in TDMF will only copy allocated cylinders when migrating volumes. Master ZOSA Agent 1 ZOSV FICON Director Agent 2 ZOSW With the thin provisioning support APAR FASTCOPY will be used automatically if the target is thin provisioned S Thick To Thin Migration T 18

19 Copy Services and Thin Provisioning Picture H1 Metro Mirror H2 Flash Copy FC Metro Mirror primary is Extent Space Efficient with mix of allocated and unallocated extents Only allocated extents are copied from primary to secondary and all extents are freed on initial copy Extents are allocated on FlashCopy target only when tracks copied with Copy on Write or Background Copy 19

20 Copy Services and Thin provisioning PPRC is supported only for like volume types (full to full / thin to thin) PPRC establish will release space on target and allocate according to source FlashCopy is supported any to any Space release will be performed on full volume establish and withdraw (if specified) Global Mirror and FlashCopy to Thin Provisioned volumes is discussed later Remote Pair FlashCopy does not release space on secondary Full to Thin with preserve mirror does not make sense today Thin to Thin with preserve mirror is fine but still does not do space release XRC is not prohibited but has no awareness of thin provisioning If you use ESE on a secondary it will become fully provisioned unless QuickCopy is used for the XRC Initial Copy 20

21 Statement of Direction for Thin Provisioning The current plan and direction of IBM is to provide a DS8000 interface for z/os environments that will enable any extents on a volume that only contain empty space to be freed on the back-end storage and the space returned to the pool. R8.1.1 and ICKDSF provide the first stage for this space release function The plan also includes enabling space release with copy services to allow the use of the space release on replicated devices and to free space where appropriate on the replicated copies. IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remain at our sole discretion. 21

22 FlashCopy to Thin Provisioned Volumes With small extents the space efficiency of FlashCopy to a Thin Provisioned volume will be significantly improved although worse than Track Space Efficient (TSE) which had a single track allocation unit vs. 21cylinders/16MB for Thin Provisioning with small extents Capacity usage for sequential write workloads will generally be similar Capacity usage for random write workloads could be significantly worse. However most workloads have significant skew in random writes Performance will be significantly better than TSE which did not have any destage grouping for writes to the source and the Copy Source to Target activity was always done a single track at a time The amount of destage grouping will be slightly less than FlashCopy with large extents as each extent will have partial strides at the beginning and/or end Smaller extent size will mean that for typical chaotic client workloads the workload balance is more balanced even for short bursts of writes 22

23 Global Mirror performance with Thin Provisioned FlashCopy Journals 23

24 DS8000 Metadata DS8000 has two types of Metadata Global Metadata stored on three ranks for redundancy Volume Metadata stored on extents in the same extent pool as the volume Global Metadata is read into memory at IML and then is only accessed for updates following this. Global Metadata must be updated for extent allocation, volume creation and other significant configuration changes Volume Metadata contains a range of information which can be both read and written and includes: Copy Services Bitmaps CKD Track Format Information 24

25 Optimizing performance with FlashCopy ESE Having three HPFE or DA with SSD will mean that Global Metadata is on Flash and extent allocation will be significantly faster As Global Metadata updates are serialised one or two HPFE/DA will still provide benefits Having at least 10% Flash/SSD in the extent pool will mean that volume metadata is on this tier and will optimise FlashCopy and other bitmap access With overprovisioning more than 10% Flash/SSD will be required as metadata is based on virtual space 25

26 Estimating FlashCopy Capacity requirements Easy Tier trace data can be used to estimate capacity requirements for FlashCopy to Thin Provisioned volumes This could be for Global Mirror usage or for Backup/Testing purposes Percentage of Extents Estimate will be conservative as it is based on large extent data not small extents /07/ :36 11/07/ :36 11/07/ :36 11/07/ :36 11/07/ :36 12/07/ :36 12/07/ :36 12/07/ :36 12/07/ :36 13/07/ :36 13/07/ :36 13/07/ :36 13/07/ :36 14/07/ :36 14/07/ :36 14/07/ :36 14/07/ :36 15/07/ :36 15/07/ :36 15/07/ :36 15/07/ :36 16/07/ :36 16/07/ :36 16/07/ :36 16/07/ :36 17/07/ :36 17/07/ :36 17/07/ :36 17/07/ :36 26 Percentage of Extents Written to in Interval Cumulative Percentage of Extents Written To Estimate for Global Mirror Journal Usage

27 KMIP support as Encryption Key Server Beginning with R8.1, the DS8880 will support either KMIP or IPP (but not both simultaneously) DS8880 will continue to support SKLM and ISKLM via IPP only (not KMIP) for now DS8880 first implementation of KMIP will be Safenet KeySecure Key Server Others key managers may be supported submit a RPQ if needed 27 Standardization makes it easier for servers to support the growing number of encryption clients by supporting KMIP.

28 Copy Services Manager (CSM) on the HMC 28 CSM follow on product based on TPC-R IBM Copy Services Manager is a storage replication product that provides a single place to manage all the replication across your IBM storage environment. Installed on HMC by code load (CDA) process CSM code level package will be installed (initial R8.1 release) DS8000 CSM Function Authorization Offering DS8000 Copy Services and Copy Services Manager (CSM on HMC) Full CSM functionality Enabled via DSFA key CSM enablement files are activated on the HMC(s) when key is applied Upgrade CSM on HMC CSM can be upgraded independently of DS8000 microcode from R8.1.1

29 Native LDAP Client on DS8000 Copy Services Manager now contains LDAP client CSM can run in DS8880 HMC starting with R8.1 No CSM license/enablement required on HMC if using just for LDAP support Can replace TPC as the LDAP provider CSM provides the same interface as TPC Same DS8000 LDAP steps except now CSM is the provider Resides on DS8000 HMC or wherever CSM is installed LDAP must be first configured in CSM Enable in both HMCs if dual HMCs installed in DS8880 GUI support for LDAP setup in the Administration panel 29

30 Create & Offload PE Package & Statesave Ability to trigger generation & offload of Statesaves, ODD dumps and PE Packages Performed via DS-CLI or ReSTful API Default is to offload the last available Can also list and select any available Automation opportunities with solutions such as GDPS GDPS HyperSwap occurs Issue commands to offload PE package and statesave Data for Analysis is available far sooner / Problem Resolved sooner / Swap Back sooner 30

31 Remote Event Notification via Syslog DS8000 provides an audit log for DS8000 configuration changes and other actions Today this is available via the internal audit log but not externalized and must be accessed via command to save off to a workstation Fear is that the internal audit log may be altered to hide unauthorized alteration or access This new capability will offer the option to log directly to an external Syslog server Up to 8 Syslog servers can be defined Events logged to external Syslog server are: User login/logout Changes to logical configuration made via DSCLI or web interface (DSGUI) Follows standard Syslog format 31

32 Media Error Recovery on PPRC secondary For environments with multiple site replication environments media errors or other data loss events can occur on any of the replicated copies. HyperSwap protects against events on the production copy but manual actions are currently needed if there is an event such as a RAID rebuild failure on other copies of data. When a media error occurs on the secondary the DS8000 will log the track range lost in the PPRC structures and suspend the pair. For Global Copy and Global Mirror auto unsuspend will add the track range to the OOS and the tracks will be recovered on resync. For Metro Mirror resynchronisation will add the track range to the OOS and the tracks will be recovered on resync. In the initial release only a subset of data loss events will be covered by this functionality. Only media error events will be covered (ESCs 4910 and 4920) Only up to 500,000 tracks will be able to be handled 32

33 Thank You for Attending! Please remember to complete your evaluation of this session in the SHARE mobile app. The New and Improved DS8880 Family 33

34 Visit the SHARE Booth (#303) Educate Network Influence Learn more about hot topics from peers in the Tech Talk Corner Take part in the Hack-a-Thon with & Engage with fellow attendees Connect with the znextgen community Join the #SHAREatl social media conversation Discover ways to get involved with SHARE Meet SHARE Volunteers 34