Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

High Availability og virtualisering, IBM Power Event


Published on

Power-platformen er ideel til virtualisering og konsolisering, og det stiller store krav til sikring af data i tilfælde af nedbrud. Få en præsentation af IBM's nye muligheder for at sikre stabil og sikker drift.

Erik Rex, Consulting IT Specialist, IBM

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

High Availability og virtualisering, IBM Power Event

  1. 1. IBM Power SystemsHigh Availability ConsiderationsIBM i Erik Rex Cert Consultant Specialist IBM Danmark aps © 2012 IBM Corporation
  2. 2. Downtime Causes Of Downtime Solution Required Disaster Recovery High Availability Downtime refers to a period of time or a (Continuous percentage of a time span that a machine or system (usually a computer server) is Operations) offline or not functioning, usually as a result of either system failure (such as a crash or routine maintenance. Source: IBM HA Presentation, Eric Hess, April 2001 * ‘HA’ generally refers to solutions that provide BOTH recovery and availability. Not all technologies provide a solution for BOTH…iTera 5.0 HA does Reliability is not the same as Availability!2 © 2012 IBM Corporation
  3. 3. Business Continuity is: Capability of a business to withstand outages and operate mission critical services normally and without interruption per a pre-defined Service Level Agreement – Solution must address data, operational environment, applications, the application hosting environment, and the end user interface – Requires a collection of services, software, hardware, and procedures to be selected, described in a documented plan, implemented, and practiced regularly Includes both Disaster Recovery (DR) and High Availability (HA) – DR addresses the set of resources, plans, services and procedures to recover and resume mission critical applications at a remote site in the event of a disaster – HA defined as the ability to withstand all outages (planned, unplanned, and disasters) and to provide continuous processing for all mission critical applications3 © 2012 IBM Corporation
  4. 4. What is a Service Level Agreement (SLA)? General: – Contractual service commitment. – A document that describes the minimum performance criteria a provider promises to meet while delivering a service. – Typically also sets out the remedial action and any penalties that will take effect if performance falls below the promised standard. Relative to Availability: – Commitment to the business describing the level of availability for IT services that support critical business solutions. – Addresses when IT services are expected to be fully operational, when they may be running degraded, and when they won’t be available – Driven primarily be importance of IT services in providing business solutions, cost factors, and realism. Many factors involved4 © 2012 IBM Corporation
  5. 5. Application Resilience Combine with Data Resilience for complete solutionFully transparent• Full resilience with automatic restart & transparent failover• Users repositioned to last committed transaction• No data loss, no sign-on required, no perceived loss of server; HA enabled only delay in response applications and iSeriesSemi-transparent: Huh? Did Clusters• Automatic application restart & recovery to last transaction boundary something happen?• The resilient data & the application restart point match exactly iSeriesSemi-automatic: Clusters• Automatic application restart & recovery to some architected Checkpoint restart. Data application “restart” point Not too bad . resiliency• Normally consistent with state of data, but user may have to manually match application to position of data Single ServerBasic application failover: Start over.• Automatic application restart after outage Wheres all my work?• User manually repositions within applicationNo application recovery:• Users manually restart application with resilient data• User determines where to resume work5 © 2012 IBM Corporation
  6. 6. The FundamentalsRecovery or Continuity ? Clustering Application Resiliency Data Resiliency – IASPs, Replication Transaction Integrity - Journaling Data Protection - Raid 5 & Mirroring Data Replication alone is not sufficient for HA Clustering, Automation and application resiliency completes the equation6 © 2012 IBM Corporation
  7. 7. Clustering for HA/DR Clustering is the default deployment for HA/DR in the mainframe and Unix marketplace With PowerHA SystemMirror, clustering is available to our IBM i customers Provides for automated failover – minimal IT operations involvement Planned and unplanned outage management7 © 2012 IBM Corporation
  8. 8. Clustering Data Application Resiliency Resiliency A property of the Operating Replication High System and Cluster availability Switched Management cluster Provides the logical connections IASPs enabled iSeries Navigator between resilient data groups or partner products applications Can enable the automation of APIs physical and logical switching Cluster Resource Services Can enable a resilient application Base IBM i cluster functions from IBM to be “switched”, activated and Heart beating repositioned to a defined state IP Address Takeover Enables the automatic sequencing Reliable internal cluster communications of events that bring the user, Switchover administration application and data to a coherent Distributed activities production state automatically Application design is the primary limiting factor8 © 2012 IBM Corporation
  9. 9. Data Resilience Technologies Logical Replication – Business partner software product •Vision Solution, Quick EDD, iCluster Switchable Device – Switchable IASPs Operating System Storage Management based Replication – PowerHA System Mirror Cross-Site Mirroring (XSM) with Geographic Mirroring SAN Storage Server based Replication – SAN Metro/Global Mirror used with PowerHA IBM I Advanced Copy Service toolkit9 © 2012 IBM Corporation
  10. 10. Logical Replication Second copy of data is generated logically identical Backup (target system) to first Tape Replication done on object basis (file, member, data area, program, etc.) near real-time Normally done via a business partner software product10 © 2012 IBM Corporation
  11. 11. Logical Replication Backup (target system) Tape Widely deployed data resiliency topology for Power IBM i – Typically deployed via an HA Business Partner solution package – Replication done on object basis (file, data area, program, etc.) near real-time • Done at the lowest unit of change for the object, e.g. record level for database files • Otherwise, done on entire object when change detected by replication software • Solution Packages can use IBM i Remote Journaling as efficient, reliable transport mechanism. Benefits: – Rapid activation of production environment on backup server via role-swap operation – Replicated data can be concurrently accessed for backups or other read-only apps – Minimal recovery is needed when switching over to the backup copy Considerations: – Complexity of setup and maintenance – Modification of ‘live’ copies of objects on backup server – Lag time between changes on source being available on backup server – Consistency between journaled and non-journaled objects11 © 2012 IBM Corporation
  12. 12. Switchable IASPs Independent Auxiliary Storage Pools (IASPs) – IBM i Option 41 - High Availability Switchable Resources – Switch disks from one system to another Benefits: – Simplicity – Data is always current (no copy to synchronize) – No in-flight data to lose – Minimal performance overhead – Supports integrated environments (Windows, Linux) as well as IBM i Considerations: – Setup DASD configuration, data, and application structure – Single copy of data (mirroring recommended to protect data, reduce SPOFs) – No concurrent access from both hosts – HW restrictions (distance, conc maint)12 © 2012 IBM Corporation
  13. 13. Switchable DevicesPowerHA Basic Concepts (for IBM i clients) Admin domain (IASP) aka (volume group) Application dataThe underlying data resiliency is not based on replication it is based on a pool of disk which isshared and switchable between nodes in the clusterPowerHA SystemMirror enables the cluster nodes to behave as resource for the applications inthe event of an outageAdmin Domain takes care of the sysbas data13 © 2012 IBM Corporation
  14. 14. PowerHA Standard Edition Switchable LUNs *SYSBAS (DR) F (IASP) S Primary l S Secondary e e s a s s h C IASP o Flash Flash p Backup Backup y *SYBAS (Backup I) POWER7 POWER7 IBM i DS8000 IBM i © Non disruptive backups Data Centre14 © 2012 IBM Corporation
  15. 15. PowerHA SystemMirror Strategy Deep Integration – Cluster Aware IBM i – SLIC based event processing – Centralize cluster topology management Ease of deployment & ease of use – System Director Navigator management – Discovery based deployment – Cluster wide security Multi-Site & Disaster Recovery – Differentiate with IBM storage – Integrated IBM copy services Solution Package Optimization – Standard Edition, Enterprise Editions15 © 2012 IBM Corporation
  16. 16. PowerHA SystemMirror(Cross-Site Mirroring) (XSM) with Geographic Mirroring Second copy of data in an IASP is generated logically identical to first Changes to production IASP replicated to second copy of IASP thru another system Operating system storage management based replication solution Primary (source system) Backup (target system) Production Data Backup Mirror Copy16 © 2012 IBM Corporation
  17. 17. PowerHACross-Site Mirroring (XSM) with Geographic Mirroring Mirroring of IASP data via IBM i storage management to a second server – XSM Included in Option 41 of OS – Enables switching or automatic failover to mirrored copy of IASP Primary (source system) Benefits: – Same as switched device Production Backup (target system) Data – Two copies of IASP data – Can be local or remote (Sync or Async) Backup Mirror – Ease of deployment and operation Copy – Supports integrated environments (Windows, Linux) as well as IBM i Client partitions – Heartbeat monitoring with automate failover or manual switchover Considerations: – Performance impacts of synchronous operation, distance, bandwidth, latency – Mirror copy cannot be concurrently access – Lengthy full data re-synchronization17 © 2012 IBM Corporation
  18. 18. PowerHA Basic Concepts Admin domain GeomirrorInternal disk is not switchable (LUNs required), you use geomirror with internal disk configurations18 © 2012 IBM Corporation
  19. 19. PowerHA Metro/Global Mirror with IBM i Advanced Copy Services toolkit Replication of iASP data at storage controller level to Backup SAN using Metro or Global Mirror – Metro or Global Mirror generates a second copy of the IASP on another Storage server – Toolkit part of Power IBM i Advanced Copy Services for IBM i offering – Combines Metro/Global Mirror, PowerHA, IASP, and IBM i cluster services – Coordinated switchover/failover Benefits: iSeries Cluster – Remote copy and coordinated switching without an IPL and Device Dom ain – Can combine with FlashCopy for backup window reduction Considerations: – Performance impacts of synchronous mode: distance, bandwidth, latency – Mirror copy cannot be concurrently accessed – Asynchronous mode requires IBM SAN Global Mirror – Requires tools and services to deploy19 © 2012 IBM Corporation
  20. 20. PowerHA Enterprise Edition Two Node Cluster Admin domain *SYSBAS *SYSBAS (DR) (Prod) Metro Mirror POWER7 IBM i F IASP IASP (Switchable) Global Mirror l HA DR a s h C IASP DR HA o Flash p Backup y *SYBAS (Backup I) POWER7 POWER7 IBM i DS8000 DS8000 IBM i Production SVC* SVC Storewize V7000* Storewize V7000 © Local Site DR Site * Initially available English only via prpq 5799 HAS20 © 2012 IBM Corporation
  21. 21. PowerHA Enterprise Edition Three Node Cluster DR Site LUN Group (active) Production Admin domain *SYSBAS *SYSBAS (DR) (Prod) MetroMirror POWER7 IBM i F IASP IASP (Switchable) Global Mirror l DR a s h C IASP HA o Flash p Backup *SYBAS y *SYBAS (Backup I) (Backup I) POWER7 POWER7 IBM i DS8000 DS8000 IBM i SVC* SVC* Storewize V7000* Storewize V7000* © Local Site DR Site21 © 2012 IBM Corporation
  22. 22. Redundant VIOS I/O Virtualization Redundant VIOS partitions provide VIOS VIOS two paths to attached SAN storage – AIX, i, and Linux partitions Power Hypervisor – One set of disk – Client partitions use MPIO Redundant VIOS partitions provide access to mirrored SAN VIOS VIOS storage – AIX, i, and Linux partitions Power Hypervisor – Mirrored set of disk – Mirroring done by client partitions (e.g., IBM i)Note: Redundant VIOS partitions are not supported on BladeCenter JS12, JS22, JS23, and JS4322 © 2012 IBM Corporation
  23. 23. PowerVM can Help Manage Risk Business and IT security and resiliency are as critical as ever, and must be dynamic and intelligent in order to match the speed of business change PowerVM Live Partition Mobility – Move running IBM I, AIX and Linux partitions between systems – Using VIOS Virtualized SAN and Network Infrastructure Virtualized SAN and Network Infrastructure√ Eliminate planned outages and balance workloads across systems23 © 2012 IBM Corporation
  24. 24. IBM i Capacity Back Up (CBU) Licensing ExamplePlanning CBU allows PowerHA licenses Production CBU entitlement fail-over from the registered Partition #1 production server Unused – Minimum 1 entitlement required on the CBU box – CBU server allows the temporary transfer of entitlements from primary server for non concurrent usage on the CBU server – Round-up when using partial processors – 3.5 processors = 4 entitlements Partition #2Example Active standby No HA/DR required for Partition 1 CBU Cores – No PowerHA licenses HA required for Partition 2 and 3 – All processors in the production server partitions 2 and 3 are licensed for PowerHA Partition #3 – One key, 8 entitlements – The license key will be a permanent Active standby key installed on partition 2 and 3 CBU Cores A single processor is licensed on the CBU server – One key, one entitlement IBM i, 5250, PowerHA – The license key will be a temporary key for 8 cores good for two years24 installed on partitions 2 and 3 © 2012 IBM Corporation
  25. 25. Key Solutions Comparison Characteristics 1. Primary use 8. Number of Backup systems 2. Characteristic of Replication 9. Number of Data copies allowed Mechanism 10. Cost Factors 3. Recovery Time 11. End User 4. Recovery Point 12. Outage coverage 5. Ordering of changes 13. Cluster controlled resource 6. Concurrent access 14. Risks 7. Geographic dispersion Consider other decision factors25 © 2012 IBM Corporation
  26. 26. Applicability of Solution to Problem Set Start to determine possible matches of technologies to specific needs 1. Initial analysis to eliminate technologies that do not fit 2. After initial analysis, perform detailed analysis of complete requirement sets against specific characteristics of each technology Data Resilience Technologies Logical Switched disk PowerHA PowerHA with replication Copy Services toolkit Backup WindowBusiness Continuity n/a Reduction Requirement Planned Maintenance Recovery for n/a disaster outage HA for unplanned outage Workload n/a n/a n/a Balancing 26 © 2012 IBM Corporation
  27. 27. Conclusions When to consider Logical Replication? – Need two or more copies of the data – Want some level of concurrent access to second data copy – Need backup window reduction – Already have solution deployed using logical object replication – Need a solution that has no special hardware configuration requirements – Transaction level integrity is important for all journaled objects When to consider Switchable IASPs ? – Single copy of data meets requirements; addressed exposure to disk subsys failures – Need a very simple, low cost, low maintenance solution – No need for DR solution – Source and target system will be at the same site – Want consistent fail/switchover times within minutes independent of transaction volumes – Need transaction level integrity for all objects; no loss of in-flight data – Need highest throughput environment – Need multiple, independent databases that can be moved between systems27 © 2012 IBM Corporation
  28. 28. Conclusions (2) When to consider PowerHA System Mirror (Cross-Site Mirroring) ? – Want a system-generated second copy of the data (at an IASP level) – Need two copies of data, but do not need concurrent access to second copy – Want relatively low cost, low maintenance solution, but also need disaster recovery – Want consistent fail/switchover times within minutes independent of transaction volumes When to consider PowerHA Metro/Global Mirror with IASP and Toolkit ? – Want storage based solution for HA; especially if multiple platforms are involved – Want consistent fail/switchover times within minutes independent of transaction volumes – Need two copies of data, but do not need concurrent access to second copy28 © 2012 IBM Corporation
  29. 29. Conclusions (3) When to consider a combination solution? – When no single solution meets all of your business continuity requirements29 © 2012 IBM Corporation
  30. 30. Power Systems30 © 2012 IBM Corporation
  31. 31. Summary: Data Application Clustering PLUS Resiliency Resiliency Data replication PLUS Replication and Cluster High availability Switched cluster Cluster enabled replication IASPs Management iSeries Navigator enabled or partner products applications EQUALS ’real’ HA APIs Cluster Resource Services Base IBM i cluster functions from IBM Heart beating Data Replication alone is not sufficient for IP Address Takeover HA Reliable internal cluster communications Switchover administration Clustering, Automation and application Distributed activities resiliency completes the equation31 © 2012 IBM Corporation
  32. 32. PowerHA Global/Metro PowerHA w/ Geographic Mirror w/ IASP Logical Replication Switchable IASPs Mirroring & iTC ToolkitPrimary use HA (including DR) HA (no DR) HA (including DR) HA (including DR) Object based replication; No replication; Page level replication as Sector level replication of changes at record or 1 copy of data that is controlled by operating all pages written to disk. object level based on data switchable between system based on storageCharacteristic & audit journal. systems management writes. Physical copy of an IASPof replication based on disk I/O (cache mechanism Logical copy of object Logical copy since based). level changes for selected physical DASD configs objects. can differ. Apply lag + replication IASP Vary on IASP vary on IASP vary on switchover overhead. Recovery Journal settings SMAPP / Journal settings SMAPP / Journal settings SMAPP / Journal settings Time Considera- No IPL required No IPL required No IPL required tions No IPL required Minutes Minutes Minutes Minutes Transaction boundary Transaction boundary Transaction boundary Transaction boundary with commitment control. with commitment with commitment control. with commitment control. Recovery Mixed – audit and data control. Last data written to IASP. Last data written to IASP. Point journal. Data / objects Last data written to IASP. Considera- sent to target will be tions recovered. Lose changes Objects not in IASP. Objects not in IASP. not xmitted (zero data loss Objects not in IASP. 32 with synch remote jrn). © 2012 IBM Corporation
  33. 33. PowerHA Metro/Global PowerHA w/ Mirror w/ IASP Logical Replication Switchable IASPs Geographic Mirroring & iTC Toolkit Based on journal Ordering preserved Ordering at system Ordering at controller receiver content & level. Ordering level. Preserved atOrdering HABP ability to preserved across LUN (disk) level for of synchronize changes ASP group. Metro Mirror.changes from data & audit Consistency groups journals. for Global Mirror. Typically read only, No concurrent No concurrent access No concurrent possibly shared data. access since no . access. Always some lag time copy of data Copy current withConcurre in data currency. Flash Copy.nt access Remote Journal Consistency groups helps. define lag time for Global Mirror. Geo Virtually unlimited Limited (250 M) Virtually unlimited Virtually unlimitedDispersio n # Back 1<= n <127 n=1 1<= n <=3 1<=n<=2 up (or BP max) (with switchable (2 or 3 with (2 with cascadingsystems towers) switchable towers) Metro Mirror) # data 127 (or BP max) none 1 2 33 © 2012 IBM Corporation copies
  34. 34. PowerHA w/ PowerHA Metro/Global Logical Replication Switchable IASPs Geographic Mirroring Mirror w/ IASP & iTC Toolkit Any DASD Switchable tower (or Any (flexible) DASD Ext DASD configuration. HABP IOP) configuration. 57xx-HAS Cost software. Bandwidth. IBM i Option 41 57xx-HAS Bandwidth. Factors Duplicate disks. Bandwidth. Duplicate Toolkit. Duplicate disks. disks. Replication overhead. Can automatically Geographic mirroring Metro/Global MirrorEnd User Can automatically restart application. overhead. overhead.Disruption restart application. Can automatically Can automatically restart application. restart application. Planned, unplanned, Planned, unplanned Planned, unplanned, Planned, unplanned, Outage disaster, save window disaster, save window disaster, save windowcoverage Cluster Yes Yes Yes Yes – of switchable control devices Loss of in flight data. Disk subsystem is Asynch case: can lose Somewhat complex Mismatch of data single point of copy on double failure Asynch via Global levels for various failure, therefore no if cannot quiesce & vary- Mirror. protection against off. Risks objects. Disk protection catastrophic disk Resynch after detach Monitoring logical provided by Ext. failure may yield lengthy object replication Storage. unprotected condition. 34 environment © 2012 IBM Corporation
  35. 35. PowerHA Webcast V1.0PowerHA for IBM i Resources PowerHA Website – PowerHA Options for IBM i - Introduction (incl. 7.1) – PowerHA and DS8000 Storage Integration on IBM i – Lab Services – Redbooks at – PowerHA SystemMirror for IBM i Cook book - SG24-7994 (Jan 2012) – Implementing PowerHA for IBM i - SG24-7405-00 (Nov 2008) – Clustering and IASPs for Higher Availability - SG24-5194-01 – Independent ASPs: A Guide to Moving Applications to IASPs - SG24-6802-00 – Independent ASP Performance Study on the IBM iSeries - REDP-3771-00 – Implementing SAP Applications on the IBM System i with IBM i5/OS - SG24-7166-00 IBM System Storage Solutions for IBM i – Course code: AS930, Duration: 4.0 days – Is your ISV solution registered as ready for PowerHA? – High Availability Clusters (Power HA) and Independent Disk Pools for IBM i – Course code: AS541,OS830 Duration: 4.0 days – Risk Self Assessment: – © 2012 IBM Corporation © Copyright IBM Corporation 2011
  36. 36. Special notices This document was developed for IBM offerings in the United States as of the date of publication. IBM may not make these offerings available in other countries, and the information is subject to change without notice. Consult your local IBM business contact for information on the IBM offerings available in your area. Information in this document concerning non-IBM products was obtained from the suppliers of these products or other public sources. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. Send license inquires, in writing, to IBM Director of Licensing, IBM Corporation, New Castle Drive, Armonk, NY 10504-1785 USA. All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. The information contained in this document has not been submitted to any formal IBM test and is provided "AS IS" with no warranties or guarantees either expressed or implied. All examples cited or described in this document are presented as illustrations of the manner in which some IBM products can be used and the results that may be achieved. Actual environmental costs and performance characteristics will vary depending on individual client configurations and conditions. IBM Global Financing offerings are provided through IBM Credit Corporation in the United States and other IBM subsidiaries and divisions worldwide to qualified commercial and government clients. Rates are based on a clients credit rating, financing terms, offering type, equipment type and options, and may vary by country. Other restrictions may apply. Rates and offerings are subject to change, extension or withdrawal without notice. IBM is not responsible for printing errors in this document that result in pricing or information inaccuracies. All prices shown are IBMs United States suggested list prices and are subject to change without notice; reseller prices may vary. IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply. Any performance data contained in this document was determined in a controlled environment. Actual results may vary significantly and are dependent on many factors including system hardware configuration and software design and configuration. Some measurements quoted in this document may have been made on development-level systems. There is no guarantee these measurements will be the same on generally- available systems. Some measurements quoted in this document may have been estimated through extrapolation. Users of this document should verify the applicable data for their specific environment. Revised September 26, 200636 © 2012 IBM Corporation
  37. 37. Special notices (cont.)IBM, the IBM logo, AIX, AIX (logo), AIX 5L, AIX 6 (logo), AS/400, BladeCenter, Blue Gene, ClusterProven, DB2, ESCON, i5/OS, i5/OS (logo), IBM BusinessPartner (logo), IntelliStation, LoadLeveler, Lotus, Lotus Notes, Notes, Operating System/400, OS/400, PartnerLink, PartnerWorld, PowerPC, pSeries, Rational, RISCSystem/6000, RS/6000, THINK, Tivoli, Tivoli (logo), Tivoli Management Environment, WebSphere, xSeries, z/OS, zSeries, Active Memory, Balanced Warehouse,CacheFlow, Cool Blue, IBM Systems Director VMControl, pureScale, TurboCore, Chiphopper, Cloudscape, DB2 Universal Database, DS4000, DS6000, DS8000,EnergyScale, Enterprise Workload Manager, General Parallel File System, , GPFS, HACMP, HACMP/6000, HASM, IBM Systems Director Active Energy Manager,iSeries, Micro-Partitioning, POWER, PowerExecutive, PowerVM, PowerVM (logo), PowerHA, Power Architecture, Power Everywhere, Power Family, POWER Hypervisor,Power Systems, Power Systems (logo), Power Systems Software, Power Systems Software (logo), POWER2, POWER3, POWER4, POWER4+, POWER5, POWER5+,POWER6, POWER6+, POWER7, System i, System p, System p5, System Storage, System z, TME 10, Workload Partitions Manager and X-Architecture are trademarksor registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms aremarked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM atthe time this information was published. Such trademarks may also be registered or common law trademarks in other countries.A full list of U.S. trademarks owned by IBM may be found at:, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/orother countries.AltiVec is a trademark of Freescale Semiconductor, Inc.AMD Opteron is a trademark of Advanced Micro Devices, Inc.InfiniBand, InfiniBand Trade Association and the InfiniBand design marks are trademarks and/or service marks of the InfiniBand Trade Association.Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registeredtrademarks of Intel Corporation or its subsidiaries in the United States and other countries.IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce.Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.Linux is a registered trademark of Linus Torvalds in the United States, other countries or both.Microsoft, Windows and the Windows logo are registered trademarks of Microsoft Corporation in the United States, other countries or both.NetBench is a registered trademark of Ziff Davis Media in the United States, other countries or both.SPECint, SPECfp, SPECjbb, SPECweb, SPECjAppServer, SPEC OMP, SPECviewperf, SPECapc, SPEChpc, SPECjvm, SPECmail, SPECimap and SPECsfs aretrademarks of the Standard Performance Evaluation Corp (SPEC).The Power Architecture and wordmarks and the Power and logos and related marks are trademarks and service marks licensed by and TPC-H are trademarks of the Transaction Performance Processing Council (TPPC).UNIX is a registered trademark of The Open Group in the United States, other countries or both.Other company, product and service names may be trademarks or service marks of others. Revised December 2, 2010 37 © 2012 IBM Corporation