IBM iha/dr and PowerHA Strategy

Transcription

1 IBM iha/dr and PowerHA Strategy Created Steven Finnes Presented by Mervyn Venter

2 Session objectives Understand the concept of shared storage clustering Typical Storage Based HA/DR PowerHA configurations Flashcopy New PowerHA HyperSwap clustering PowerHA with geomirroring and internal disk PowerHA geomirror price example (amazingly low cost solution) A quick profile of the PowerHA customers around the world PowerHA and CBU for i example PowerHA and Enterprise Pools CBU for PowerHA for the E880 for huge savings and fast failover Lab services PowerHA FSR New Advanced Copy Services New multi-target PowerHA with DS8K

3 PowerHA shared storage clustering solutions High Availability (HA) Management data center Standard Edition Clustering for mission critical application availability Planned and unplanned outage management Shared storage resiliency Disaster Recovery (DR) Management multi-site Enterprise Edition Multi-Site clustering (covers both HA and DR) Integrated storage based replication Simplified compliance testing Data Center Clustering Multi-Site Clustering

4 PowerHA SystemMirror Shared Storage Cluster Benefits: Automated Fallover Redundant LAN Non disruptive upgrades PTFs Application Monitoring Implemented in SLIC Server A Cluster Configuration Server B Event / ERROR Notification GUI, CL mgmt Different Failure Types: IP Loss Detection Redundant SAN Loss of Storage Application Interruption Server Crash Loss of Power Configuration Options Storage Enclosure Active / Passive

5 PowerHA basic concepts Admin domain Application data (IASP) aka (volume group) PowerHA SystemMirror creates and manages a shared storage cluster topology IASP volume group hosts the DB, IFS data Admin Domain manages the sysbas data Note that the foundational topology does not involve replication

6 IBM storage based high availability configurations Application Application Example: high availability configuration, PowerHA Standard Edition cluster Metro Mirror Example: high availability configuration PowerHA Enterprise Edition Cluster

7 PowerHA Storage based disaster recovery configuration Application Global Mirror PowerHA Enterprise Edition with Global Mirror replication Unlimited distance Typically used for disaster recovery

8 unified two-site HA/DR solution Requirements Multi-site configurations Data center/campus component for HA Second site for DR Solution Strategy: Unified clustering solution for data center & multi-site resiliency PowerHA SystemMirror Enterprise Edition Application Metro Mirror or Global Mirror

9 + flash copy to minimize backup window IASP Prod LPAR FlashCopy IASP FlashCopy LPAR FlashCopy is an integral part of a PowerHA on IBM i cluster It effectively eliminates your backup window Full system flash copy is also an option though not as seamless as with IASPs

10 IBM PowerHA SystemMirror on i data resiliency options Supported Solutions Geographic Mirroring IBM i host-based mirroring between data in IASPs LUN-level switch DS8000, SVC, or Storwize hosted IASP LUNs switchable between IBM i partitions Metro Mirror Synchronous DS8000, SVC or Storwize storage-based mirroring Global Mirror Asynchronous DS8000, SVC or Storwize storage-based mirroring Flash Copy DS8000, SVC or Storwize point-in-time copy

11 two site traditional cluster with Metro Mirror Application Metro Mirror Traditional two-site Metro Mirror cluster configuration Synchronous replication limits effective distance due to lag IASP replication synchronous to application state (real-time identical copies) Server outage management via a PowerHA cluster operation Storage outage management via a PowerHA cluster operation

12 enterprise edition HyperSwap solution for high availabilit Application Site one Metro Mirror HyperSwap Site two Two-site DS8K HyperSwap PowerHA Enterprise Edition cluster configuration Server outage management via a PowerHA cluster operation Storage outage management via a HyperSwap switch

13 Enterprise edition HyperSwap cluster under the hood *SYSBAS Metro Mirror *SYSBAS IASP MetroMirror Virtual IASP IASP *SYSBAS DS MetroMirror HyperSwap *SYSBAS DS8000 HyperSwap has the effect of making the replicated pair of IASPs appear as a single virtual IASP HyperSwap switches the source and target IASP and SYSBAS in the event of a storage outage The source IASP is mirrored to the target IASP via Metro Mirror The source and target SYSBAS data are mirrored via Metro Mirror In the event a storage outage event, the source system switches to the mirrored IASP and the mirrored SYSBAS In the event of a production server outage, PowerHA conducts a failover to the target production server, (the virtual IASP is switched to target) Metro Mirror will reverse direction of replication and production resumes on the secondary power server If VIOS is deployed, LPM can be used for firmware updates, load balancing etc DS8800 and above (TPC-R not utilized)

14 Three site MGM cluster with HyperSwap Welcome to the Waitless World Application Metro Mirror HyperSwap Global Mirror Site one Site two Site three Metro Global Mirror (MGM) cluster with Hyper Swap IBM PowerHA System Mirror for i Planning Insights: IBM plans to introduce the capability to add a third system connected to the PowerHA for i HyperSwap pair via either a Metro Mirror or Global Mirror link. 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 remains at our sole discretion.

15 Three site MGM cluster with HyperSwap Application Metro Mirror HyperSwap Global Mirror Site one Site two Site three IBM PowerHA System Mirror for i Planning Insights: IBM plans to introduce the capability to add a third system connected to the PowerHA for i HyperSwap pair via either a Metro Mirror or Global Mirror link. Metro Global Mirror (MGM) cluster with Hyper Swap 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 remains at our sole discretion.

16 PowerHA geomirroring HA/DR clustering Welcome to the Waitless World Sysbas Admin Domain Sysbas production partition IASP target partition IASP geomirror DB2, IFS DB2, IFS PowerHA geomirror cluster (typically with internal disk and < 4 Tbytes ) Complete HA/DR coverage for all outage types (hardware, middleware, operator error) Off line back-up followed by source side /target side tracking change resynchronization Both bandwidth and network quality are important. Synchronous mode up to 40 KM, production and target always identical Asynchronous mode unlimited distance, production and target ordered and consistent

17 Geomirroring ihosting iremote VM restart for DR Applications i host partition IASP Admin domain* i host partition IASP client partition NWSSTG IBM i hosted partition geomirror NWSSTG IBM i hosted partition client partition * Admin Domain on host is optional Non-cluster PowerHA configuration, full system replication, this is disaster recovery setup, this is not a HA solution IBM client placed into a network storage space which is placed into an IASP Guest and host partition must be shut down before remote host and client can be restarted Limitation: no heart beating, can t do concurrent OS upgrades, is more resource intensive than a PowerHA cluster Note that everything is being replicated so network bandwidth and quality is critical Any roll over or failover requires an abnormal IPL of target

18 Small client price example with PowerHA and geomirror $ 6500 for a complete HA/DR solution Production server S814 has one core,cbu server, S814 has one core. Since geomirror consumes only a fraction of the CPW you only need one core on the CBU Production site and DR site are 400 miles apart therefore we will need geomirror async mode. Geomirroing async mode costs $3400 per core. Since customers in this environment typically use internal disk and therefore can not do switchable luns, we put geomirroring sync mode into the standard edition. In all other cases, storage replication requires the Enterprise Edition. In this case the customer needed 100Mbits of bandwidth (lab services will do the sizing for bandwidth) So let s do the math to see what this HA solution cost us. Do we need a calculator? $3250x2 = $6800 $6500 for an HA/DR solution that requires very little care and feeding.

19 PowerHA with geomirroring PowerHA with geographic mirroring is popular with our smaller IT shops Very inexpensive compared to logical replication solutions, its easy to use and requires little day to day monitoring and maintenance. Typically used by shops with under 2 Tbytes and on internal disk After an unplanned outage the target data is replicated back to the source therefore the larger the IASP the longer the resync time Doing a tape backup off of the target works great, Quiesce the IASP on the current production copy system (see speaker notes) if you want to get a clean transaction boundary. If you choose to do the quiesce (recommended), do it during a quite time. Geomirroring is IBM i mirroring of the data writes to the IASP source and target over IP Referred to as host based replication (as opposed to storage based replication) IBM i storage management sends the memory pages to both the remote and local server either synchronously or asynchronously Synchronous distance is typically under 30 or 40 KM but distance is driven by application response time requirements Bandwidth and quality of service are both important. When we ve seen issues they usually come down to network quality.

20 Who are our PowerHA for IBM icustomers? PowerHA for IBM I is installed in accounts ranging from small to very large enterprises. Virtually all of them (over 95% ) moved off of logical replication solutions. Over 1000 are clients with fewer than four processor cores. These customers typically are using PowerHA with geomirroring and internal disk About 20% of these are using ihosting i with geomirroring for a full system replication solution. Although the ihosting I with geomirring is classified as a disaster recovery solution, some clients prefer it because its relatively easy to set up and doesn t require a cluster configuration where the database is separated out into an IASP. The customers using PowerHA with geomirroring are represented in every industry; municipalities, retail, distribution, banking, manufacturing The other half of the PowerHA on IBM i customers are using IBM storage servers. The DS8K implementations are LUG class customers who nearly always have at least two sites involved in the cluster and increasingly, three sites. The rest of the customers are using Storwize servers ranging from the V3700 on up to the SVC or the V9000. The V7000 has been the most popular in recent years. The motivation behind storage servers ranges from scalability, robustness, flash copy and the capability to support various combinations for HA and DR in a PowerHA cluster.

21 PowerHA Price Example Economic Value - TCA PowerHA is priced per processor core used in the HA/DR cluster Taking advantage of the CBU topology in the example topology: Assume 880 cluster, 7 ios and 7 PowerHA PowerHA price: 5,250/core = $36,750..savings: $42,000 IBM i price: 59,000/core = $413,000..savings: $826,000 Total savings.$868,000

22 PowerHA V7 with Enterprise Pools example PowerHA Processor, Memory, Software # nodes # s proc # m processors price s memory m memory t memory m price s price total memory Total Power E870 Production $0 desired ,280 IBM i 8 56 $3,776,000 actual 320 1,000 1,320 $0 $0 $0 PowerHA Ent Ed 8 56 $336, total $4,112, production $4,112,000 Power E870 Backup $ $0 $0 IBM i 1 0 $59,000 PowerHA 1 0 $5, total $64,250 backup $64,250 total processor $4,176,250 total mem $0 $4,176,250 proc savings $4,047, mem saving $0 total savings $4,047, Animated chart

23 Two node PowerHA cluster with Enterprise Pools # nodes # s proc # m processors price s memory m memory t memory m price s price total memory Total Power E870 Production $0 desired ,280 IBM i 8 56 $3,776,000 actual 320 1,000 1,320 $0 $0 $0 PowerHA Ent Ed 8 56 $336, total $4,112, production $4,112,000 Power E870 Backup $ $0 $0 IBM i 1 0 $59,000 PowerHA 1 0 $5, total $64,250 backup $64,250 total processor $4,176,250 total mem $0 $4,176,250 proc savings $4,047, mem saving $0 total savings $4,047, This represents the net savings assuming that the frames, cables, processor nodes etc are the same between the two systems Production server is a 64 core 870 with 1.32TB of memory (initially they wanted1.28tb however mobile comes in units of 100GB) 75% of memory or 1000 GB is the max allowed mobile, the remaining 320 is static for a total of 1.32TB 56 of the production processor activation are mobile 8 are static, 64 PowerHA and IBM i entitlements Secondary server is a 64 core 870 with 8 active cores and 1.32T 50% installed memory must be active therefore 660GB is mobile, one PowerHA and one IBM i entitlement Total savings for IBM i, PowerHA EE, processor activations and memory = $ 4,047,750.00

24 Power Systems CBU for Welcome to the Waitless World entitlement transfer All transferable entitlements must originate on the primary system and may not run concurrently on the primary system and the CBU system Subsequent to the initial workload deployment, production partitions may be moved to the CBU system for workload balancing etc The total number of processor entitlements running production across both servers can not exceed the original total licensed entitlements. Primary CBU Offering for AIX and IBM i Power E880 customers HA/DR deployments requiring fast failover via active standby memory and processors Offering Entitlements One or two no charge processor nodes depending on the primary server configuration No charge active standby memory and processor cores via Elastic Capacity on Demand (ECOD) = PowerHA licensed cores on the primary system (minus 8 for required the activations on the CBU) Offering requirements overview Primary and CBU must be same GHz of Power E880 Primary can be new or installed box, CBU must be a new box Primary system must have a minimum of 75% of the processors activated and 50% of installed DIMM memory active One entitlement of AIX or IBM i & PowerHA non transferable Maximum of 8 processor activations on the CBU and minimum of 25% of DIMM memory active Minimum of 8 PowerHA entitlements on the primary system No charge ECOD days must be activated upon install of CBU system and remain active for 365 days The ECOD processor days can only be used on the Power E880 CBU system and must be renewed annually and customer is required to maintain minimum requirements Registration of primary system and CBU prior to CBU order fulfillment (registration validates minimum requirements) Primary and CBU must be within the same enterprise

25 Power E880 Servers in a CBU for PowerHA configuration PowerHA cluster CBU system specify feature code: EB3J Power E880 Primay System: 4.35 GHz or 4.0 GHz system 1 to 4 nodes per system Node feature codes: EPBB, EPBD N cores of PowerHA entitlements 75% of installed processors must be active and licensed with AIX and/or IBM i (Standard or Enterprise for either AIX or i) A minimum of 8 cores must be licensed with PowerHA (Standard or Enterprise) 50% DIMM memory active Power E880 CBU System: 4.35 Ghz or 4.0 Ghz system (must match primary) 1 to 4 nodes per CBU system* Node feature codes:epbg,epbh,epbb,epbd Maximum of 8 active cores 365 x N-8 = # of no charge ECOD processor days 365 x N-8 x 32 GB no charge ECOD memory days 25% of DIMM memory active *Select processor nodes from: No charge processor nodes: EPBG, EPBH One or two nodes on the primary = 1 no-charge node on the CBU Three or four nodes on the primary = 2 no-charge nodes on the CBU For charge processor nodes: EPBB, EPBD

26 Order Process/Registration Prior to ordering the CBU with PowerHA fill in the worksheet posted on the CBU registration website to determine minimum configuration requirements and no charge processor node and ECOD activations Submit CBU entitlement worksheet IBM verifies client configuration entitlements (no charge processor nodes and ECOD days) Customer agrees to CBU terms and conditions via registration website Send configuration files to After project office approval, order the approved CBU configuration Specify the # of no charge processor nodes (EPBG or EPBH) Econfig will automatically add the CBU system feature code: EB3J After CBU system is installed, configuration of Primary and CBU system is sent to PowerHACBU@us.ibm.com CBU project office will apply the appropriate number of ECOD days to Power E880 CBU system Implement TCOD (temporary COD) via standard process TCOD contract signed by client ECOD enablement codes ordered via MES Registration website:

27 PowerHA FSR (Full System Replication) FSR automates full system replication It s relatively simple to migrate to from internal disk and logical replication Functionality PowerHA FSR Integrated automation/management from IBM i * IBM i based recovery for Data/Commitment control etc FlashCopy saves for scheduled outage reduction (full system flash requires an IPL to save the data to tape) * RTO minutes hour Minimize bandwidth requirements Minimize performance overhead of sync replication ( not replicating temporary I/O, savf s etc ) Provide capability to do PTF, operating system, and software packages concurrent to production Active host at HA/DR ( hardware error reporting ) Outage management requires IPL processing No IASP migration required Ensure that the solution meets the SLA of the customer Due the proper sizing's for performance and bandwidth Use as a first step in the transition to clustering * Via Lab Services tools IPL

28 Advanced Copy Services (ACS) 4.1 Major release boundary for existing ACS customers - upgrade path from ACS 3.1 ACS 4.0 was only for FSR with V7K customer Support for FSR with DS8K Revised Global Mirror support for IASP Withdrawn DS8K MGM support ACS 3.1 will be the last release to support old style MGM Support for Multi Target Metro/Metro Mirror with CSM Support for Multi Target Metro/Global Mirror with CSM Improved SVC/V7K for IASP Detach capability for DS8K with IASP s when used with CSM

29 Multi Target PPRC Support Multi Target PPRC support on with icsm(acs) allows 2 configuration. Metro/Global Mirror 1 synchronous set of pairs providing an RPO of zero data loss 1 asynchronous set of pairs providing an undetermined RPO based on bandwidth and writes Requires 3 DS8870 s with 7.4 or higher Requires CSM or complete TPC(spectrum control) solution Requires IBM i 7.1 or higher. This requirement is due to Java requirements for the CSM client CSM can be loaded on any IBM platform including PPC linux, AIX, windows or zos ( soon IBM i?)

30 Multi Target PPRC Support Multi Target PPRC provides a large functional uplift over the older MGM cascaded support. The main highlights are No restrictions on using incremental FlashCopy in the environment. MGM did not allow any FlashCopies to be incremental without causing full resync s on switchover No requirement for all environments to use the same LSS s ( previous toolkit restriction ) No full resync s when switching to DR. MGM required a full resync for any switch to D/R No action required in a multi target environment when H2 fails MGM required customer to take manual action to remove H2 and start H1->H3 to maintain replication to the third site Any node can be detached for D/R testing ( provided it is currently running ) No detach capability at all A switch from H1 -> H2 can be performed when H1 -> H3 is suspended/failed This would cause a full resync with MGM A switch over from H1 -> H3 is possible if H1 -> H2 is suspended/failed Not possible with MGM For MM/GM, a cascaded environment back to H1 then to H2 will be setup by CSM, then a Global Mirror from H3 -> H1 will be started by icsm(acs) Not possible with MGM everything is a full resync ( an multiple of those ) New GUI with CSM MM/GM after a switch to H3 it does not know that we have started Global Mirror over the top of H3->H1

31 Additional resources for PowerHA IBM i PowerHA Wiki Lab Services PowerCare Redbooks at NEW REDBOOKs Draft Version Available in Jan 2016! We re cleaning house and bringing out a new series

32 PowerHATools for IBM i Complement and extend PowerHA and IBM Storage capabilities for HA/DR Helps reduce business risk and improve resiliency for critical applications Simplifies set up and automation of HA/DR and backup solutions Reduces cost of maintaining and regular testing of an HA/DR environment Facilitates flexible deployment options for single or multi-site protection Assures consistent deployment using best practices and experienced consultants PowerHA Tools for IBM i is a service offering from IBM Systems Lab Services 31

33 PowerHA Tools for IBM i Welcome to the Waitless World PowerHA Tools for IBM i Capability Benefit DS8000 Storwize Internal Smart Assist for PowerHA on IBM i Provides operator commands and scripts to supplement PowerHA installation and ongoing operations for IASP enabled applications. IASP Copy Services Manager (Automated recovery with faster IASP-level vary on, no system IPL) Flashcopy Automates Flashcopy of IASP for daily off-line backup with seamless BRMS integration. Simplifies deployment and ongoing management of high availability for critical IBM i applications. Increases application availability by reducing or eliminating backup window for routine daily backups. Yes Yes Yes Yes Yes LUN-level Switching Simplifies deployment and automates switching of an IASP between IBM i cluster nodes in one data center. Enables a business continuity manager to provide a simple, single site HA solution. Yes* Metro Mirror or Global Mirror Simplifies initial deployment and automates ongoing server and storage management of two-site Metro Mirror or Global Mirror HA or DR solutions. Requires IASP enabled applications.. Enables a business continuity manager to provide seamless operation of integrated server and storage operations for two-site high availability or disaster recovery. Yes Metro Global Mirror (MGM) Extends PowerHA functionality to provide three-site server/storage replication solution combining Metro Mirror for HA with Global Mirror for DR. Requires IASP enabled applications and IBM Tivoli Productivity Center Replication (TPC-R). Full System Copy Services Manager (Automated recovery, requires full system IPL on target LPAR) Flashcopy Metro Mirror or Global Mirror Automates full system Flashcopy for daily off-line backup with integrated support for BRMS without IASPenabled applications. Simplifies initial deployment and automates ongoing server and storage management of two-site Metro Mirror or Global Mirror HA or DR solutions. without IASPenabled applications. Enables a business continuity manager to further lower business risk and maximize business resilience for highly critical business applications that require threesite HA/DR protection. Increases application availability by reducing or eliminating backup window for routine daily backups. Enables an entry solution while planning IASP enablement. Enables a business continuity manager to provide seamless operation of integrated server and storage operations for HA or DR. Enables an entry solution while planning IASP enablement. Yes XIV Yes Yes Yes Yes Yes 32

34

35 SmartAssist for PowerHA on IBM i Sample PowerHA Assist Commands ADDCADUSR - adds all user profiles in the Admin Domain Create user profile exit point to auto add user profiles on creation DLTPRFCLU - delete profiles around a cluster CHKDUPLIBS - check for duplicate libraries in SYSBAS and IASP across the cluster CHKENVRCY Analysis tool for files, journals etc to ensure an unscheduled switch can come online as fast a possible Global Mirror statistics programs to monitor performance and recovery points SET/RTVFACT control the PowerHA failover actions to be able to turn on/off automatic failover for specific cluster events STRALLNOD - start all cluster nodes Sample programs for automatically starting PowerHA and Geographic mirroring on IPL RTVCPYSSN - used multiple API s to retrieve PowerHA session status and primary node information into a CL program

36 IBM Lab Services Offerings for PowerHA for IBM i PowerHA Service Offering IBM i High Availability Architecture and Design Workshop PowerHA for IBM i Bandwidth Analysis IBM i Independent Auxiliary Storage Pool (IASP) Workshop PowerHA for IBM i Implementation Services Description An experienced IBM i consultant will conduct a planning and design workshop to review solutions and alternatives to meet HA/DR and backup/recovery requirements. The consultant will provide an architecture and implementation plan to meet these requirements. An experienced IBM i consultant will review network bandwidth requirements for implementing storage data replication. IBM will review I/O data patterns and provide a bandwidth estimate to build into the business and project plan for clients deploying PowerHA for IBM i. An experienced IBM i consultant will provide jumpstart services for migrating applications into an IASP. Training includes enabling applications for IASPs, clustering techniques, plus managing PowerHA and HA/DR solution options with IASPs. An experienced IBM consultant will provide services to implement an HA/DR solution for IBM Power Systems servers with IBM Storage. Depending on specific business requirements, the end-to-end solution implementation may include a combination of PowerHA for IBM i and/or PowerHA Tools for IBM i, plus appropriate storage software such as Metro Mirror, Global Mirror and/or Flashcopy. For more information on PowerHA Tools for IBM i offerings and services, contact: Mark Even even@us.ibm.com stgls@us.ibm.com

37 A PowerHA and storage options Recommend viewing IBM i POWER External Storage Support Matrix Summary TechDoc - PRS and Quick reference - Storage options for PowerHA SystemMirror for IBM i TechDoc - TD Internal SAS/SSD DS8000 SVC V840,V9000 Storwize XIV DS5000 Other Storage Geographic Mirroring Metro Mirror Global Mirror Metro Global Mirror LUN switching FlashCopy HyperSwap Coming note: no global mirror link

38 PowerHA for IBM i HA solutions for the 21 st Century PowerHA storage based HA/DR solutions are based on shared storage clustering configurations Logical replication solutions Complexity and time required to manage software replication Fear of failover associated with software replication tools Upgrade and maintenance $$$ of software Tape Backup takes too long Staffing required to manage software replication Service and Support PowerHA Solution Clustering technology implemented in SLIC eliminates complexity uncertainty Designed for automated role swap and failover operations Concurrent maintenance for OS upgrades, PTF applies, hardware maintenance Flashcopy eliminates backup by enabling save operations concurrent to production Operational simplicity staffing is a fraction of what is required with software replication IBM service and support

39 Session summary PowerHA for IBM i Highly automated solutions for high availability and disaster recovery HA/DR solutions based on IBM storage or on internal disk solution Ultra low cost modern HA/DR solutions for small customer shops Several ways to save money: CBU, CBU for PowerHA, Enterprise Pools Lab Services brings expertise and added value like smart assists Resources..new redbooks, the wiki, join the PowerHA on i Linkedin group