Click to add text Introduction to the new mainframe: Large-Scale Commercial Computing © Copyright IBM Corp., 2006. All rights reserved. Chapter 5: Availability.

Introduction to the new mainframe © Copyright IBM Corp., 2006. All rights reserved. 2 Objectives The ability to: Understand what availability means to a commercial enterprise Describe the inhibitors to availability Describe operating system facilities that improve availability Describe the major components of Parallel Sysplex

Introduction to the new mainframe © Copyright IBM Corp., 2006. All rights reserved. 3 A real customer requirement: Royal Bank Boosts Availability - Online Banking Front End - Internet Back End - Data/Applications  Challenge: Maximize Availability 12 million customers  2.5 million online 60,000 employees  Benefits Reliable integration with internet Supports ~40 web-based applications Efficient use of parallel sysplex Improved customer availability IBM System z Parallel Sysplex System DB2 Database IMS Database CICS Applications WebSphere MQ For z/OS, V5.3

Introduction to the new mainframe © Copyright IBM Corp., 2006. All rights reserved. 4 Client Server Architecture 2 tier and 3 tier Architecture thin vs thick client maintenance and change issues Microsoft vs IBM

Introduction to the new mainframe © Copyright IBM Corp., 2006. All rights reserved. 5 What is availability? Availability is the state of an application being accessible to the end user. e.g. 13 years without a visible customer outage

Introduction to the new mainframe © Copyright IBM Corp., 2006. All rights reserved. 6 Definitions: High availability: The infrastructure (or applications) cannot undergo an unplanned outage for more than a few seconds or minutes without serious impact the business. Acceptable to bring down the application for a few hours for scheduled maintenance. Continuous availability: The infrastructure and applications cannot be interrupted at all. No allowance for any outage, either unplanned or planned. 99.999% availability- just over 5 minutes per year of all outages in total.

Introduction to the new mainframe © Copyright IBM Corp., 2006. All rights reserved. 7 Introduction to availability High Availability Fault-tolerant, failure- resistant infrastructure supporting continuous application processing Continuous Operations Non-disruptive backups and system maintenance coupled with continuous availability of applications Disaster Recovery Protection against unplanned outages such as disasters through reliable, predictable recovery Protection of critical business data Recovery is predictable and reliable Operations continue after a disaster Costs are predictable and manageable

Introduction to the new mainframe © Copyright IBM Corp., 2006. All rights reserved. 8 Outage Definition An outage (unavailability) is the time, a system is not available to an end user. Outages may be planned or unexpected (unplanned). -Planned outages include causes like data base reorganisation, release changes, and network reconfiguration. -Unplanned outages are caused by some kind of a hardware, software or data problem While planned outages can be scheduled, they still are disruptive. The modern trend is to try to avoid planned outages altogether. This requires extensive hardware and software facilities.

Introduction to the new mainframe © Copyright IBM Corp., 2006. All rights reserved. 9 Cost of outages (1) Financial Impact of Downtime Per Hour (by various Industries) Source: Contingency Planning Research & Strategic Research Corp.

Introduction to the new mainframe © Copyright IBM Corp., 2006. All rights reserved. 12 Inhibitors to availability Number of 9s – or the Myth of the nines Class of 9sOutageExample 99,999 %5 min / yearContinous Availability z/OS Parallel Sysplex 99,99 %53 min / yearFault TolerantS/390 Parallel Sysplex 99,9 %8,8 hrs / yearHigh Availability Single IBM System z CPC 99 %88 hrs / yearGeneral Purpose High available UNIX Cluster 90 %876 hrs / yearCampus LAN

Introduction to the new mainframe © Copyright IBM Corp., 2006. All rights reserved. 13 Redundancy Hardware – IBM Mainframe Power  2x Power Supply  2x Power feed Internal Battery Feature  Optional internal battery in cause of loss of external power) Cooling Dynamic oscillator switchover Processors  Multiprocessors  Spare Processing units Memory  Chip sparing  Error Correction and Checking ….Distance concept and codes

Introduction to the new mainframe © Copyright IBM Corp., 2006. All rights reserved. 14 Concurrent Maintenance and Upgrades – fewer outages Duplex Units  Power Supplies, Concurrent Microcode (Firmware) updates Hot Pluggable I/O e.g. Stratus Comp co. PU Conversion Permanent and Temporary Capacity Upgrades  Capacity Upgrade on Demand (CUoD)  Customer Initiated Upgrade (CIU)  On/Off Capacity on Demand (On/Off CoD) Capacity BackUp (CBU)

Introduction to the new mainframe © Copyright IBM Corp., 2006. All rights reserved. 15 CBU Server Production Server Capacity BackUp (CBU) Who Needs It? Any business with a requirement for increased availability or Disaster Recovery What Is It? The ability to nondisruptively increment capacity temporarily, Dual Microcode Loads  Provide two machine configurations in one box Take advantage of "spare" PUs Significant cost savings possible  Standby MIPS cost can be eliminated  IBM Software license charges on standby MIPS can be eliminated Configure memory and channels to support production workload How Can I Use It? Adjacent machines in the same location Multiple images in the same Parallel Sysplex® cluster Backup/Recovery site

Introduction to the new mainframe © Copyright IBM Corp., 2006. All rights reserved. 16 Absolute Storage Space 123 Physical Memory 1 2 Example: Absolute storage increment “123” is concurrently moved from physical memory increment 1 to physical memory increment 2. EBR (E... Backup Restore)- Dynamic Memory Move The Dynamic Memory Move operation - concurrently changes the physical memory backing of an absolute storage increment Performed transparent to the Operating System Utilizes the zSeries Copy/Reassign Hardware Used during EBA to:  Move physical memory usage from the targeted book to books that will be remaining in the system.  Optimize memory allocation after EBA completion.  EBA = Enhanced Book Availability

Introduction to the new mainframe © Copyright IBM Corp., 2006. All rights reserved. 17 EBR - Redundant I/O Interconnect (RII) STI Multipath Module (STI-MP) A multiplexer that supports attachment to four I/O features in an I/O domain and has an alternate path to a second STI-MP for a redundant I/O infrastructure. Key Usage Memory Upgrade Dynamic MBA fanout error recovery Reduction of UIRA outage Book Repair STI cable repair MBA fanout card repair On book add MBA fanouts used for I/O are concurrently rebalanced to the new book

Introduction to the new mainframe © Copyright IBM Corp., 2006. All rights reserved. 18 PU6 PUxPUy Logical Physical EBR - Concurrent Physical Processor Reassignment This operation is used for concurrently changing the physical backing of one or more logical processors The state of source operating physical processor is captured and transplanted into the target physical processor. Expected to be transparent to the operating system. Utilizes the PU sparing function Used during EBA to:  Move processors from the targeted book to spare processors on a book remaining in the system  Rebalance processors after EBA completion.

Introduction to the new mainframe © Copyright IBM Corp., 2006. All rights reserved. 20 RAS Features of an Storage Subsystem Independent dual power feeds N+1 power supply technology/hot swappable power supplies, fans N+1 cooling Battery backup Non-Volatile Subsystem cache, to protect writes that have not been hardened to DASD yet Nondisruptive maintenance Concurrent Licensed Internal Code (LIC) activation Concurrent repair and replace actions RAID architecture Redundant microprocessors and data paths Concurrent upgrade support (that is, ability to add disks while subsystem is online) Redundant shared memory Spare disk drives Remote Copy to a second storage subsystem  Synchronous (Peer to Peer Remote Copy, PPRC)  Asynchronous (Extended Remote Copy, XRC)

Introduction to the new mainframe © Copyright IBM Corp., 2006. All rights reserved. 21 Disk Mirroring using PPRC and XRC Peer to Peer Remote Copy(PPRC) -Metro Mirror Synchronous remote data mirroring  Application receives “I/O complete” when both primary and secondary disks are updated Typically supports metropolitan distance Performance impact must be considered  Latency of 10 km Extended Remote Copy(XRC) -z/OS Global Mirror Asynchronous remote data mirroring Application receives “I/O complete” as soon as primary disk is updated Unlimited distance support Performance impact negligible System Data Mover (SDM) provides Data consistency of secondary data Central point of control

Introduction to the new mainframe © Copyright IBM Corp., 2006. All rights reserved. 22 PPRC Failover / Failback (FO/FB) The new primary volumes (at the remote site) records changes while in failover mode. The original mode of the volumes at the local site is preserved as it was when the failover was initiated. Only need to resynchronize from time of failover, not entire data set A B Sync PPRC A B Normal Application I/Os A B Sync PPRC (suspended) A B Application I/Os Failover A B Sync PPRC (full duplex) A B Application I/Os Failback Finish CRCR A B Sync PPRC (full duplex) A B Application I/Os Failback Start OOSOOS

Introduction to the new mainframe © Copyright IBM Corp., 2006. All rights reserved. 23 Parallel Sysplex Removes Single Point of Failure  Server  LPAR  Subsystems Planned and Unplanned Outages Single System Image Dynamic Session Balancing Dynamic Transaction Routing Highlights  Data sharing  Locking  Cross-system workload dispatching  Synchronization of time for logging, etc. Hardware/software combination  Coupling Facility  Sysplex Timer – TOD clock synchronization  Workload Manager in z/OS  Compatibility and exploitation in software subsystems, like DataSharing in Database systems IBM System z

Introduction to the new mainframe © Copyright IBM Corp., 2006. All rights reserved. 24 z/OS factors to availability -Workload Balancing using Workload Manager (WLM) -Capability to restart applications using the Automatic Restart Manager (ARM) without interfering Assists Two-Phase commits using Resource Recovery Services (RRS) Make dynamicly changes to your system configuration using the System Modification Program Extended (SMP/E)

Introduction to the new mainframe © Copyright IBM Corp., 2006. All rights reserved. 26 z/OS Recovery z/OS Recovery features Recovery Termination Manager (RTM) Extended Specify Task Abnormal Exit (ESTAE) Functional Recovery Routine (FRR)

Introduction to the new mainframe © Copyright IBM Corp., 2006. All rights reserved. 27 The Human Factor …. Automation: critical for successful rapid recovery and continuity The More People Involved….. ….. The Higher the Odds of Human Errors. The benefits of automation: Allows business processes to be built on a reliable, consistent recovery time Recovery times can remain consistent as the system scales to provide a flexible solution designed to meet changing business needs Reduce infrastructure management cost and staffing skills Reduces or eliminates human error during the recovery process at time of disaster Facilitates regular testing to help ensure repeatable, reliable, scalable business continuity Helps maintain recovery readiness by managing and monitoring the server, data replication, workload and the network along with the notification of events that occur within the environment

Introduction to the new mainframe © Copyright IBM Corp., 2006. All rights reserved. 28 Today’s Business Require Rapid Database Availability Achieve Application and Database Restart Consistent, repeatable, fast Database Restart: To start a database application following an outage without having to restore the database  This is a process measured in minutes Avoid Application and Database Recovery Unpredictable recovery time, usually very long and very labor intensive Database Recovery:  Restore last set of Image Copy tapes and apply log changes to bring database up to point of failure  This is a process measured in hours or even days!!!

Introduction to the new mainframe © Copyright IBM Corp., 2006. All rights reserved. 29 SITE 1 NETWORK 1 12 2 3 4 5 6 7 8 9 10 11 SITE 2 NETWORK 1 12 2 3 4 5 6 7 8 9 10 11 What is GDPS/PPRC? (Metro Mirror) Multi-site base or Parallel Sysplex environment Remote data mirroring using PPRC Manages unplanned reconfigurations z/OS, CF, disk, tape, site Designed to maintain data consistency and integrity across all volumes Supports fast, automated site failover No or limited data loss - (customer business policies) Single point of control for Standard actions  Stop, Remove, IPL system(s) Parallel Sysplex Configuration management User defined script (e.g. Planned Site Switch) PPRC Configuration management 100 km

Click to add text Introduction to the new mainframe: Large-Scale Commercial Computing © Copyright IBM Corp., 2006. All rights reserved. Chapter 5: Availability.

Similar presentations

Presentation on theme: "Click to add text Introduction to the new mainframe: Large-Scale Commercial Computing © Copyright IBM Corp., 2006. All rights reserved. Chapter 5: Availability."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Click to add text Introduction to the new mainframe: Large-Scale Commercial Computing © Copyright IBM Corp., 2006. All rights reserved. Chapter 5: Availability.

Similar presentations

Presentation on theme: "Click to add text Introduction to the new mainframe: Large-Scale Commercial Computing © Copyright IBM Corp., 2006. All rights reserved. Chapter 5: Availability."— Presentation transcript:

Similar presentations

About project

Feedback