Nordic Large Systems Update, 2015 GDPS Update Soren Understrup, IBM DK

Transcription

1 Nordic Large Systems Update, 2015 GDPS Update Soren Understrup, IBM DK Large Systems Update 2015 Agenda GDPS 3.12 was GA on March 31, 2015 Covered in this session New product: GDPS/Multi-Target Metro Mirror GDPS/: z/os Proxy feature GDPS Virtual Appliance (GA on April 30, 2015) Other enhancements in GDPS 3.12 Bits & bobs & hints & tips 2 Large Systems Update 2015

2 What is GDPS? Global Continuous Availability & Disaster Recovery Offering for IBM z Systems over 17 years and still going strong Manage & Automate Central Point of Control z Systems and Distributed Servers xdr for z/vm and on z Systems Replication Infrastructure Real-time Monitoring and Alert Management Automated Recovery HyperSwap for Continuous Availability Planned & Unplanned Outages Configuration Infrastructure Mgt Single site, 2-site, 3-site, 4-site Automated Provisioning z Systems CBU / OOCoD Automation z/os xdr A C DCM B D GDPS/ HM GDPS/ GDPS/XRC GDPS/GM GDPS/MTMM GDPS/MzGM GDPS/MGM GDPS/A-A GDPS Appliance Solutions Replication HyperSwap Manager (Metro Mirror) XRC (z/os Global Mirror) Global Mirror Multi-target Metro Mirrror Metro z Global Mirror 3-site and 4-site Metro Global Mirror 3-site and 4-site Active-Active (Metro Mirror) System Automation for z/os NetView for z/os SA Multi-Platform SA Application Manager Multi-site Workload Lifeline Disk & Tape Metro Mirror z/os Global Mirror Global Mirror DS8000/TS7700 Software IBM InfoSphere Data Replication (IIDR) for DB2 IIDR for IMS IIDR for VSAM 3 Technology First GDPS installation 1998, now 800+ in 46 countries 3 Large Systems Update /2015 GDPS/Multi-Target Metro Mirror aka GDPS/MTMM Large Systems Update 2015

3 MultiTarget Metro Mirror (MTMM) New disk location and replication leg terminology Data is transferred to both targets in parallel Pairs operate independent of each other Pairs may be established, suspended or removed separately A replication problem on one leg does not impact the other leg HyperSwap is possible on either leg RL2 H1 RL1 H2 RL3 (MTIR) H3 Internal IR Pairs Automatically created Converted into active pairs when needed Track the data difference between the remote volumes Provides all the benefits of synchronous mirroring plus has the additional protection of a second synchronous leg 5 Large Systems Update 2015 GDPS support DS8870 Multi-Target Mirror architecture (aka MT-) New MT- architecture on DS8870 Supporting multiple sync and/or async targets from the same primary device A number of topologies supported by MT- Two synchronous Metro Mirror One synchronous Metro Mirror and one asynchronous Global Mirror Two asynchronous Multi-target solutions with Metro Global Mirror or Metro z Global Mirror Initial GDPS delivery focused on the two synchronous Metro Mirror solution (Multi-Target Metro Mirror or MTMM) New GDPS product: GDPS/MTMM 6 Large Systems Update 2015

4 H1 failure Unplanned swap to H2 Failure at H1 HyperSwap to H2 Failover H2H1 Move I/O to H2 H1 H3 Resume H2H3 with Incremental Resync (IR) Failover H3H1 Failback H2H3 Mirroring is quickly resumed H2 When H1 recovered Failback H2H1 Each replication leg is tracked and managed independently 7 Large Systems Update 2015 Planned swap back to H1 HyperSwap to H1 Failover H1H2 Move I/O to H1 Resume H1H2 and H1H3 pairs H1 H3 Failover H3H2 Failback H1H2 Failback H1H3 H2 Maintaining two secondary targets (two legs) from a single primary device 8 Large Systems Update 2015

5 IBM Systems GDPS/MTMM sample configuration PTS/CTS BTS K1 P1 CF1 CF2 P2 K2 site-1 PRI Primary ALT site-2 local K1 CDS1 CDS2 spare RL1 H1 RL2 (MTIR) RL3 H3 CDS1 CDS2 spare local K2 2 sets of non-ed CDSs in each of the disk locations CDS1 spare H2 CDS2 spare 2 server sites (Site1 & Site2) 3 disk locations H1&H2 assumed to be in Site1, H3 in Site2 H2 could be a bunker site 9 Large Systems Update IBM Corporation GDPS/MTMM provides. Ability to enable HyperSwap on either or both of the legs Planned HyperSwap targets the leg selected PRIMARYFAILURE policy specified at leg level Policy to specify preferred swap leg for unplanned HyperSwap Unplanned HyperSwap will occur on preferred leg if possible, else, other leg attempted For failures GDPS freezes impacted leg only, other leg unaffected FAILURE policy specified at leg level New policy options STOPLAST and CONDLAST introduced to set the policy to STOP or COND if leg to be frozen is the only remaining viable leg GDPS/MTMM is inherited from GDPS/ but is a new product Designed primarily for full time, full 2 leg configuration operations Single leg configuration supported to faciliatate initial upgrade/migration from GDPS/ Majority of system, sysplex and HW management functions inherited from GDPS/ xdr for z/vm is supported with some initial restrictions Many functions in GDPS/ not implemented yet e.g. TS7700, DCM, Foreign New CDS topology introduced to support 3 storage locations 10 Large Systems Update 2015

6 GDPS/MTMM prerequisites and restrictions All systems in the sysplex must be running GDPS/MTMM 3.12 No coexistence between GDPS/MTMM and GDPS/ z/os requires support APARs and a parameter change in DEVSUPxx member to enable MT support Supported releases of NetView and System Automation for z/os z/vm 5.4, 6.2 or SPE and SA MP SPE required for xdr support DS8870 (at ucode level 7.4 or higher) on ALL disk subsystems in GDPS config Symmetric MTMM configuration every primary must have 2 secondaries Each leg must be HyperSwap-ready (all paths Freeze=Y, 1-1 LSS mapping) No support for GDPS/MGM or GDPS/MzGM IR configurations Cascading sync/async relationships off of H1/H2/H3 disks not supported GDPS/MzGM non-ir is tolerated Note: There is no toleration for Multi-target relationships in either GDPS/ or GDPS/HM 11 Large Systems Update 2015 GDPS/ capabilities currently not supported in GDPS/MTMM Heat Map Transfer Query Services I/O Timing (IOTiming) triggers for HyperSwap are ignored Non-HyperSwap ready configuration (Freeze=N paths, 1-to-many/many-to-1 LSS mapping) Fixed Block devices (FB or Open LUNs) Managing on behalf of foreign systems (either with or without the z/os Proxy) TS7700 management Distributed Cluster Management (DCM) VCS, AppMan & zbx xdr for Native on z Systems xdr VM SSI, VM disks using alternate subchannel sets IMS/XRF interface for GDPS GDPS Tools available with GDPS/ z9 systems - CBU/OOCoD script statements (replaced by CAPACITY statement) A number of GEOPLEX OPTIONS Planned HyperSwap with Terminate and Resync options Facilities for managing single OSConfig (DASDVARY and automatic reply to dup volser) DS8K MTMM restriction: RPFC only supported on one of the two replication legs If any of these is essential to client, send mail to gdps@us.ibm.com 12 Large Systems Update 2015

7 GDPS/MTMM Benefits GDPS/MTMM manages the Multi-Target Metro Mirror topology Two independent CA/DR relations so that a failure of one of the copies does not affect the CA/DR capability of the other site Provides, via policy, the ability to set the preferred swap leg for HyperSwap Inherits the following GDPS/ capabilities: End to end continuous availability of data and DR for z/vm and on IBM z Systems Simplification of systems management actions such as Stopping and IPLing systems Temporary capacity management Sysplex resource management CDS management extended to support 3 storage locations Powerful workflow automation Simple scripting to address planned and unplanned situations Monitoring and alerting for the replication, system and sysplex environment for any issues GDPS Health Checks provided Builds on 17 years of proven, industry leading, capabilities 13 Large Systems Update 2015 GDPS/ z/os Proxy support Large Systems Update 2015

8 Typical GDPS/ client landscape. Foreign Sysplex GDPS/ Sysplex B A1 A2 K1 P1 P2 P3 K2 C D CA: Continuous Availability DR: Disaster Recovery One or more GDPS/ sysplexes Each with own Ksystems All systems in the GDPS sysplex running SA/NV A number of other stand-alone systems or small sysplexes aka foreign systems/sysplexes How to provide CA/DR capabilities to these foreign systems/sysplexes???? Some GDPS-managed DR capability exists No CA capability (no HyperSwap) 15 Large Systems Update 2015 Providing DR to foreign systems (before z/os Proxy) B A1 A2 16 Large Systems Update 2015 C Some GDPS management previously available for foreign systems: management Hardware management Load, reset, act/deact LPAR No system status tracking Coordinated freeze for secondary data consistency and DR capability HyperSwap available for GDPS sysplex systems, not transparent to foreign systems D Foreign systems need to be stopped prior to planned swap Foreign systems will hang during unplanned swap and must be reset and reipled after the swap K1 GDPS/ Sysplex P1 P2 P3 K2

9 New!!! z/os Proxy: Providing CA to foreign systems z/os Proxy CTC Foreign System CTC K1 P1 P2 P3 K2 D Backup LPAR D HyperSwap P S Run z/os Proxy on each z/os Proxy-managed foreign system Each foreign system to be managed attaches via FICON CTC to each GDPS K-system z/os Proxy communicates with and coordinates with GDPS K-systems GDPS manages entire configuration as a single configuration 17 Large Systems Update 2015 The final picture GDPS/ Sysplex B A1 A2 C D K1 P1 P2 P3 K2 P1, P2, P3 are systems in the GDPS sysplex They enjoy full benefit of GDPS/ A1, A2, B, C, D are all z/os Proxy managed systems They enjoy most of the benefits of GDPS/ Most importantly CA with Planned/Unplanned HyperSwap Note: Data of GDPS sysplex systems and z/os Proxy-managed systems are all frozen/swapped together 18 Large Systems Update 2015

10 z/os Proxy pre-requisites and support info z/os Proxy is a separately priced feature of GDPS/ Priced on a per z/os Proxy-managed z/os system basis Maximum 16 z/os Proxy-managed system per GDPS/ instance Licence enablement via IFAPRDxx Prerequisites z/os Proxy-managed systems require: Any generally supported release of z/os on managed systems z/os BCPii must be implemented REXX runtime library (Alternate REXX library available with z/os at no-charge) GDPS/ Controlling systems require: Full function GDPS/ 3.12 GDPS/MGM & GDPS/MzGM 3-site & 4-site configurations will be supported post-ga GDPS/MTMM not supported 2 K-sys strongly recommended 2 FICON CTC from each z/os Proxy-managed system to each Ksys 19 Large Systems Update 2015 z/os Proxy benefits z/os Proxy-managed foreign systems Single point of control for systems in the GDPS systems and foreign systems Continuous Availability with Planned & Unplanned HyperSwap Co-ordinated D/R Faster implementation timescales to provide CA Many of the GDPS capabilities/benefits extended to foreign systems Same general GDPS management principles and processes for all z/os systems No new skills required to adopt a different product/solutoin No need to reinvent the wheel with RYO automation to manage foreign systems D/R Alternatives need to be evaluated carefully for each client situation Although simpler to implement, z/os Proxy not always the best nor the lowest cost solution z/os Proxy is a separately priced feature of GDPS/ Priced on a per z/os Proxy-managed z/os system basis Maximum 16 z/os Proxy-managed system per GDPS/ instance Licence enablement via IFAPRDxx 20 Large Systems Update 2015

11 IBM Global Technology Services Background and Architecture GDPS Virtual Appliance Overview Large Systems Update IBM Corporation GDPS Virtual Appliance extends GDPS capabilities into z/vm and on System z environments that do not have z/os. IBM GDPS Virtual Appliance is designed to facilitate near-continuous availability and disaster-recovery by extending GDPS capabilities for on System z and z/vm environments. GDPS Virtual Appliance features: Single point of control and automation reduces the need for highly specialized skills to handle recovery and planned site switches Manages remote copy environment and keeps data available and consistent for operating systems and applications. HyperSwap function protects against failures to disk subsystems. Monitoring and automation to ensure reliable and rapid recovery via automated processes Virtual Appliance requires: General purpose engine z/vm and on System z ECKD Disk z/vm LPAR xdr Proxy x2 System z z/vm + disks (primary) Takeover GDPS Appliance LPAR System z Site 1 Site 2 z/vm LPAR xdr Proxy x2 z/vm + disks (secondary) 22 Large Systems Update 2015

12 z/vm Managed Systems z/vm LPAR xdr Proxy x2 System z z/vm + disks (primary) GDPS Appliance LPAR System z Site 1 Site 2 z/vm LPAR xdr Proxy x2 z/vm + disks (secondary) Multiple z/vm systems supported Each z/vm system must contain at least two guests running SA MP. This is the GDPS proxy cluster Each z/vm may also contain: One or more additional guests running SA MP and some application workload. One or more additional guests without SA MP and some application workload. One or more non- guests (CMS, etc.) TCP/IP Connections from GDPS Virtual Appliance to: Proxy guests (required) Other guests with SA MP (optional) SA MP Clusters: Proxy guests must be separate cluster Group other nodes into clusters, as appropriate for efficient SA MP design. 23 Large Systems Update 2015 xdr Guest SA MP Clusters Required TCP/IP Connection(s) 24 NetView E/AS NetView z/os SA MP Master Node Proxy Master z/vm TCP/IP Optional TCP/IP Connections SA MP Node Proxy Backup SAP SA MP Master Node SA MP Clusters GDPS SA zos SAP SA MP Node SAP SA MP Node 24 Large Systems Update 2015 Multiple z/vm systems supported z/vm guests running and SA MP Proxy Guest used by GDPS to communicate commands to z/vm and to monitor for disk errors Is a cluster of just one node One or more application clusters made up of one or more nodes One node will be the master All guests run an application workload, e.g., SAP TCP/IP connections between the guests and NetView Event/Automation Service Address Space (E/AS) are used to inform GDPS of Their existence Their ongoing presence, and Any change in their status

13 xdr for on z/vm Software Requirements Supported Distributions Supported Distributions SUSE SLES 11 Red Hat 6 Version of System Automation SA MP (plus APAR) or higher SA MP (plus APAR) or higher Separately priced SA MP feature xdr for is required Latest fixpacks for and SA MP Required VM Version V5.4, or V6.2 or higher Check GDPS PSP bucklets for recommended maintenance Supported Disk Types DASD ECKD 25 Large Systems Update 2015 Other GDPS 3.12 Items & News Large Systems Update 2015

14 GDPS Heat Map Transfer GDPS/XRC Similar set up to the GDPS/ support Supported for HMT from XRC primary to XRC secondary or XRC tertiary disk HMTU Daemon(s) run on Kx only One daemon for all XRC sessions GDPS config process builds the initial input configuration files for the HMTU New GEOXPARM statement at the session or Master session level to indicate GDPS should manage HMT and the which disk (secondary or tertiary) HMT capable disk subsystem pairs and device pairs included in the HMT configuration Kx initiates transfer every 12 hours (so long as there are non-suspended volumes in session) HMTU daemons connect to the HMCs of the disk subsystems in the HMT configuration 27 Large Systems Update 2015 GDPS Heat Map Transfer GDPS/XRC GDPS dynamically updates the configuration for HMT based on volume/session status For example, when a session is suspended, the volumes are removed from the HMT config and any future Easy Tier learning will not be transferred until the volumes are actively mirroring again HMT panels to start/stop process, view status (e.g. last transfer time, duration), initiate a transfer Monitor3 extensions to monitor DS8K HMC connectivity and transfer state GDPS HMT for XRC is supported for the XRC leg in MzGM environments, but the transfer will always be from the Site1 disk from a perspective. In the event of a HyperSwap to Site2, in an IR configuration, when XRC resumes, HMT will continue to copy the learning information from the Site1 disk 28 Large Systems Update 2015

15 GDPS Health Checks Several health checks updated with new capabilities Check_LOGR extended to check DFHULOG logstreams and optionally System Automation for z/os logstreams Check_CONFIG has new override capabilities Check_DASDMIH has a new method for defining the best practice value for ranges of devices to comapare against Check_CONSOLE is updated to check for additional messages in the z/os Auto Reply policy Check_CONSOLE has been added to XRC and GM environments Check_SPOF has been added to the GM environment for connectivity between the Kg and primary disk GEOHCP00 now support use of a GEOHCPxx member PARM_SUFFIX=xx in GEOHCP00 points to this new member All other statements in GEOHCP00 would be ignored when a valid suffix is defined GDPS health checks now dynamically installed rather than via SETPROG EXIT commands 29 Large Systems Update 2015 GDPS 3.12 small items + hints and tips GDPS/ support for zbx has a new reactivate option for blades and virtual servers Essentially a deactivate followed by an activate of the targeted resource CANZLOG NetView V6.1 introduced the consolidated Netlog/Syslog and this has implications on your memory requirements due a 500MB to 2GB dataspace allocated at IPL time xdr Users The required minimum memory for the proxy machines has been increased to 512MB GDPS has been tested in a 2-site GDPS/ configuration with zhyperwrite and no issues have been discovered. When using dynamic SDF panels in System Automation for z/os you are recommended to use a 3270 emulator session with at least 32 (preferably more) lines. 30 Large Systems Update 2015

16 GDPS Support items GDPS/ and GDPS/XRC support for IBM Peer-to-Peer VTS has been removed Support or disk subsystems that do not support failover and failback functions has been removed The GDPS/MGM Incremental Resync tool has been removed, it is replaced by the supplied GDPS/MGM procedures GDPS 3.12 is the last release to support the OVERRIDE option in GEOPLEX OPTIONS. Existing defaults will continue to be used. NetView for OS/ will go end of support on 30 June 2015 NetView for z/os 5.3 will go end of support on 30 September 2015 System Automation for z/os V3.3 goes end of support 30 April 2015 System Automation for Multi-Platforms V3.1 and System Automation Application Manager V3.1 go end of support 30 April 2015 The Sysplex Timer (9037) is out of support 31 Large Systems Update 2015 Questions? 32 Large Systems Update 2015