© 2010 IBM Corporation
SAP application availability- High Availability & Disaster Recovery
Last update: 2010-09-09 by MK
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
2 SAP application availability concepts
Aspects of Availability
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
3 SAP application availability concepts
HA & DR Differences
High Availablity
� Restart < 15 minutes
� Automated Takeover
� Covers failures :
� at local site
� protects against physical errors
� Server
� Disks
� Adapter
� Network
� protects against fatal SW errors
� Operating systems
� Databases
� Applications
� Services
Disaster Recovery
� Restart ~ 4 Hours
� Manual procedures involved
� Protects against
� loss of primary site
� Covers failure of:
� HA solution
� primary site (Infrastructure)
� logical errors
� fatal user error
� loss of complete Infrastructure Blocks
� Caused by
� disaster of nature
� Heavy impact on primary site
� Disaster Recovery Plan required
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
4 SAP application availability concepts
Hardware Failures Account for a Small Minority of System Outages
• Several studies place the proportion between 20% and 45%
• Human error, software error and planned maintenance cause the majority of service outages
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
5 SAP application availability concepts
The high availability scale
36 days1 Offline backup per week
16h 48 min90%
87,5
hours
Offline software
maintenance1h 40 min 99%
One offline backup per
year
8 hours
45 min1 Weekly restart10 min99,9%
One offline software maintenance per year
52 minDaily fast switchover1 min99,99%
1 yearly restart (?)5 minWeekly fast
switchover 6 sec99,999%
??30 sec??0,6 sec99,9999%
Yearly downtime usable
for …. Downtime
per year
Weekly downtime
usable for
(examples)
Downtime
per week Availability
Infrastructure „Five 9s“ industry approach
Today‘s best breed Eco-system approaches
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
6 SAP application availability concepts
Classification via RTO and RPO
Recovery Time Objective
1 Min. 30 min. 1-2 Hr.. 4-8 Hr.. 12-16 Hr.. 24 Hr.. Days
Co
st
Tier 4 – stand by
Tier 3 – pre-configured
Tier 2 – base OS installed
Tier 7 – Sysplex (GDPS)
Tier 6 – cluster
Tier 5 – system automation
Tier 1 – empty
system
Recovery from a disk image Recovery from tape copy
Re
co
ve
ry P
oin
t O
bje
cti
ve
RTO: The time it takes to have systems/applications running again after a failure
RPO: The time delta between transaction data and restored data after failure
1 s
1-5 m
4-8 h
24 h
days…
1-2 h
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
02/12/10
Classical SAP SPOFs
Global File Services
/sapmnt
/usr/sap/trans
Database Server
Message/Enqueue Server
Critical NetWeaver infrastructure components
All SPOFs above
Portal Server (NW EP)
Services Bus (NW PI)
…further dedicated servers
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
8 SAP application availability concepts
A typical resilient SAP infrastructure
CI
repl.
enqueue
Replicated enqueue cluster.
DB
Cluster or
standby DB
DB reconnect
DB
RDBMS
CIMessage
Server
Enqueue
Server
Web
Disp.
Transparent
load
balancing
Web
Disp.
(DMZ)
Appl.
Server
Appl.
Server
HA clusters
ABAP J2EE
ABAP J2EE
ABAP J2EE
RDBMS
RDBMS
RDBMSPortal /
PI
D/R
SCS SCS‘
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
9 SAP application availability concepts
Process oriented view on SAP application availability
PlatformProcess Components
PlatformProcess Components
Enterprise Services
Repository
SAP NetWeaver
Business Process Platform
99,5%
CRM99,5%
CRM99,5%
SRM99,5%
SRM99,5%
ERP99,5%
ERP99,5%
En
terp
ris
e P
ort
al
99
,5%
En
terp
ris
e P
ort
al
99
,5%
BusinessData
BusinessDataBusiness
Data
PersistencyLayer
PersistencyLayer
SAP Composite ApplicationsEnd-useruptime =97,5%
A business process is represented by Composite Applications which consist of multiple services (SOA approach)
Services are provided by SAP backend systems and transported by NetWeaver middleware (PI, EP)
The overall availability of a Composite Application is the product of the availabilities of all involved components
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
10 SAP application availability concepts
SAP HA Strategy
SAP‘s HA scope:
business applications
technology components
SW Life-Cycle Management
Infrastructure components (network –server – storage – DB)
partner products with their HA features
Unplanned downtime
eliminate SPOFs
Planned downtime
to be decreased with smart software logistics and rolling maintenance proceduresNetwork
Storage
Server
OS
Database
Pa
rtn
er
So
luti
on
s
NetWeaver
Business Applications
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
11 SAP application availability concepts
SAP application features to minimize downtime
Logon groups decouple physical servers from User front-end
DB reconnect of App-Servers
Virtualization of hostnames
Replicated Enqueue for faster SCS take-over
Transaction & Data integrity on application side
Rolling kernel upgrade
for SCS maintenance
Enhancement Packages Policy
New Business Logics and Patches
Switch Framework allows for selection
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
12
Hardware Availability : IBM system x & BladeCenter
� Chipkill & Memory ProteXion Technology
� Redundant network
� Redundant fibre channel
� RAID for local disk
� Hot-swap & Hot-add in all major subsystems
� BladeCenter
� Redundant Cooling Domains at Chassis Level
� Redundant Connectors / Disks Design at Blade Level
� Redundant Power Modules at Chassis Level
� Redundant blowers
e.g. Power Feeds
Red. HDD
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
13 SAP application availability concepts
New IBM hardware features to minimize downtime
POWER6 and newer generations
– Processor instruction retry incl. alternateprocessor recovery
– Dynamic I/O bit line repair incl. redirect of physical connection to DIMMs
– Hot-Node Add & Repair
– Live Partition Mobility
• Reduce impact of planned outages
• Relocate workloads to enable growth
• Provision new technology with no
disruption to service
• Save energy by moving workloads off
underutilized servers
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
14 SAP application availability concepts
HA & D/R principles
Clustering alternatives: „shared
nothing“ vs. „shared everything“
DBStandby
DB
Replication
Single DB instanceSingle DB instanceSingle DB instanceSingle DB instance Two DB instancesTwo DB instancesTwo DB instancesTwo DB instances
Replication on database level
Replication on storage level
One logical SAP DatabaseOne logical SAP DatabaseOne logical SAP DatabaseOne logical SAP Database
sharedstorage
ClusterNode
ClusterNode
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
15
Tested 3rd party Clustering Solution on System x for SAP
Micorsoft Cluster Services
Failover Cluster as part of Microsoft Windows 2000/2003 Server
Configurations
SAP NetWeaver ‘04 AS ABAP+AS JAVA Configuration on MSCS
Known configuration
One SAP Central Instance & One Database Instance
Many side effects on MSCS status
Mulitple (A)SCS Instances in a Two Node MSCS Cluster (NetWeaver 2004s)
Three and More Node MSCS Configuration
Cluster Solution for
Enqueue Replication Servers
File Service
Database – e.g. MS SQL Server
More Features
Shared Disk & Quorum
Heartbeat
ISICC Whitepaper (2007)
VERITAS Storage Foundation HA
„Out of the box“ Solution
Configurations
� Preconfigured VCS Agents for SAP, DB and Storage
� Up to 32 nodes per cluster
� SAP Multi SID Support
� Local Clustering & Metropolitan Disaster Recovery withMirroring or Replication
� Wide Area Disaster Recovery (with Global Cluster Option)
Cluster Solution for
� R/3 4.6c (Basis 4.6D) and 4.7, NW 04/s
� SAP Replicated Enqueue (ABAP and JAVA)
More Features
� No SPOF Quorum Disk, Majority Node
� Additional VCS Agent required for database in use
� Online Storage Management, no planned downtimes
� Cluster Server Simulator/Test and verify HA configsbefore taking them into production
ISICC Whitepaper (2007)
SteelEye LifeKeeper
provides monitoring and switchovercapability for Linux
Configurations
� NFS mounts (Linux) or file shares
� IP addresses (via virtual IP)
� Logical Volumes, if using LVM (Linux)
Cluster Solution for
� SAP Central Instance and SAP Central Services Instance (ABAP)
� SAP Central Services (JAVA)
� SAP Replicated Enqueue Server (on thebackup system)
� Database (Oracle, DB2, SAPdb/MaxDB)
New Redbook written in ISICC Februray2008
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
16 SAP application availability concepts
Dual Stack SAP WebAS Architecture (Rel. 6.40ff)
Java Schema
ABAP Schema
Database
Add-In Dialog Instance
Java
Server Process
Server ProcessServer
Process
Java
Dispatcher
JavaABAP
ICM
IGS
Gateway
ABAPDispatcher
Work
ProcessWork
ProcessWork
Process
Single Point of failures (SPOF):� Database
� ASCS-Instance including� Enqueue Server for ABAP
� Message Server for ABAP
� SCS-Instance including� Enqueue Server for Java
� Message Server for Java
� Central file share /sapmnt/…
Add-In Central Instance
Java Server
Process
Server ProcessServer
Process
Java Dispatcher
SDM
JavaABAP
ABAPDispatcher
WorkProcessWork
ProcessWork
Process
Gateway
ICM
IGS
SCS
Instance
ENQ Server
(Java)
MSG Server(Java)
ASCS
Instance
ENQ Server
(ABAP)
MSG Server(ABAP)
Note: SDM is not considered to be a
SPOF since it is no runtime critical
component
Global FS
Appl-Svs.
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
17 SAP application availability concepts
First MSCS
Node
MSCS Cluster 1
First MSCS
Node
AddititionalMSCS Node
MSCS Cluster 2
Central Services
Instance
(SCS)
ABAP
Central Services
Instance(ASCS)
Central Services
Instance
(SCS)
ABAP
Central Services
Instance(ASCS)
Additional
MSCS Node
Database Instance
Database Instance
failover failover
Basic NetWeaver 7.0 (MSCS) Cluster Configuration
– Each MSCS Cluster consists of two nodes
– Two MSCS clusters shown
• Advantage: in case of a SCS failure,
only SCS node needs be taken over,
not the whole SAP system (longer!)
– Can also be on a single cluster.
• Introduce failure classes
– Optional Quorum disk helps to avoid
“split-brain” condition in case cluster
interconnect gets lost.
Dialog instance
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
18 SAP application availability concepts
Mulitple (A)SCS Instances in a Two Node MSCS Cluster
– Two node MSCS Cluster
– Multiple (A)SCS instances of different SAP Systems
– Local Enqueue Replication
Servers for every (A)SCS
instance (not mapped in picture)
– Database instances on the
same machines or on a
separate Cluster
Dialog Instance
failover
failover
First MSCS Node MSCSCluster
ASCSinstance
System1 (<SAPSID1>)
failoverSCS
instance
SCS
instance
System2 (<SAPSID2>)
ASCS
instance
System3 (<SAPSID3>)
ASCSinstance
System<N> (<SAPSID<N>)
SCS
instance
Additional MSCS Node
ASCS
instance
System1 (<SAPSID1>)
SCS
instance
SCS
instance
System2 (<SAPSID2>)
ASCS
instance
System3 (<SAPSID3>)
ASCS
instance
System<N> (<SAPSID<N>)
failover
Central Instance
SCS
instance
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
19
SAP High Availabilty - Redbooks, Whitepapers and Proof of Concepts at the ISICC
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
20 SAP application availability concepts
High Availability Products on Power Systems for SAP
No formal certification by SAP, but solution partners are responsible for support and maintenance
Proof-of-Concepts are a prerequisite in order to claim SAP conformity of any cluster product.
Accordingly, these HA solutions are available on IBM Power Systems:
AIX
PowerHA System Mirror
Tivoli System Automation for MP
IBM DB2 HADR
Oracle RAC
Linux
Tivoli System Automation for MP
PowerHA
IBM DB2 HADR
SteelEye LifeKeeper
SLES 10 Heartbeat + DRBD
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
21 SAP application availability concepts
PowerHA SystemMirror for AIX Standard Edition
Cluster management for the data center
Monitors, detects and reacts to events
Establishes a heartbeat between the systems
Enables automatic switch-over
IBM shared storage clustering
Can enable near-continuous application service
Minimize impact of planned & unplanned outages
Ease of use for HA operations
PowerHA SystemMirror for AIX Enterprise Edition
Cluster management for the Enterprise
Multi-site cluster management
Includes the Standard Edition function
PowerHA SystemMirror Editions
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
22 SAP application availability concepts
SAP Solution Package for IBM PowerHA SystemMirror 6.1 + PowerHA 5.5
Motivation
Standardized toolset around the globe
Support for replicated enqueue scenarios
Align implementation to SAP recommendations
Provide SAP specific Best Practices and recommendations
Supported SAP scenarios
ABAP, JAVA and Double Stack w/o ERS and App (optional)
Tested for NW7.0, 7.20, ECC6.0, EP6, PI7.1
2-tier and 3-tier installations
Multi-node clusters
DB2 and Oracle DBs
HA + DR (PowerHA/XD and SystemMirror Enterprise)
Solution
Set of documentation covering Storage, VIOS, AIX and PowerHA for SAP HA installation & configuration
PowerHA configuration
PowerHA start, stop and monitor scripts
Distributed for free to IBMers and BPs via request to ISICC Infoservice
Limitation
manual setup (not automated) of PowerHA accordingly to Documentation
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
23 SAP application availability concepts
Bundle – Overview of Best Practices
� Start/stop/monitor script design
� ERS
� File system layout
� Resource Groups and their Dependencies
� Making SAP Global File systems Highly
Available
� Naming Conventions
� Power Technology Overview
� Tooling and How-To for: LVM Mirror, VIOS configuration, AIX file systems
PowerHA
LVM
PowerHA PowerHA
PowerHA/XD
PPRC
LVM LVM
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
24 SAP application availability concepts
PowerHA Best Practices WIKI established in 2009
Link at ISICC-WIKI http://w3.tap.ibm.com/w3ki2/display/isicc/PowerHA+Best+Practices
Co-Authors and contributors welcome
could be established as central SAP with PowerHA repository
Plan to post content to a public WIKI in late 2010
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
25 SAP application availability concepts
Tivoli System Automation for Multi PlatformsHigh Availability (HA) solution for platforms running Linux and AIX
System Automation guarantees high availability for business applications
Can be used for applications of any type (Databases, WebServer, SAP, …)
Provides fast detection of HW failures and SW failures (“Monitoring”)
Performs automated recovery, like restart in place of failover (“Automation”)
Policy-based HA solution with powerful policy elements
Allows to describe automation behavior on a high abstraction level
Example: Almost no effort to extend a two node scenario to eight nodesNo script programming
Resource
Mgrs
Resource Resource
MgrsMgrsEventEventEvent Coordinated Restart &
FailoverCoordinated Restart & Coordinated Restart &
FailoverFailover
Automation
Mgr
AutomationAutomation
MgrMgr
Restart & Failover
Rules
SAPSAP
PolicyPolicy
DB2DB2
PolicyPolicy
ApacheApache
PolicyPolicyCustomerCustomer
PoliciesPolicies
Pre-Canned Scenarios:
out-of-the-box policies and features provided
by System Automation
Generic Scenario:
customer specified policies
……
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
26 SAP application availability concepts
TSA - Resource Types and Policy Elements
Resources Types
Serial fixed resource (SAP App-Sv.)
Serial floating resource (DB, SCS, ASCS)
Resource Group
Is a collection of resources which are treated as one logical instance
Entity to start, stop, and monitor
Group status is an aggregation of its members‘ status
Members can be Resources and Resource Groups
Equivalency
Pool of optional resources
Relationships
For start/stop sequence: StartAfter, StopAfter
For dependent resources: DependsOn, DependsOnAny, and ForcedDownBy
For placement constraints: Collocated, AntiCollocated, Affinity, AntiAffinity, IsStartable
Node 1
MountPoint
MountPoint
ServiceIP
DB2
Floating Resource: Mount Point
DB2
ServiceIP
Floating Resource: DB2
Floating Resource: ServiceIP
Resource Group:RG_DB2
DependsOn
DependsOn
NIC
NIC
NIC
NIC
Equivalency: Network
Dep
endsO
n
Node 2
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
27 SAP application availability concepts
Shared (CPU) resources support cluster mechanisms
Prod 1
DB-Sv
QA
Test
Prod 2
App-Sv
Dev
IDES
HA-Cluster
Node-1 Node-2
Data
CUOD
CPUsCUOD
CPUs
Prod 1
DB-Sv
QA
Test
Prod 2
DB- &
App-Sv
Dev
IDES
Node-1 Node-2
Data
CUOD
CPUsCUOD
CPUs
System
Failure
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
28 SAP application availability concepts
Database Take Over - "Cold" Failover
DB-Server DB-B'up
OS
Application
Cluster-Mgr
Database -SW
OS
Cluster-Mgr
�Cold failover is slower since :
–'graceful' shutdown of app's on backup
server
–moving and mounting logical volumes
–starting the DB instance on backup
server
–opening the data files
–rebuilding buffers
�After failover, application servers must re connect to the database
�After failover, the instance caches are cold
introducing a performance brownout
DB-Backup
Failover
Heartbeat
Physically Shared disks
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
29 SAP application availability concepts
Database Take Over - "Hot" Failover
�Hot failover is faster since :
–updated buffers on take-over instance
–take-over system in permanent forward
recovery mode
–no transactions to be applied from redo
logs
FailoverDB-Node 1 DB-Node 2
OS
Cluster-SW
Oracle Packs
SAN Topology
FailoverDatabase
OS
Oracle Packs
Database
Global FS Global FS
Appl-ServerAppl-Server
Appl-Server
Quorum Node
Quorum Disk
OS
low scale /
low cost
Cluster-SW
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
30 SAP application availability concepts
Global FS
Oracle RAC principles
High Availability plus scalability option for Oracle DB
Active/active architecture provides
transparent client failover capability w/ little or no user downtime
increased SAP throughput capacity per additional node
Queries continue uninterrupted (TAF)
SCS HA by SAPCTL-Utility for AIX and Linux
NodeNode
AA
NodeNode
BB
NodeNode
AA
NodeNode
BB
Node A in an RAC cluster fails, users are
migrated
SAP GUI, Portal
private networks
Enterprise LANs
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
31 SAP application availability concepts
Basic DR concept: Shadow DB resp. Log Shipping
Production HA system
cluster
Shadow DB system
� Alternative for long distance
mirroring of large DBs� Reduced WAN-bandwidth
necessary
� Can recover logical DB
errors.
� Logical DR:
�Shadow DB can run on
local or remote site
�No dedicated storage
system is required
� Physical DR
� If shadow DB runs on
remote side it can
protect against physical
and logical errors
LOG shipping, e.g.:DB2 HADR, Ora Dataguard, Libelle…
LOG shipping, e.g.:DB2 HADR, Ora Dataguard, Libelle…
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
32 SAP application availability concepts
DB2 HADR (High Availability Disaster Recovery)
Two active machines
Primary
Processes transactions
Ships log entries (not logfiles)
to the other machine
Standby
Cloned from the primary
Receives and stores log
entries from the primary
Re-applies the transactions
If the primary fails, the standby can take over the transactional workload. Standby becomes the new primary
If the failed machine becomes available again, it can be automatically resynchronized.The old primary becomes the new standby
Operation modes:
Asynchronous
Near-synchronous
Synchronous
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
33 SAP application availability concepts
ERS
system2 (standby)
MS
IP_P
system1 (primary)
ES replicate IP_S
PowerHA / TSA PowerHA / TSA
Application Server instances
Improved Central Services Availability by Replicated Enqueue Server - Basic Architecture
� Started shipping with NetWeaver 7.0 release
�backward compatible to 4.6D kernel
� faster SCS/ASCS take over for large installations
� combined with standard HA packages
� Also supports SAP rolling kernel upgrade procedure
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
34 SAP application availability concepts
VMware Fault Tolerance for SAP Solutions
Single identical VMs running in
lockstep on separate hosts
Zero downtime, zero data loss failover for all virtual machines
in case of hardware failures
Zero downtime, zero data loss
No complex clustering or specialized hardware required
Single common mechanism for
all applications and OS-es
Currently only 1vCPU. Good
for CI services.
VMware vSphere™
OS
SAP
OS
SAP
OS
SAP
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
35 SAP application availability concepts
SAPGUI
Application Servers
Database Server
IBM High Availability solutions cover whole SAP landscape
Network /
Backbone
R/3 Data
Functional Backends
�parallel DBs
�liveCache
�etc.
� Enterprise Portal
� PI
�ITS/IGS
Transient Functions
ABAP-Engine
�Message Server
�Enqueue Server
JAVA-Engine
�Message Server
�Enqueue Server
Replicated
Enqueue Server
hot-StandbyliveCache
DB2 HADR
DB2 PureScale
Oracle RAC
PowerHA WIKI
TSA policies
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
36 SAP application availability concepts
Time for Questions …
Mail contact: [email protected]
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
37 SAP application availability concepts
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.
Many of the features described in this document are operating system dependent and may not be available on Linux. For more information, please check: http://www.ibm.com/systems/p/software/whitepapers/linux_overview.html
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 January 19, 2006
Special Notices
© 2010 IBM Corporation
IBM SAP Business Partner Accreditation
38 SAP application availability concepts
Revised June 15, 2006
Special Notices (Cont.)
The following terms are registered trademarks of International Business Machines Corporation in the United States and/or other countries: AIX, AIX/L, AIX/L(logo),
alphaWorks, AS/400, BladeCenter, Blue Gene, Blue Lightning, C Set++, CICS, CICS/6000, ClusterProven, CT/2, DataHub, DataJoiner, DB2, DEEP BLUE,
developerWorks, DirectTalk, Domino, DYNIX, DYNIX/ptx, e business(logo), e(logo)business, e(logo)server, Enterprise Storage Server, ESCON, FlashCopy, GDDM,
i5/OS, IBM, IBM(logo), ibm.com, IBM Business Partner (logo), Informix, IntelliStation, IQ-Link, LANStreamer, LoadLeveler, Lotus, Lotus Notes, Lotusphere, Magstar,
MediaStreamer, Micro Channel, MQSeries, Net.Data, Netfinity, NetView, Network Station, Notes, NUMA-Q, Operating System/2, Operating System/400, OS/2,
OS/390, OS/400, Parallel Sysplex, PartnerLink, PartnerWorld, Passport Advantage, POWERparallel, Power PC 603, Power PC 604, PowerPC, PowerPC(logo),
Predictive Failure Analysis, pSeries, PTX, ptx/ADMIN, RETAIN, RISC System/6000, RS/6000, RT Personal Computer, S/390, Scalable POWERparallel Systems,
SecureWay, Sequent, ServerProven, SpaceBall, System/390, The Engines of e-business, THINK, Tivoli, Tivoli(logo), Tivoli Management Environment, Tivoli
Ready(logo), TME, TotalStorage, TURBOWAYS, VisualAge, WebSphere, xSeries, z/OS, zSeries.
The following terms are trademarks of International Business Machines Corporation in the United States and/or other countries: Advanced Micro-Partitioning, AIX 5L,
AIX PVMe, AS/400e, Chipkill, Chiphopper, Cloudscape, DB2 OLAP Server, DB2 Universal Database, DFDSM, DFSORT, DS4000, DS6000, DS8000, e-
business(logo), e-business on demand, eServer, Express Middleware, Express Portfolio, Express Servers, Express Servers and Storage, GigaProcessor, HACMP,
HACMP/6000, IBM TotalStorage Proven, IBMLink, IMS, Intelligent Miner, iSeries, Micro-Partitioning, NUMACenter, On Demand Business logo, OpenPower,
POWER, Power Architecture, Power Everywhere, Power Family, Power PC, PowerPC Architecture, PowerPC 603, PowerPC 603e, PowerPC 604, PowerPC 750,
POWER2, POWER2 Architecture, POWER3, POWER4, POWER4+, POWER5, POWER5+, POWER6, POWER6+, Redbooks, Sequent (logo), SequentLINK, Server
Advantage, ServeRAID, Service Director, SmoothStart, SP, System i, System i5, System p, System p5, System Storage, System z, System z9, S/390 Parallel
Enterprise Server, Tivoli Enterprise, TME 10, TotalStorage Proven, Ultramedia, VideoCharger, Virtualization Engine, Visualization Data Explorer, X-Architecture,
z/Architecture, z/9.
A full list of U.S. trademarks owned by IBM may be found at: http://www.ibm.com/legal/copytrade.shtml.
A full list of trademarks owned by SAP may be found at: http://www.sap.com/company/legal/copyright/trademark.epx
UNIX is a registered trademark in the United States, other countries or both.
Linux is a registered trademark of Linus Torvalds in the United States, other countries or both.
Microsoft, Windows, Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries or both.
Intel, Intel Xeon, Itanium and Pentium are trademarks or registered trademarks of Intel Corporation in the United States and/or other countries.
AMD Opteron is a trademark of Advanced Micro Devices, Inc.
Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States and/or other countries.
TPC-C and TPC-H are trademarks of the Transaction Performance Processing Council (TPPC).
SPECint, SPECfp, SPECjbb, SPECweb, SPECjAppServer, SPEC OMP, SPECviewperf, SPECapc, SPEChpc, SPECjvm, SPECmail, SPECimap and SPECsfs are
trademarks of the Standard Performance Evaluation Corp (SPEC).
NetBench is a registered trademark of Ziff Davis Media in the United States, other countries or both.
AltiVec is a trademark of Freescale Semiconductor, Inc.
Other company, product and service names may be trademarks or service marks of others.