Post on 09-Apr-2018
1
© 2012 IBM Corporation
IBM Power Systems
IBM PowerHA™ SystemMirror for i& Independent ASPs
Jenny Dervin – jdervin@us.ibm.com
© 2012 IBM Corporation
IBM Power Systems
2
Virtualization without Limits
� Drive over 90% utilization
� Dynamically scale per demand
Dynamic Energy Optimization
� 70-90% energy cost reduction
� EnergyScale™ technologies
Resiliency without Downtime
� Roadmap to continuous availability
� High availability systems & scaling
Management with Automation
� VMControl to manage virtualization
� Automation to reduce task time
Workload-Optimizing Systems
AIX - The Future of UNIX
Total Integration with i
Scalable Linux ready for x86 Consolidation
Systems for a Smarter Planet
Power your Planet
+
2
© 2012 IBM Corporation
IBM Power Systems
3
PowerHA SystemMirror
� Complete IBM Power Systems integrated end to end solutions for HA DR – Focus: 24x 7 Application availability through planned or unplanned outage events
– Deeply integrated extension of AIX and IBM i (implemented in SLIC and the OS)
� Clustering technology – Clustering provides the applications a complete resiliency infrastructure
– Cluster monitors and manages primary and secondary resources for HADR operations
� Storage based data resiliency– Data resiliency is an extension of the host system storage management architecture
– Storage volumes are either switchable or mirrored between nodes in the cluster
– Hardware based replication services for Multi-Site Operations
• Host Based Replication (geomirroring for IBM i, or GLVM for AIX)
• Storage Base Replication (Metro Mirror or Global Mirror)
� Overall solution characteristic – Automation, minimal IT operations involvement
– Data between primary and secondary nodes always in sync always ready for a failover event
© 2012 IBM Corporation
IBM Power Systems
4
� 6.1 5761-HAS: PowerHA 6.1 licensed program• IBM i HA Switchable Resources (5761-SS1 Option 41) required for 5761-
HAS
• Requires IBM i 6.1 or higher
• HA Switchable resources option 41 is an OS function that facilitates resilient resources and copies of IASPs
� 7.1 5770-HAS: PowerHA System Mirror 7.1 licensed program• New name, with new functions and enhancements
• Requires IBM i 7.1
• HA Switchable Resource included in 5770-HAS PowerHA System Mirror 7.1
(no separate OS option 41 to order with 5770-HAS)
– Standard Edition
– Enterprise Edition
� IBM i 6.1 and 7.1 Lab Services Advanced Copy Services (ACS)– Complements PowerHA with additional automation and functions
High Availability Solutions
3
© 2012 IBM Corporation
IBM Power Systems
5
PowerHA SystemMirror 7.1 for i Offering
$4,500
$3,500
$2,500
Data Center HA (per core)
Standard Edition
$6,500
$5,000
$3,250
Multi Site HA/DR (per core)
Enterprise Edition
Scale
Offering Focus
PowerHA SystemMirror for i
Small Tier
Blade & Entry Power
Medium Tier
Mid-range Power
Large Tier
Enterprise Servers
� Standard Edition PID 5770-HAS
� Enterprise Edition is a feature of 5770-HAS and is the multi site solution
� No charge upgrades from PowerHA 6.1 to 7.1 Standard Edition or Enterprise Edition
� HASR (opt 41) is included with purchase of PowerHA SystemMirror 7.1
� Sub capacity pricing, license only the cores in the partitions covered by PowerHA
US list prices, prices vary by geo, GA April 23 2010
© 2012 IBM Corporation
IBM Power Systems
6
PowerHA in a CBU Configuration� IBM’s server offering for i clients is the CBU for i:
– One HASR “opt 41” required per system (no charge with the purchase PowerHA SystemMirror
7.1)
– You license only the cores in the partition's), being used for HA/DR support
– Only one PowerHA LPP on each corresponding HA partition on your CBU box
– Get PowerHA temp keys for the other standby cores in the HA partition(s) on your CBU box
Primary CBU
6 active cores
4 PowerHA 1 HASR
6 active cores
1 PowerHA1 HASR
3 PowerHA Temp Keys
AIXAIX application is running on this corehas no bearing on CBU t’s&c”s
4
© 2012 IBM Corporation
IBM Power Systems
7
Geographic Mirroring
• Synch
• Any storage
• Direct, VIOS, IBM i Hosted
storage
IBM i 7.1 PowerHA SystemMirror for i
MetroMirror
• Synch
DS6000
DS8000
SVC
V7000
• NPIV
FlashCopy
• Snapshot
• DS6000
DS8000
SVC
V7000
• Space
Efficient
• NPIV
SwitchedIASPs
• Internal or
external
storage
• IOA or
Tower **
End-to-EndSolution
*** Switchable towers limited to POWER6®
and prior hardware - avoid
GlobalMirror
• Asynch
• DS6000
DS8000
SVC
V7000
• NPIV
Geographic Mirroring
• Asynch
• Any storage
• Direct, VIOS, IBM i Hosted
storage
LUN Level Switching
• IASP is
located
inside DS
• DS6000
DS8000
only
Hess - 2010
An end-to-end solution for management of IBM i 6.1 and 7.1 and DS6000 and DS8000®
resiliency and replication technologies for HA, DR and backups
IBM i Cluster Resource Services
DSCLI DS Command Line Interface
HA Switchable Resources - IBM i option 41
PowerHA SystemMirror for i
(5770-HAS) – 7.1
© 2012 IBM Corporation
IBM Power Systems
8
PowerHA – Synchronous Geographic Mirroring
–IBM i OS based data replication solution
–Target server is active, and can be used for other workloads
–IASP on target cannot be accessed while replication is active
–Synchronous means that changed page must be received and acknowledged on target copy
before production write completes
–Requires sufficient network bandwidth and not advised for long distances
Source Target
IASP IASP
LPAR-1
*SYSBAS
LPAR-1
*SYSBAS
ack
12
34
5
© 2012 IBM Corporation
IBM Power Systems
9
PowerHA – Asynchronous Geographic Mirroring
–IBM i OS based data replication solution
–Target server is active, and can be used for other workloads
–IASP on target cannot be accessed while replication is active
–Asynchronous means that local write can complete once it is buffered on the production side
–Supports greater distances, but still requires sufficient bandwidth and proper CPU, memory, disk planning
Source Target
IASP IASP
LPAR-1
*SYSBAS
LPAR-1
*SYSBAS
ack
12
32
© 2012 IBM Corporation
IBM Power Systems
10
PowerHA - Switched IASPs
– IASP is switched between partitions
• Switching between servers is not supported on POWER7. POWER6
TMis last server to
support HSL and switchable towers.
– Each partition takes turns using the IASP
– Other partition is active and can be used for other
activity
– Redundant partitions provide protection from
LPAR-specific planned and unplanned outages
– Cannot address disk outages or backups
• Disk Mirroring or RAID6 is a good idea
• Save-While-Active for backups
– Combine with replication solutions to address backups or DR
Basic Switched IASPs between LPARs
LPAR-1
*SYSBAS
LPAR-2
*SYSBAS
IASP
6
© 2012 IBM Corporation
IBM Power Systems
11
PowerHA - Metro Mirror
–PowerHA integrates storage-based replication with IBM i clustering infrastruction
–Synchronous replication ensures new production data is written to target first
–Excellent RPO and very good RTO
–An IASP based solution
–DS6000 or DS8000
• Direct attach or VIOS using NPIV
–SVC and Storwize V7000
• Requires 7.1
• VIOS attach only
ExternalStorage
HA
ExternalStorage
Local Site
MetroMirror
Production
*SYSBAS
IASP
*SYSBAS
IASP
PowerHA Metro Mirror
© 2012 IBM Corporation
IBM Power Systems
12
PowerHA - Global Mirror
HA
*SYSBAS
ExternalStorage
Local SiteExternalStorage
IASP
Consistency Group (C.G.)
Global Mirror
DR Site
DR
*SYSBASIASP
Continentaldistances
PowerHA Global Mirror–PowerHA integrates storage-based replication with IBM i clustering infrastruction
–Asynchronous replication allows for long distances
–An IASP based solution
–DS6000 or DS8000
• Direct attach or VIOS using NPIV
–SVC and Storwize V7000
• Requires 7.1
• VIOS attach only
7
© 2012 IBM Corporation
IBM Power Systems
13
LUN-level switching� DS6000 or DS8000 only
� One copy of iASP switched between 2 partitions/systems
� Can’t access from both systems at once
� Separate FC adaptors and PowerHA remaps host connections within the storage to switch
� Server level redundancy provides protection from server outage but not disk outage
OS and other
system data
OS and other
system data
DS8000
System i cluster servicesProduction
*SYSBAS
HA
*SYSBAS
IASP
© 2012 IBM Corporation
IBM Power Systems
14
PowerHA - FlashCopy
–FlashCopy is a very quickly executing point in time copy
• Bitmap keeps track of changes
• Copy takes place as a background operation
–IASP based solution
–FlashCopy options – full copy, no copy
–Space Efficient FlashCopy can reduce FlashCopy storage by 70-80%
–Use with 6.1 Quiesce to eliminate IASP vary off
–Advanced Copy Services for PowerHA can provide additional automation
DS8000
Prod LPAR
FlashCopy
*SYSBAS
IASP
IASPLPAR-2
(backup)
*SYSBAS
PowerHA FlashCopyTape Backup
8
© 2012 IBM Corporation
IBM Power Systems
15
Combination of Technologies
�Combine technologies for a complete solution
– Local HA for planned outages
– Disaster recovery
– Offline backups
Cluster Admin Domain
Sysbas Sysbas
Global MirrorIASP
Sysbas
IASP
FlashCopy
Lun level Switching
© 2012 IBM Corporation
IBM Power Systems
16
PowerHA SystemMirror Integration for Advanced HA and DR
� Metro/Global Mirroring
– Local copies for advanced HA, remote
copies for DR, testing and backups
� Advanced Copy Services (Lab Services)
– Integrates best of breed products for centralized monitoring and control of
complex environments
• PowerHA - DS8000 - TPC-R*
* TPC-R = Tivoli Productivity Center - Replication
DR1
DS8000
Prod
DS8000
HA
DS8000
IASPProd
Main Site
(HA)
IASPProd
Global Mirroring
Metro Mirror
Backupor Test
Disaster Recovery
Site
IASPProd
FlashCopy
PowerHA for i(automation & management)
TPC-R
DCopy
ACS(additional management)
9
© 2012 IBM Corporation
IBM Power Systems
17
Advanced Copy Services for PowerHA on i (ACS)� Complements PowerHA on i
� IBM Lab Services delivered tools and expertise
� Integration, Automation &
Training
� IBM i & DS8000, DS6000
storage advanced integration
� Customized HA/DR
configurations
� Simple one line command
operations
� Note: previous generations of ACS were referred to as
Lab Services ‘Toolkit’
Hess 2010
www-03.ibm.com/systems/resources/systems_services_labservices_stgls_advcpysvc_powerha_10.pdf
�Multi-site Metro-Global Mirror (MGM)
�DS5000 Copy Services
�Menu interface to manage DS environments
�Geographic Mirroring
�Support for internal disk
�
�
7.1
7.1
�
7.1
PowerHA ACSTechnology
�Metro Mirror for HA/DR
�TPC-R Support
7.1Automated failover (HMC Quorum device)
�Automated Quiesce / memory flush
�Automated cluster node start/stop
�
�
�
�
LUN Level Switching
Global Mirror for DR
Space efficient flash copy
One Command Planned switch over
© 2012 IBM Corporation
IBM Power Systems
18
Recent
Enhancements
10
© 2012 IBM Corporation
IBM Power Systems
19
DS8000 NPIV Support (7.1 TR2)
VIOS
POWER6 with IBM i 6.1.1
SYSBAS
IASP
8Gbs HBA
Hypervisor
VIOS 1
8Gbs HBA
VIOS 2 IBM i Client 1
� Each port is assigned separate WWPNs by the Hypervisor
� Each port is seen as a separate adapter by IBM i – so PowerHA resets it individually.
� Reduces the hardware for a single partition from 4 to 2 adapters for PowerHA
Note, This configuration can support up to 64 IBM i partitions without adding any more adapters
PowerHA for IBM i plus DS8000 NPIV (Virtual Fiber)
© 2012 IBM Corporation
IBM Power Systems
20
Recent Enhancements
SI44564SI443262011/10/14Inquiry message for duplicate libraries and spool files
during vary-on
-SI422972011/10/14N-2 Support
-SI457412012/04/14CFGGEOMIR command to configure geographic mirroring
-SI441412011/10/14CFGDEVASP command to create IASP
-SI457412012/04/16PowerHA GUI
-SI457412012/04/16Support for Storwise V7000, SVC Copy Services
6.1 PTF7.1 PTFRelease
Date
11
© 2012 IBM Corporation
IBM Power Systems
21
PowerHA
Building
Blocks
© 2012 IBM Corporation
IBM Power Systems
22
IASPs: Foundation for Long Term, Scalable HA/DR
IASP – Application -1
IASP – Application -2
IASP – Journaling
IASP with reduced
cost archive storage
ASP1 (SYSBAS)
User ASP(SYSBAS)
Hess 2010
Pools of disk which operate separately from SYSBAS
– Enables switching a disk pool within a cluster
– Contains the data that is replicated by the hardware
Foundation for all PowerHA and ACS solutions
Independent ASPs (IASPs) offer:
– Uptime
• Shorter IPLs – leave non-critical IASPs offline
• Reclaim Storage (RCLSTG) by IASP
– Security
• Data and path encryption by ASP
– Archive
• Storage performance and cost by IASP
– Consolidation
• Meet compliance needs for isolation
• SaaS (Software as a Service)
• Reduce software licensing fees (single OS)
• Reduce number of OS upgrades
12
© 2012 IBM Corporation
IBM Power Systems
23
� 5.4 / 6.1 / 7.1 Administrative Domain ‘Admin Domain’
– Changes on one node are propagated to others
• User profiles
• System Values
• Security
• Key configuration data
• (7.1) Authority lists (*AUTL)
• (7.1) Printer Device Descriptions (*PRTDEV)
� 6.1 / 7.1 HA Assist
– Low cost logical replication (flat priced, no tier) Replication for key *SYSBAS data
– Replicate DB2 for query use
– Use with or without Admin Domain
– Pre-requisite: requires PowerHA program product purchase on both servers
PowerHA - Environment Resiliency OptionsSynchronize non-IASP objects across systems in the cluster
PowerHA
Network
PROD (source) HA/DR (target)
LPAR-1 LPAR-2
IASP IASP
Admin Domain/HA Assist
© 2012 IBM Corporation
IBM Power Systems
24
� Administration Domain (part of PowerHA)
– Changes on one node are propagated to others
• User profiles• System Values
• Security• Key configuration data
PowerHA - Environment Resiliency OptionsSynchronize non-IASP (SYSBAS) objects across systems in the cluster
Additional Monitored Resources (6.1)• Subsystem Descriptions (*SBSD)
• Network Server Descriptions (*NWSD) of types *WINDOWSNT, *IXSVR, and *ISCSI.
• NWS Configurations (*NWSCFG)
• NWSH Device Descriptions (*NWSHDEV)
• NWS Storage Spaces (*NWSSTG)
• Tape Device Descriptions (*TAPDEV)
• Optical Device Descriptions (*OPTDEV)
• Ethernet Line Descriptions (*ETHLIN)
• Token-ring Line Descriptions (*TRNLIN)
Additional Monitored Resources (7.1)
• Authorization lists (*AUTL)
• Printer Device Descriptions (*PRTDEV)
Monitored Resources (5.4)• User profiles (*USRPRF)
• Class (*CLS)
• Job description (*JOBD)
• ASP device description (*ASPDEV)
• System values (*SYSVAL)
• Network attributes (*NETA)
• Environment variables (*ENVVAR)
• TCP/IP Attributes (*TCPA)
Hess 2010
13
© 2012 IBM Corporation
IBM Power Systems
25
Cluster Aware IBM i Operating System
� Node detects OS failure and sends distress messageto other nodes, triggering failover of apps
� Monitors for network failures via heartbeatingbetween nodes
– Node partitions and will automatically rejoin when communication is restored
� In 7.1, additional failures (hardware, power) can be detected by registering for HMC/IVM failure events
� Operator can initiate a switchover for a planned outage
© 2012 IBM Corporation
IBM Power Systems
26
PowerHA
Management
14
© 2012 IBM Corporation
IBM Power Systems
27
PowerHA SystemMirror Management Options
� Commands– Commands now included in PowerHA SystemMirror product– IBM i 5.4 level commands moved to QUSRTOOL library
� Cluster Resource Services GUI– Web application– Task-based approach similar to previous iNavigator GUI– Includes all PowerHA/clustering functionality– Allows a customized solution based on business needs
� PowerHA GUI– Web application– Simplified configuration and management– Currently available fully translated in 7.1– Does not yet support V7000, SVC, or lun-level switching– Future direction
• Support all PowerHA environments• Replaces existing GUI support
© 2012 IBM Corporation
IBM Power Systems
28
WRKCLU (command that does everything!)
15
© 2012 IBM Corporation
IBM Power Systems
29
Cluster Resource Services GUI
© 2012 IBM Corporation
IBM Power Systems
30
Updated PowerHA GUI
16
© 2012 IBM Corporation
IBM Power Systems
31
Updated PowerHA GUI
� Currently supports:
– Geographic mirroring
– Switched disk (IOA)
– DS8000 Metro Mirror
– DS8000 Global Mirror
– DS8000 FlashCopy
� Future plans to support
– V7000 / SVC Copy Services
– Lun-level switching
© 2012 IBM Corporation
IBM Power Systems
32
PowerHA SystemMirror for IBM i
�IBM System Director Navigator web based manager
�IBM i storage based data resiliency
�IBM i automated role over/ fail over
�IBM service and support
�IBM Metro Mirror
�IBM Global Mirror
�IBM i skill base for IT operations
�IBM i configuration synchronization
�IBM i cluster-wide administration
�IBM i multi site centralized point of control for HA/DR
�IBM i host based mirroring
�IBM i configuration tools
�IBM i system state synchronization
�IBM i cluster-wide resilient devices
PowerHA
� PowerHA SystemMirror is differentiated by IBM i storage
based data resiliency
� PowerHA is designed for automated HA/DR operations
� PowerHA skills are an extension IBM i skills
� WW IBM and BP community
support IBM i
17
© 2012 IBM Corporation
IBM Power Systems
33
A PowerHA Technology for Every Storage Type
NoNoNoYesYesNoFlashCopy
Yes (1)Yes (1)NoNoYes (1)Yes (1)Switched Disk
NoNoNoNoYesNoLUN switching
NoNoNoNoYesNoMetro Global Mirror
NoNoNoYesYesNoGlobal Mirror
NoNoNoYesYesNoMetro Mirror
YesYesYesYesYesYesGeographic
Mirroring
Other
StorageDS5000XIV
SVC
V7000
DS6000
DS8000
Internal
SAS/SSD
Note 1: Native attach only
© 2012 IBM Corporation
IBM Power Systems
34
IndependentASPs
18
© 2012 IBM Corporation
IBM Power Systems
35
IBM i - Single Level Storage
n Data spread across available disk arms (by ASP)
n Information is not necessarily contiguousn Objects are split into 1MB chunks
n Balanced by space occupancy
n Balances disk arm utilization
n Minimizes disk administration
IBM i
Data
© 2012 IBM Corporation
IBM Power Systems
36
Basic Auxiliary Storage Pools
� ASP -> a collection of disks used to isolate IBM i objects from other objects on another collections of disks
� Provides mechanism for grouping disks together.� Can be grouped to isolate data or for performance� ASP 1 == system ASP� ASP numbers 2-32 == Basic User ASPs� System ASP + Basic User ASPs == SYSBAS� User ASPs :
– Linked to system ASP– Cannot be independently varied on or off– Will overflow into system ASP
� CPW uses 3 ASPs– System ASP – programs, temp storage, system data– DB ASP – all workload database files– JO ASP – journal receivers. Unprotected to maximize write performance.
19
© 2012 IBM Corporation
IBM Power Systems
37
Multiple User ASPs
Data
ASP-1(System + Appl-1)
Data
Databasechanges
ASP-2(Journal Receiver)
ASP-3(Appl-2)
© 2012 IBM Corporation
IBM Power Systems
38
What is an IASP?
� IASP == Independent Auxiliary Storage Pool
� An IASP is a set of disk units which contain a collection of user objects that can be taken offline or
brought online independent of system activity or other IASPs
� Can be independently varied on and off
� Switchable between systems
� Identified by name via device description and internally by ASP number (33 – 255)
� IASP capability for IFS and IBM i objects included in
the base operating system since V5R2
20
© 2012 IBM Corporation
IBM Power Systems
39
Types of IASPs�UDFS IASP
– Can only contain IFS objects– Advantage is faster vary-on since DB recovery steps can
be skipped– Can be converted to Primary at a later time if library
objected are needed
�Primary IASP– Can contain IFS and library objects– May have 0 or more secondary IASPs linked to it
�Secondary IASP– Can contain IFS and library objects– Linked to one Primary IASP– Varied on and off with the Primary IASP– Used to isolate journal receivers from the data (similar to a
Basic ASP)
© 2012 IBM Corporation
IBM Power Systems
40
IASP Terminology
Auxiliary Storage Pool (ASP) --- or Disk Pool
System User
Basic Independent
Primary Secondary
(1 to n)UDFS
ASP Group
SYSBAS
21
© 2012 IBM Corporation
IBM Power Systems
41
Library name space
ASP Group
IASPs can be grouped together into an ASP group. *SYSBAS and an ASP group together becomes the "library name space"
Sys ASP
user ASPs
*SYSBAS
Primary
IASP
Secondary
IASPs
*SYSBAS
ASP Group
ASP Group
company 1 company 2
© 2012 IBM Corporation
IBM Power Systems
42
Multiple Databases = Multiple Name Spaces
*SYSBAS
Includes temporary objects
IASP 33
Mfg Data
IASP 34
HR Data
IASP 35Branch 1
Data
IASP 36Branch 2
Data
22
© 2012 IBM Corporation
IBM Power Systems
43
Additional Characteristics of IASPs
� Each ASP Group is represented as a separate DB2 database instance.
� Duplicate library names are allowed within different ASP groups on the same system.
� Duplicate library names are not allowed between SYSBAS (ASPs 1-32) and any IASP on the system.
� Each job or thread always has visibility to objects in SYSBAS but is ‘attached’ to, at most, one ASP group at a time.
� IASPs are not available after an IPL. They must be varied on.� IFS for an IASP is mounted to the root as /<IASPNAME> at vary on.� RDBDIRE for IASP DB activated at vary on
Most of the work associated with IASP enablement involves getting users and jobs “attached” to the appropriate IASP
© 2012 IBM Corporation
IBM Power Systems
44
IASPs: Single System Advantages
IASP – Application -1
IASP – Application -2
IASP – Journaling
IASP with reduced
cost archive storage
ASP1 (SYSBAS)
User ASP(SYSBAS)
Independent ASPs (IASPs) offer:
– Uptime
• Shorter IPLs – leave non-critical IASPs on-line
• Reclaim Storage (RCLSTG) by IASP
– Security
• Data and path encryption by ASP
– Archive
• Faster access than tape
• Storage performance and cost by IASP
– Consolidation
• Multiple versions of same application
• Server/partition consolidation
• Reduce software licensing fees (single OS)
• Reduce number of OS upgrades
– Isolation
• Isolate different applications
• Meet compliance needs for isolation
• SaaS (Software as a Service)
23
© 2012 IBM Corporation
IBM Power Systems
45
Geographic Mirroring
• Synch
• Any storage
• Direct, VIOS, IBM i Hosted
storage
IBM i 7.1 PowerHA SystemMirror for i
MetroMirror
• Synch
DS6000
DS8000
SVC
V7000
• NPIV
FlashCopy
• Snapshot
• DS6000
DS8000
SVC
V7000
• Space
Efficient
• NPIV
SwitchedIASPs
• Internal or
external
storage
• IOA or
Tower **
End-to-EndSolution
*** Switchable towers limited to POWER6®
and prior hardware - avoid
GlobalMirror
• Asynch
• DS6000
DS8000
SVC
V7000
• NPIV
Geographic Mirroring
• Asynch
• Any storage
• Direct, VIOS, IBM i Hosted
storage
LUN Level Switching
• IASP is
located
inside DS
• DS6000
DS8000
only
Hess - 2010
An end-to-end solution for management of IBM i 6.1 and 7.1 and DS6000 and DS8000®
resiliency and replication technologies for HA, DR and backups
IBM i Cluster Resource Services
DSCLI DS Command Line Interface
HA Switchable Resources - IBM i option 41
PowerHA SystemMirror for i
(5770-HAS) – 7.1
© 2012 IBM Corporation
IBM Power Systems
46
iASP Benefits (vs full system replication)
� Faster switching, no IPL
� No replicating OS, microcode, temp space
� Target system is online – just switch the data
� Better recovery – just data recovery steps
� Reduced bandwidth requirement
� Integrated with clustering
� BRMS networking integration
� Improved flexibility and masking planned outages
� Much simpler, automated switch process
� Consolidate workloads using separate iASPs
� Less impact for planned outages (PTF and OS upgrades)
24
© 2012 IBM Corporation
IBM Power Systems
47
OS upgrade process
1. Upgrade target system OS• Replication continues
• Upgrade happens on SYS with no data
2. Swap to target system• iASP upgraded during vary-on
• Data upgraded on first use
3. Upgrade other system
4. Start replication in reverse
© 2012 IBM Corporation
IBM Power Systems
48
Creating an IASP (new command in 7.1)
25
© 2012 IBM Corporation
IBM Power Systems
49
Creating an IASP (2)
© 2012 IBM Corporation
IBM Power Systems
50
Creating an IASP
26
© 2012 IBM Corporation
IBM Power Systems
51
Accessing an IASP
� INLASPGRP in job description– Used when users need access to IASP for daily work
– Anyone signing in under that job description will have access to the
IASP
– If the IASP is unavailable, user cannot sign on
� SETASPGRP– Command to access IASP within interactive session
– Will not affect submitted jobs
– Command will fail if IASP is unavailable
© 2012 IBM Corporation
IBM Power Systems
52
Accessing an IASP – via Job Description
27
© 2012 IBM Corporation
IBM Power Systems
53
Accessing an IASP – via SETASPGRP
© 2012 IBM Corporation
IBM Power Systems
54
Example:
DSPLIB *ALL *ALLAVL
Display Libraries
Libraries: *ALL
ASP
Opt Library Type Device
_ DBLIB PROD DLB1
_ JIMCDLB1 PROD DLB1
_ QRCL00033 PROD DLB1
_ QRCY00033 PROD DLB1
_ QRPL00033 PROD DLB1
_ QSYS00033 PROD DLB1
_ QSYS200033 PROD DLB1
_ SYSIB00033 PROD DLB1
_ #LIBRARY PROD
_ #RPGLIB PROD
IBM i commands have ASP parameter
� CRTLIB LIB(JIMCDLB1) ASP(*ASPDEV)
ASPDEV(DLB1)
� WRKLIB/DSPLIB LIB(*ALL) ASPDEV(*ALLAVL , ASPname, *SYSBAS, *ASPGRP, ........)
� SAVLIB, RSTLIB, ...
IASP Library Management
28
© 2012 IBM Corporation
IBM Power Systems
55
IFS Objects in IASPs
IFS objects are accessed in an IASP by specifying
the IASP directory name first in the path.
/ (root)
QSYS.LIB QIBM IASPn ( etc.)
QIBM QSYS.LIB ( etc. )
Path to QIBM in IASPn = ‘/IASPn/QIBM’
© 2012 IBM Corporation
IBM Power Systems
56
iASP Supported Objects Types as of IBM i 6.1 and 7.1
*WSCST
*VLDL
*USRSPC
*USRQ
*USRIDX
*TBL
*SYMLNK
*SVRSTG
*STMF
*SRVPGM
*SQLUDT
*SQLPKG
*SPLF
*PNLGRP*MENU*FNTRSC*CHTFMT
*SPADCT*OVL*JRN*DTADCT
*SCHIDX*OUTQ*JOBQ*DTAARA
*SBSD*NODL*JOBD*DIR
*QRYDFN*NODGRP*IGCDCT*CSI
*QMQRY*MSGQ*GSS*CRQD
*QMFORM*MSGF*FTR*CMD
*PSFCFG*MODULE*FORMDF*CLS
*NODGRP*MGTCOL*FNTTBL *CLD
*PGM*MEDDFN*FILE*CHRSF
*PDG*LOCALE*FIFO*BNDDIR
*PAGSEG*LIB*FCT*BLKSF
*PAGDFN*JRNRCV*DTAQ*ALRTBL
29
© 2012 IBM Corporation
IBM Power Systems
57
Object Types Which Don’t Belong in an IASP
*USRPRF*NWID*IGCTBL*CTLD
*RCT*NTBD*IGCSRT*CSPTBL
*S36*M36CFG*FLR*CSPMAP
SSND*M36*EXITRG*CRG
*SOCKET*MODD*EDTD*COSD
*PRDLOD*LIND*DSTMF*CNNL
*PRDDFN*JOBSCD*DOC*CFGL
*PRDAVL*IPXD*DEVD*AUTL
*NWSD*IMGCLG*DDIR*AUTHLR
Security Objects (Objects affecting security remain in SYSBAS)
Legacy Objects (Non strategic objects (i.e *36 must remain in SYSBAS)
Configuration Objects (System configuration objects have no use on another system)
Note: Object types in blue can be synchronized via Admin Domain
© 2012 IBM Corporation
IBM Power Systems
58
� Changes on one node are propagated to
others
• User profiles, System Values, Security, Key configuration data
PowerHA – Administrative Domain
Synchronize non-IASP (SYSBAS)
objects across systems in the
cluster
Additional Monitored Resources (6.1)• Subsystem Descriptions (*SBSD)
• Network Server Descriptions (*NWSD) of types *WINDOWSNT, *IXSVR, and *ISCSI.
• NWS Configurations (*NWSCFG)
• NWSH Device Descriptions (*NWSHDEV)
• NWS Storage Spaces (*NWSSTG)
• Tape Device Descriptions (*TAPDEV)
• Optical Device Descriptions (*OPTDEV)
• Ethernet Line Descriptions (*ETHLIN)
• Token-ring Line Descriptions (*TRNLIN)
Additional Monitored Resources (7.1)• Authorization lists (*AUTL)
• Printer Device Descriptions (*PRTDEV)
Monitored Resources (5.4)• User profiles (*USRPRF)
• Class (*CLS)
• Job description (*JOBD)
• ASP device description (*ASPDEV)
• System values (*SYSVAL)
• Network attributes (*NETA)
• Environment variables (*ENVVAR)
• TCP/IP Attributes (*TCPA)
Hess 2010
LPAR-1 LPAR-1
IASP IASP
HA (target)PROD (source)
SYSBAS SYSBAS
30
© 2012 IBM Corporation
IBM Power Systems
59
IASP Enablement Considerations
The majority of changes needed to support IASPs are work management oriented. IASP migration can generally be transparent to most end-users and application developers.
� Location of application objects
� Migrating data to the IASP
� Work Management related changes
� Application run time considerations
� Database considerations
� Additional considerations for multiple IASPs on a system
© 2012 IBM Corporation
IBM Power Systems
60
Location of Application Objects
*SYSBAS
�Objects not supported in IASP
�Exit programs, etc. that must be found in *SYSBAS
�Operational version of job control objects (SBSD, etc)
�Temporary objects�System libraries�Application program
objects?
ASP Group
�Permanent application
data objects
�Spool files (maybe)
�Journals & journal receivers
�Definitional version of job control objects (SBSD,
etc)
�Application program
objects ?
31
© 2012 IBM Corporation
IBM Power Systems
61
Location of Application Objects - Details
*SYSBAS
�Objects needed at system startup, or when an IASP is off-line– Startup program– Objects referenced in most system values and network attributes
– including QSYSLIB & QSYSLIBL– Exit programs– System monitoring software– System management utilities
�Objects referenced by a subsystem not attached to an IASP– JOBQs, routing programs, and JOBDs
�Some objects referenced by USRPRFs– JOBD– MSGQ– Attention program
© 2012 IBM Corporation
IBM Power Systems
62
Location of Application Objects - Details
IASP
�Database Objects & Application Data– The less database objects in SYSBAS, the better for
performance and ease of management
�Application IFS objects and directories– INLASPGRP on JOBD, and SETASPGRP command do not
affect IASP IFS visibility – Access via hierarchical structure– Single IASP: Create symbolic links in old *SYSBAS IFS
location, pointing to new location in IASP– Multiple IASPs? Make application ‘root agnostic” – set
environment variable for application root directory– Check any symbolic links remaining in SYSBAS to ensure
they reference the correct location– Change references to IFS objects moved to the IASP if
symbolic links not created. i.e. /QSYS.LIB/…
32
© 2012 IBM Corporation
IBM Power Systems
63
� Program objects in *SYSBAS or in IASP?– Single or multiple IASPs on system?
– Shared copy of application or single?
– Unsupported object types for IASP?
– No duplicate library names in IASP and SYSBAS
Location of Application Objects–*SYSBAS or IASP
© 2012 IBM Corporation
IBM Power Systems
64
Moving Objects into an IASP
33
© 2012 IBM Corporation
IBM Power Systems
65
IFS Objects in IASPs
IFS objects can be placed in an IASP using the rst
(Restore Object) command, usually from a save file.
Restore Object (RST)
Type choices, press Enter.
Device . . . . . . . ‘/QSYS.LIB/QGPL.LIB/SAVF2.FILE’
Objects:
Name . . . . . . . ‘ < path on save media > ‘
Include or omit . *INCLUDE
New object name . ‘/APPLEn/ < path in IASP > ‘
Restore Object (RST)
Type choices, press Enter.
Device . . . . . . . ‘/QSYS.LIB/QGPL.LIB/SAVF2.FILE’
Objects:
Name . . . . . . . ‘ < path on save media > ‘
Include or omit . *INCLUDE
New object name . ‘/APPLEn/ < path in IASP > ‘
© 2012 IBM Corporation
IBM Power Systems
66
IASP Set-Up Summary
� Decide whether program objects will be in *SYSBAS or in IASP
� Evaluate IFS directories and files to move to IASP– Create symbolic links in old *SYSBAS IFS location, pointing to new
location in IASP
� Populating IASPs with data– Use ASPDEV since RSTLIB default will put objects in *SYSBAS
– Cannot create files, tables, etc. into QSYS2nnnnn
– Journal objects must be in same ASP group as objects being journaled
� Create new companion libraries for library content to be split
between *SYSBAS and IASP
� Modify startup program to vary on IASP
34
© 2012 IBM Corporation
IBM Power Systems
67
Work Management Restrictions
� Certain system values cannot reference objects in an IASP– QACGLVL, QATNPGM, QAUDCTL, QCFGMSGQ, QCONSOLE,
QCTLSBSD, QIGCCDEFNT, QINACTMSGQ, QPRBFTR, QPRTDEV, QPWDVLDPGM, QRMTSIGN, QSRTSEQ, QSTRUPPGM, QUPSMSGQ, QUSEADPAUT
� These network attributes cannot reference objects in the IASP– ALRFTR, DDMACC, DFTMODE, MSGQ, OUTQ, PCSACC
� All objects referenced in user profiles must exist in *SYSBASE, except– Initial programs or initial menus (if jobd points to IASP)
– Output queues
� JOBQ and SBSD can exist in IASP, but should be copied to *SYSBAS
� QSYSLIBL & QUSRLIBL cannot contain libraries in an IASP
© 2012 IBM Corporation
IBM Power Systems
68
Subsystem Description Support (6.1)
� Can exist in an IASP, but cannot be started from the subsystem
� Support for associating an IASP with a subsystem description– All jobs running with the subsystem will use the specified ASP group namespace– Parameter added to subsystem description object– IASP must be available for subsystem to be active– The subsystem must be ended before the IASP can be varied off
35
© 2012 IBM Corporation
IBM Power Systems
69
Support for Job Queues in IASP (6.1)
� Job queue object can be created in IASP– Allows applications to run with IASP with fewer changes
� Operationally, identical to JOBQ in SYSBAS:– User can manipulate jobs (submit, hold, release, etc.) on JOBQ– User can manipulate JOBQ (clear, hold, release delete, etc.)
� Behavioral differences exist:– Jobs on JOBQ in IASP will not persist across vary off / vary on– Jobs on JOBQ in IASP will not be available on backup system after
switchover or failover– Equivalent to business partner replication products
© 2012 IBM Corporation
IBM Power Systems
70
IASP Application Considerations
� If program objects remain in SYSBAS:
– IASP should be varied on before starting the application if possible
– Otherwise,
• application time out may need to increase for vary on processing
– application must handle object not available (as result of vary off, etc.)
� Evaluate use of SBMJOB and any commands with ASPDEV
parameter to ensure desired behavior
� Can use Vary on/off exit programs for IASP to perform application
startup and shutdown processing
� Be aware of any ripple affects of removing libraries from QSYSLIBL /
QUSRLIBL
36
© 2012 IBM Corporation
IBM Power Systems
71
IASP Application Considerations
� Modify job descriptions for user profiles
– Set initial ASP group for user profiles associated with the application
� Evaluate SBSDs for changes or attachment to IASP
– AJEs, PJEs, JOBQs, Routing programs
� JOBDs needed by the system should be moved to *SYSBAS
– Remove library qualified references
– Make any needed updates to INLLIBL
– JOBDs needed by the system should not have INLASPGRP set
– JOBDs accessing IASP data should have INLASPGRP set
© 2012 IBM Corporation
IBM Power Systems
72
IASP Application Considerations
� Determine how application will access specific IASP (name space)
– Job description’s INLASPGRP is most transparent to users
– Use SETASPGRP to switch between IASPs and/or SYSBAS
– If issuing SETASPGRP programmatically:
• Set library list parameters correctly
• Verify the command won’t be issued in a situation where
SETASPGRP is not allowed ( PDM, attention handling
program )
• In a multiple IASP environment, close any open files, release
object locks, and RCLRSC to release any program pointers.
37
© 2012 IBM Corporation
IBM Power Systems
73
IASP Database Considerations
� Views, tables cannot span IASP boundary– No join logicals over physicals in different IASPs or IASP and SYSBAS
� Multi-IASP SQL queries allowed via 3 part SQL names
� Commitment control behavior– If connected to IASP DB, cannot commit changes against both IASP
and *SYSBAS (except QTEMP) – pre V7R1
– V5R4 and earlier – commit definition scoped to IASP only
– IBM i 6.1 – commit definition scoped to IASP or SYSBAS, but not both, based on object of first commit action.
If connected to IASP, can use remote DRDA connection to SYSBAS and 2-phase commit, but not between IASPs.
– IBM i 7.1 – can commit changes to both IASP and SYSBAS in the same commit definition – uses 2 phase commit.
© 2012 IBM Corporation
IBM Power Systems
74
IASP Database Considerations
� RDB name for IASP– Single IASP on system, may want to give the old *LOCAL RDB
name to the IASP instead.
� DDM files– Configure to use RMTLOCNAME(*RDB) and RDB(iasp DB
name)
� New permanent libraries or collections for application:– CRTLIB LIB(library-name) ASP(*ASPDEV) ASPDEV(asp-device-
name)
– Create collection – default for ASPDEV is the current database
38
© 2012 IBM Corporation
IBM Power Systems
75
IASP Database Considerations
� Static SQL with Multiple IASPs
– When a static SQL program is run, an access plan is created and
stored with the program. If the SQL program is located in
*SYSBAS, a job/thread with IASP1 in its namespace will create
an access plan for data in IASP1. When a job/thread with IASP2
in its namespace runs the SQL program, the existing access plan
is invalid, so a new access plan will be created and stored in the
program
– Create separate static SQL applications /packages in each IASP
for best performance.
© 2012 IBM Corporation
IBM Power Systems
76
IASP Database Considerations
� JDBC, ODBC, FTP connectivity– Use JOBD of USRPRF to set INLASPGRP where possible– JDBC and ODBC have parameters to specify the Database
connection to allow for connection to an IASP
• FTP - Use the "quote rcmd xxxxx" to SETASPGRP for jobs that cannot have the *JOBD set the namespace
� JDBC - parameter in the i Java Toolbox to connect to IASP database
DriverManager.registerDriver(new AS400JDBCDriver());AS400JDBCDataSource ds = new AS400JDBCDataSource(“SYS1");
ds.setUser("xxxxxxxx");ds.setPassword("yyyyyyyy");ds.setNaming("sql");ds.setDatabaseName(“IASP1");
39
© 2012 IBM Corporation
IBM Power Systems
77
IASP Database Considerations
� ODBC – i Access for Windows ODBC driver parameter to connect
to IASP database
SQLAllocHandle(…);
SQLSetEnvAttr(…);
SQLAllocHandle(…);
SQLDriverConnect(hdbc, NULL, "DSN=myDSN;DATABASE=IASP1;UID=myUID;PWD=myPWD;", SQL_NTS, NULL, 0, NULL, SQL_DRIVER_NOPROMPT) ;
© 2012 IBM Corporation
IBM Power Systems
78
Other Considerations for Multiple IASPs
� Can use DRDA and DUW to connect to data in one IASP from
programs in another IASP
� Remember, each environment will share SYSBAS!
– Shared QUSRSYS, QGPL
– Shared LPPs
– Shared QSYSOPR
� A uniquely-named library for each IASP should be created in
*SYSBAS for:
– JOBDs, SBSDs, CLSs, etc.
� Place library in front of QGPL in the user's library list
40
© 2012 IBM Corporation
IBM Power Systems
79
IASPFlashCopy
CHGASPACT Function (6.1)� Suspends transactions & operations to ensure that as much in-flight data as
possible is written to disk– Places transactions at database boundaries if possible
•Use commitment control for maximum effectiveness
� Operates against individual IASPs or *SYSBAS� Useful prior to FlashCopy of *SYSBAS, FlashCopy of IASP, detaching of mirror
copy, switching of mirror copy� Command or API support
– CHGASPACT *SUSPEND, *RESUME, *FRCWRT– QYASPCHGAA API – Change ASP Activity
Main Storage
Pinned
pages
will
remain
“ibm i Quiesce”
Performing a FlashCopy
http://publib.boulder.ibm.com/infocenter/systems/scope/i5os/index.jsp?topic=/rzaig/rzaigmanageiasp.htm
ASP-1
IASP
IASP copy
ready for
backup use
© 2012 IBM Corporation
IBM Power Systems
80
Encryption for IASP (6.1)
� Protects data transmission to and from the disk drive (important in a SAN environment)
� Protects data transmission in the cross site mirroring environment (only when the data being mirrored is on an encrypted independent disk pool)
� Protects data in the case of theft of the disk drive � Protects data in the case of return or resale of a disk drive (reduces the
need to sanitize the disk drive)
� For best performance, put data to be encrypted into a secondary IASP
� In 6.1, must be specified at IASP creation time – cannot be applied to existing IASPs
� In 7.1, added capability to start and stop encryption on an existing IASP
5761-SS1 Option 45 - Encrypted ASP Enablement required
41
© 2012 IBM Corporation
IBM Power Systems
81
Typical IASP Migration Project Outline
� Proof-of-concept on subset of applications� Education on IASP enablement considerations� Set up test environment where IASP enablement changes
will be performed and tested� Perform and test all process, application and work
management changes for IASPs� Integrate most changes into non-IASP production system� Determine production migration strategy based on available
hardware and replication options� Test migration process on sandbox environment, if possible� Perform any necessary education to support personnel and
users on process change, etc.� Execute production migration
© 2012 IBM Corporation
IBM Power Systems
82
Customer’s Using IASPs
� Many, many successful IASP implementations world-wide– Most for HA solutions
– Most have single ASP group per system / partition
� Wide variety of industries and sizes– Major financial institutions world wide
– Various international government holdings
– Telecommunications corporations world wide
– Major transportation and shipping companies
– Infrastructure and facilities providers
– ……. <insert your industry segment here> ……
� More customers are doing this EVERY DAY
� IASP enablement can take a few days or a few months – depends on architecture of applications, configuration options, testing, documentation, etc..
42
© 2012 IBM Corporation
IBM Power Systems
83
Additional Resources� PowerHA Wiki
– www.ibm.com/developerworks/ibmi/ha/
� Lab Services – http://www-03.ibm.com/systems/services/labservices
� Redbooks at www.redbooks.ibm.com– Implementing PowerHA for IBM i - SG24-7405-00 (Nov 2008)– IBM I 6.1 Independent ASPs - SG24-7811-00– PowerHA SystemMirror for IBM i Cookbook – SG24-7994-00 NEW!
� IBM System Storage Solutions for IBM i– Course code: AS930– Duration: 4.0 days– www-
304.ibm.com/jct03001c/services/learning/ites.wss/us/en?pageType=course_description&courseCode=AS930
� High Availability Clusters (Power HA) and Independent Disk Pools for IBM i– Course code: AS541– Duration: 4.0 days– www-
304.ibm.com/jct03001c/services/learning/ites.wss/us/en?pageType=course_description&courseCode=AS541
© 2012 IBM Corporation
IBM Power Systems
84
High availability solutions for UNIX, and i clients
Resiliency Without Downtime -- PowerHA
Thank you!
www.ibm.com/systems/power/software/availability
43
© 2012 IBM Corporation
IBM Power Systems
85
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 client's 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 IBM's 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, 2006
Special notices
© 2012 IBM Corporation
IBM Power Systems
86
IBM, the IBM logo, ibm.com AIX, AIX (logo), AIX 5L, AIX 6 (logo), AS/400, BladeCenter, Blue Gene, ClusterProven, DB2, ESCON, i5/OS, i5/OS (logo), IBM Business Partner (logo), IntelliStation, LoadLeveler, Lotus, Lotus Notes, Notes, Operating System/400, OS/400, PartnerLink, PartnerWorld, PowerPC, pSeries, Rational, RISC System/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 trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked 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 at the 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: http://www.ibm.com/legal/copytrade.shtml.
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other 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 registered trademarks 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 are trademarks of the Standard Performance Evaluation Corp (SPEC).
The Power Architecture and Power.org wordmarks and the Power and Power.org logos and related marks are trademarks and service marks licensed by Power.org.
TPC-C 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
Special notices (cont.)