High Availability and Scalability with System z and z/os

Transcription

1 High Availability and Scalability with System z and z/os Joachim von Buttlar, Robert Vaupel IBM Deutschland Research & Development GmbH

2 Who is Who? Joachim von Buttlar System z Firmware Development Joachim_von_buttlar@de.ibm.com Robert Vaupel z/os Workload Management Development and Design IBM Senior Technical Staff Member vaupel@de.ibm.com 2

3 WS 2010/2011: Structure and Content CPU Architecture Register sets Memory organization Virtual storage Interrupt mechanism Timing facilities Instruction set Multiprocessing facilities I/O Architecture I/O infrastructure Adapter types & channels Control unit & devices Extensions for large configurations Partitioning and virtualization LPAR versus z/vm Differences and commonalities Hardware facilities Storage management Processor management I/O management z/os Address space concept Task execution and serialization Program communication and data exchange Data formats, data sets and I/O flow z/os subsystems: TSO, ISPF, JES z/os Dispatching and Hiperdispatch z/os Workload Management Parallel Sysplex Cluster concepts Parallel Sysplex structure and exploitation Data Mirroring and Global Dispersed Parallel Sysplex Data mirroring Middleware Integration and Software Architecture Date (always Fridays) :30-13:00 Introduction and Orientation System z Architecture System z Architecture z/os Introduction z/os Dispatching and Virtualization z/os Parallel Sysplex z/os Workload Management Wrap-Up and Closing 14:00-15:30 System z Architecture System z Architecture System z Architecture z/os Introduction z/os Dispatching and Virtualization z/os Workload Management z/os and System z Software Architecture 3

4 What is System z? IBM z Enterprise z196 IBM System z10 EC System /360 A System System z z server server is is what what businesses businesses use use to to host host the the largest largest commercial commercial databases, databases, transaction transaction servers, servers, and and applications applications that that require require a a greater greater degree degree of of security security and and availability availability than than is is commonly commonly found found on on smaller-scale smaller-scale machines. machines. 4

5 System z Architecture S/360 architecture is based on von Neumann s computing model: S/360 = 360 One hardware architecture One operating system For all IBM computers S/360 architecture got invented and documented in the S/360 Principles of Operation in 1964 by: Gene Amdahl Fred Brooks Garry Blaauw

6 System z and z/os History MVT SVS MVS/370 MVS/XA MVS/ESA OS/390 z/os MFT Fixed Storage 15 Partitions or Tasks One 16MB VS Area Address Spaces Multiple Virtual Storage 2 GB Virtual Storage Expanded Storage Virtual I/O Fast Program Load Dynamic I/O Posix Cluster Parallel Sysplex Workload Management Unix System Services TCP/IP... Java Websphere IEEE Float 64 bit IRD Hiperdispatch Offload Security GDPS April 1964 Introduction of S/360 Architecture Symmetric Multi Processing Virtual Memory Expanded Storage 2GB Addressing LPAR Access Registers Data-spaces CMOS Technology Parallel Sysplex 64bit Addressing S/360 S/370 S/390 z Architecture 6

7 Mainframe Computing Mainframes are computers which Execute hundreds of applications Connect to thousands of I/O devices And serve thousands of users simultaneously Mainframes can best be defined by their characteristics The most important characteristic is to ensure a reliable and predictable execution of transactions The importance of mainframes is for data base transaction processing and as the backend in data centers 7

8 Economical Importance: Why System z and z/os All companies which have the need to store huge amounts of data require Security Scalability Compatibility Availability Reliability Serviceability 95% of the 2000 world-wide biggest companies use System z computers Around 65-70% of all relevant data are stored on System z computers 60% of all data being access thru the world wide web are stored in databases on System z (DB2, VSAM, and IMS) 8

9 High Availability and Scalability System z Hardware Overview and Introduction System z Usage in Customer Environments RAS capabilities What does High Availability and Scalability mean? 9

10 Elements of System z Architecture Central Processor Units Up to 64 PUs Main Memory Byte-wise addressable 64-bit addressability 'shared' between all CPU s I/O Subsystem old': parallel (copper), 4.5 MB/sec 1990: serial (fiber), 17 MB/sec 1999: FiCON (fiber), 270 MB/sec ESCON & FiCON 'Director' Switch Control Units (CU) Managing unit Devices Hard disk, tape, printer, etc. Network (GbE,...) 10

11 Heart of System z Architecture: MCM MCM = Multi Chip Module Processor Units (PU), Storage Controller (SC), SEEPROM (S) and clock functions Integration increases with each generation, example: z9: 8 PUs per MCM with up to 2 cores z10: 5 PUs per MCM with up to 4 cores z196: 6 Pus per MCM with up to 4 cores A single MCM can provide 24 processors on a z196 but a z196 can have up to 96 processors (80 usable for workloads) 11

12 z196 PU chip, SC chip and MCM 12

13 z196 Book Layout Backup Air Plenum 16X DIMMs 100mm High 1800W Refrigeration Cooled or Water Cooled 8 I/O FAN OUT 2 FSP Rear Memory MCM Fanout Cards Front DCA Power Supplies Memory 13 3x DCA 11 VTM Card Assemblies 8 Vertical 3 Horizontal 14X DIMMs 100mm High Cooling from/to MRU

14 z196 Water cooled Under the covers (Model M66 or M80) front view 14

15 z196 Frames On z196: Traditional System z Operating Systems: z/os, Linux, zvse, zvm On z196 Blade Extensions: Power 7 Blades, System x Blades Integration via Unified Resource Manager 15

16 Growth of System z Servers Growth encompasses Speed: from z900 (770MHz) to z196 (5.2 GHz) Integration of processors and chips on same MCM Number of MCMs per system And now with z196 Integration of Blade Server z/os release used for LSPR measurements z196 measurements are for a xx-way PCI - (Processor Capacity Index 16

17 17 A typical System z could look like this z/vm V4 C M S L i n u x C M S L i n u x LPAR L i n u x V S E z/os z/ V S E z/ O S z/vm L i n u x L i n u x LPAR LPAR LPAR L i n u x z/ V S E CP1 CP2 CP3 CP4 IFL1 IFL2 IFL3 System z Enterprise Server J a v a z/vm L i n u x LPAR Standard Processors LPAR L i n u x z/vse ziip D B 2 Offload Engines Linux Engines C I C S I M S S A P zaap L i n u x L i n u x L i n u x C I C S B a t c h

18 System z Processor Characterization Central Processor (CP) Provides processing capacity for z/architecture and ESA/390 instruction sets Runs z/os, z/vm, z/vse, z/tpf, Linux for System z System Assist Processor (SAP) SAPs manage the start and ending of I/O operations for all LPARs and all attached I/O Each machine has at least one SAP Internal Coupling Facility (ICF, since 1997) Provides additional processing capacity for the execution of the Coupling Facility Control Code (CFCC) in a CF LPAR Integrated Facility for Linux (IFL, since 2001) Provides additional processing capacity for Linux workloads IBM System z Application Assist Processors (zaap, since 2004) Provides additional processing capacity for Java workloads under z/os IBM System z Information Integration Processors (ziip, since 2006) Provides additional processing capacity for certain DB2 workloads under z/os Spares Provides extra processing capacity in case of any failure of any PU SAP, ICF, IFL, zaap, ziip offer the same functionality as CPs Lower price than CP Do not affect traditional System z software charges 18

19 Why is System z different? Many different types of workloads Business Critical workloads Running systems at very high utilizations Access to systems is always required 19

20 System z Quality of Services RAS Reliability Availability Serviceability Security / Integrity Scalability Manageability Centralized control Workload management Virtualization / Partitioning Technology Workload separation Capacity Evolving architecture Flexibility / Variety Multiple workloads, multiple users Compatibility Capability Autonomic features 20

21 System z: RAS Design Focus High Availability (HA) The attribute of a system designed to provide service during defined periods, at acceptable or agreed upon levels and masks UNPLANNED OUTAGES from end-users. It employs fault tolerance, automated failure detection, recovery, bypass reconfiguration, testing, problem and change management. Continuous Operations (CO) Attribute of a system designed to continuously operate and mask PLANNED OUTAGES from end-users. It employs non-disruptive hardware and software changes, non-disruptive configuration, software coexistence. Continuous Availability (CA) Attribute of a system designed to deliver non-disruptive service to the end user 7 days a week, 24 HOURS A DAY (there are no planned or unplanned outages). It includes the ability to recover from a site disaster by switching computing to a second site. High Availability Continuous Availability Continuous Operations 21

22 Business Issue of Non-Availability On demand challenges Downtime unaffordable Heterogeneous by nature Complex to manage Hardw are Failures Unplanned Outage Causes 30% 45% 25% Operator Errors Application Failures IDC 2005 Loss of business Loss of customers the competition is just a mouse click away Loss of credibility, brand image and stock value E.g. Toll Collect : The state of Germany and the company collecting toll on the autobahn agreed on a contractual penalty of 30 Million for each 1 hour of down time (represents / min). 22 9/30/2010 Template Documentation

23 Continuous Availability / Disaster Recovery Single System Clustering in a Box Parallel Sysplex Geographical Dispersed PS MTBF in decades Built-In redundancy On/Off Capacity on Demand Capacity Backup Hot pluggable I/O Using an ICF, a single CEC (Central Electronic Complex) Parallel Sysplex can be defined Maintenance on LPAR without loss of data Protection from software outages 1 to 32 Systems Site 1 Site 2 Addresses planned and unplanned HW/SW outages Flexible, non-disruptive growth Capacity beyond largest CEC Scales better than SMPs Dynamic workload / resource management Addresses site failure / maintenance Metro / Global data mirroring Sync (PPRC) 100 km Async (XRC) any distance Eliminates tape / disk Single Point of Failure (SPOF) No / Some data loss Application independent 23

24 Scalability xx 6xx 5xx 4xx 1-way 2-way 3-way 4-way 5-way 6-way 7-way 8-way 4xx 5xx 6xx 7xx Model S Scale-up Example for System z9 Allows installations to choose the capacity they need in a granular fashion and to grow when business needs require it 24

25 What does the Course Encompass? How High Availability and Scalability is implemented on System z System z Technology and Hardware Operating System (z/os) and Partitioning Technology Focus: Dispatching Cluster Technology to achieve Continuous Availability Parallel Sysplex Capability to execute many different workloads at the same time and meet business objectives Workload Management Integration of Software, Operating System and Hardware 25

26 What to Remember? What technology steps have been invented to reach high availability and scalability Why a technology is exploited in System z On a high level How software, operating system and hardware work together And why do they work together 26

27 27

28 Literature Introduction to the New Mainframe: Large-Scale Commercial Computing ABCs of z/os System Programming Volume 11, Documents for Workload Management z/os Workload Manager: How It Works and How To Use It, April Adaptive algorithms for managing a distributed data processing workload Das Betriebssystem z/os und zseries, M.Teuffel, R.Vaupel, ISBN

29 Trademarks The following are trademarks of the International Business Machines Corporation in the United States and/or other countries. APPN* CICS* DB2* DB2 Connect DirMaint e-business logo* ECKD Enterprise Storage Server* ESCON* FICON* GDPS* Geographically Dispersed Parallel Sysplex * Registered trademarks of IBM Corporation HiperSockets HyperSwap IBM* IBM eserver IBM e(logo)server* IBM logo* IMS Language Environment* MQSeries* Multiprise* NetView* On demand business logo OS/390* Parallel Sysplex* PR/SM Processor Resource/Systems Manager RACF* Resource Link RMF S/390* Sysplex Timer* System z9 TotalStorage* Virtualization Engine VM/ESA* VSE/ESA VTAM* WebSphere* z/architecture z/os* z/vm* z/vse zseries* The following are trademarks or registered trademarks of other companies. Java and all Java-related trademarks and logos are trademarks of Sun Microsystems, Inc., in the United States and other countries Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Microsoft, Windows and Windows NT are registered trademarks of Microsoft Corporation. Red Hat, the Red Hat "Shadow Man" logo, and all Red Hat-based trademarks and logos are trademarks or registered trademarks of Red Hat, Inc., in the United States and other countries. SET and Secure Electronic Transaction are trademarks owned by SET Secure Electronic Transaction LLC. * All other products may be trademarks or registered trademarks of their respective companies. Notes: Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance ratios stated here. IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply. All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics will vary depending on individual customer configurations and conditions. This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without notice. Consult your local IBM business contact for information on the product or services available in your area. All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. Information about non-ibm products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the 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. Prices subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your geography. 29