02 - SAP Availability Concepts

SAP application availability
- High Availability & Disaster Recovery
Last update: 2010-09-09 by MK
© 2010 IBM Corporation

IBM SAP Business Partner Accreditation
Aspects of Availability
2 SAP application availability concepts © 2010 IBM Corporation

HA & DR Differences
High Availablity Disaster Recovery
Restart < 15 minutes Restart ~ 4 Hours
Automated Takeover Manual procedures involved
Covers failures : Protects against
at local site loss of primary site
protects against physical Covers failure of:
errors
HA solution
Server
primary site (Infrastructure)
Disks
logical errors
Adapter
fatal user error
Network
loss of complete Infrastructure
protects against fatal SW Blocks
errors
Caused by
Operating systems
disaster of nature
Databases
Heavy impact on primary site
Applications
Services
Disaster Recovery Plan required

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

The high availability scale
Weekly downtime
Downtime Downtime Yearly downtime usable
Availability usable for
per week per year for ….
(examples)
99,9999% 0,6 sec ?? 30 sec ??
Weekly fast
99,999% 6 sec Infrastructure
switchover „Five 9s“5 min
industry1 yearly
approach
restart (?)
One offline software

99,99% Today‘sDaily
1 min best fastbreed Eco-system
switchover 52 min approaches
maintenance per year
8 hours One offline backup per

99,9% 10 min 1 Weekly restart
45 min year
Offline software 87,5

99% 1h 40 min
maintenance hours
1 Offline backup per
90% 16h 48 min 36 days
week

Classification via RTO and RPO
Recovery from a disk image Recovery from tape copy

Recovery Point Objective
1s Tier 7 – Sysplex (GDPS)
1-5 m Tier 6 – cluster

Cost
1-2 h Tier 5 – system automation
4-8 h Tier 4 – stand by
24 h Tier 3 – pre-configured
days…
Tier 2 – base OS installed
Tier 1 – empty
1 Min. 30 min. 1-2 Hr.. 4-8 Hr.. 12-16 Hr.. 24 Hr.. Days
system
Recovery Time Objective
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
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
02/12/10 © 2010 IBM Corporation

A typical resilient SAP infrastructure
(DMZ)
SCS
CI SCS‘
CI Replicated
Message
Server enqueue cluster.
repl.
Enqueue
enqueue
Server
Web
Disp. HA
Appl.
Server
clusters
DB
Web ABAP J2EE
Disp. Cluster or
standby DB
RDBMS
Appl. DB reconnect
Server RDBMS
DB
Transparent ABAP J2EE

load
balancing
Portal / RDBMS
PI RDBMS
ABAP J2EE
D/R
Process oriented view on SAP application availability
End-user
SAP Composite Applications
uptime =
97,5%
Enterprise SAP NetWeaver
Portal
Enterprise Portal
Services Business Process Platform
Repository
99,5%
99,5%
99,5%
Enterprise
CRM
CRM SRM
SRM ERP
ERP Platform
Platform
99,5%
99,5% 99,5%
99,5% 99,5%
99,5% Process
Process Components
Components
Persistency
Business Business Persistency Layer
Data Business Data Layer
Data
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

SAP HA Strategy
SAP‘s HA scope:
Business business applications
Applications technology components
SW Life-Cycle Management
NetWeaver
Partner Solutions
Database Infrastructure components (network –
server – storage – DB)
OS partner products with their HA features
Unplanned downtime
Server eliminate SPOFs
Planned downtime
Storage
to be decreased with smart software
logistics and rolling maintenance
Network procedures

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

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
Red. HDD
Redundant Connectors / Disks Design at Blade Level
e.g. Power Feeds
Redundant Power Modules at Chassis Level
Redundant blowers
12 © 2010 IBM Corporation

New IBM hardware features to minimize downtime
POWER6 and newer generations

– Processor instruction retry incl. alternate
processor 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

HA & D/R principles
One logical SAP Database

Single DB instance Two DB instances
Cluster Cluster
Node Node
shared Replication Standby

DB
storage DB
Clustering alternatives: „shared Replication on database level

nothing“ vs. „shared everything“ Replication on storage level

Tested 3rd party Clustering Solution on System x for SAP
Micorsoft Cluster Services VERITAS Storage Foundation HA SteelEye LifeKeeper

Failover Cluster as part of Microsoft Windows 2000/2003 Server
Configurations
„Out of the box“ Solution provides monitoring and switchover
SAP NetWeaver ‘04 AS ABAP+AS JAVA Configuration on MSCS Configurations capability for Linux
Known configuration
Preconfigured VCS Agents for SAP, DB and Storage Configurations
One SAP Central Instance & One Database Instance
Up to 32 nodes per cluster NFS mounts (Linux) or file shares
Many side effects on MSCS status
SAP Multi SID Support IP addresses (via virtual IP)

Mulitple (A)SCS Instances in a Two Node MSCS Cluster (NetWeaver
2004s)
Local Clustering & Metropolitan Disaster Recovery with Logical Volumes, if using LVM (Linux)
Three and More Node MSCS Configuration Mirroring or Replication
Cluster Solution for Cluster Solution for
Wide Area Disaster Recovery (with Global Cluster
Enqueue Replication Servers Option) SAP Central Instance and SAP Central
File Service Services Instance (ABAP)
Cluster Solution for
Database – e.g. MS SQL Server
More Features R/3 4.6c (Basis 4.6D) and 4.7, NW 04/s SAP Central Services (JAVA)
Shared Disk & Quorum
SAP Replicated Enqueue (ABAP and JAVA) SAP Replicated Enqueue Server (on the
Heartbeat backup system)
ISICC Whitepaper (2007) More Features
Database (Oracle, DB2, SAPdb/MaxDB)
No SPOF Quorum Disk, Majority Node
New Redbook written in ISICC Februray
Additional VCS Agent required for database in use 2008
Online Storage Management, no planned downtimes
Cluster Server Simulator/Test and verify HA configs
before taking them into production
ISICC Whitepaper (2007)

Dual Stack SAP WebAS Architecture (Rel. 6.40ff)
Add-In Central Instance SCS

ICM Instance Add-In Dialog Instance
ENQ Server ICM
ABAP Java (Java)
Dispatcher Dispatcher
ABAP Java
MSG Server
Work Dispatcher Dispatcher
Work Java
Server (Java)
Work
Process Server
Server
Process Process
Process Work Java
Process Process Work Server
Work
Process Server
Server
Process Process
ASCS Process Process
Process
Gateway SDM Instance
Gateway
ENQ Server
ABAP Java (ABAP) ABAP Java
IGS MSG Server IGS

(ABAP) vs.
p l-S
Ap
Single Point of failures (SPOF):
Global FS Database Database
ASCS-Instance including
Enqueue Server for ABAP ABAP Schema
Message Server for ABAP
Note: SDM is not considered to be a SCS-Instance including Java Schema
SPOF since it is no runtime critical Enqueue Server for Java
component Message Server for Java
Central file share /sapmnt/…

Basic NetWeaver 7.0 (MSCS) Cluster Configuration
MSCS Cluster 1 MSCS Cluster 2

– Each MSCS Cluster consists of two
First MSCS Additional
First MSCS Addititional nodes
Node MSCS Node MSCS Node
Node
– Two MSCS clusters shown
• Advantage: in case of a SCS failure,
Central Central only SCS node needs be taken over,
Services Services
Instance Instance
not the whole SAP system (longer!)
(SCS) (SCS)
Database
failover
Database failover – Can also be on a single cluster.
Instance Instance
ABAP ABAP • Introduce failure classes
Central Central
Services Services
Instance Instance
(ASCS) (ASCS) – Optional Quorum disk helps to avoid
“split-brain” condition in case cluster
interconnect gets lost.
Dialog instance

Mulitple (A)SCS Instances in a Two Node MSCS Cluster
First MSCS Node MSCS Additional MSCS Node

Cluster
System1 (<SAPSID1>) System1 (<SAPSID1>)
SCS ASCS SCS
ASCS
instance instance failover instance instance
– Two node MSCS Cluster
– Multiple (A)SCS instances of
different SAP Systems
SCS failover SCS
instance instance – Local Enqueue Replication
Servers for every (A)SCS
instance (not mapped in
ASCS failover ASCS
instance instance picture)
– Database instances on the
System<N> (<SAPSID<N>) System<N> (<SAPSID<N>) same machines or on a
ASCS SCS ASCS SCS separate Cluster
instance instance failover instance instance
Central Instance Dialog Instance

SAP High Availabilty - Redbooks, Whitepapers and Proof of Concepts at the ISICC

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

PowerHA SystemMirror Editions

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

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

Bundle – Overview of Best Practices

PowerHA
Start/stop/monitor script design

LVM
ERS
File system layout PowerHA/XD
Resource Groups and their Dependencies PowerHA PowerHA
Making SAP Global File systems Highly

Available
LVM LVM
Naming Conventions
Power Technology Overview
Tooling and How-To for: PPRC
LVM Mirror, VIOS configuration, AIX file systems

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

Tivoli System Automation for Multi Platforms

High 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 nodes
No script programming
Event Automation Resource Coordinated Restart &

Mgr Mgrs Failover
Restart & Failover

Rules
Customer SAP DB2 Apache …

Policies Policy Policy Policy
Generic Scenario:
customer specified policies Pre-Canned Scenarios:
out-of-the-box policies and features provided
by System Automation

TSA - Resource Types and Policy Elements

Resources Types
Serial fixed resource (SAP App-Sv.)
Serial floating resource (DB, SCS, ASCS)
Resource Group Resource Group:RG_DB2

Is a collection of resources which are treated as one logical Service Floating Resource: Service
instance IP ServiceIP IP
Entity to start, stop, and monitor DependsOn
Group status is an aggregation of its members‘ status Floating Resource:
DB2 DB2 DB2
DependsOn
Members can be Resources and Resource Groups
DependsOn
Equivalency Floating Resource:
Mount Mount
Pool of optional resources Point Mount Point Point
Relationships
For start/stop sequence: StartAfter, StopAfter Equivalency: Network
NIC
NIC
NIC
NIC
For dependent resources: DependsOn, DependsOnAny,
and ForcedDownBy Node 1 Node 2
For placement constraints: Collocated, AntiCollocated,

Affinity, AntiAffinity, IsStartable

Shared (CPU) resources support cluster mechanisms
CUOD CUOD CUOD CUOD

CPUs CPUs CPUs CPUs
HA-Cluster System
Prod 1 Prod 1
Prod 2 Prod 2
DB-Sv DB-Sv
App-Sv Failure DB- &
App-Sv
Data Data
QA QA
Dev
Test Test Dev

IDES
IDES
Node-1 Node-2 Node-1 Node-2

Database Take Over - "Cold" Failover
Cold failover is slower since :

Application
Database -SW Failover –'graceful' shutdown of app's on backup
DB-Backup server
Heartbeat
–moving and mounting logical volumes
Cluster-Mgr Cluster-Mgr
–starting the DB instance on backup
server
OS OS –opening the data files
–rebuilding buffers
DB-Server DB-B'up After failover, application servers must re
connect to the database
After failover, the instance caches are cold
Physically Shared disks introducing a performance brownout

Database Take Over - "Hot" Failover

Appl-Server
Appl-Server
Appl-Server
Hot failover is faster since :
Database Failover Database –updated buffers on take-over instance

Failover –take-over system in permanent forward
Oracle Packs Oracle Packs
recovery mode
Global FS Global FS –no transactions to be applied from redo
logs
Cluster-SW Cluster-SW
OS OS
DB-Node 1 DB-Node 2
SAN Topology
OS
Quorum Disk
low scale /
Quorum Node low cost

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
SAP GUI, Portal
Enterprise
LANs
private Node A in an RAC

networks Node Node cluster fails, users are Node Node
A B migrated A B
Global FS

Basic DR concept: Shadow DB resp. Log Shipping
Alternative for long distance

mirroring of large DBs
cluster Reduced WAN-bandwidth
necessary
LOG
LOG shipping,
shipping, e.g.:
e.g.:
DB2 Can recover logical DB
DB2 HADR, Ora Dataguard, Libelle…
HADR, Ora Dataguard, Libelle…
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
Production HA system Shadow DB system

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

Improved Central Services Availability by Replicated

Enqueue Server - Basic Architecture
system1 (primary) system2 (standby)
PowerHA / TSA PowerHA / TSA
replicate IP_S
MS ES ERS
IP_P
Started shipping with NetWeaver 7.0 release

Application Server instances 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

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
SAP SAP SAP
OS OS OS No complex clustering or
specialized hardware required
VMware vSphere™
Single common mechanism for
all applications and OS-es
Currently only 1vCPU. Good
for CI services.

IBM High Availability solutions cover whole SAP landscape

DB2 HADR Application Servers
ABAP-Engine JAVA-Engine
DB2 PureScale
Message Server Message Server
Oracle RAC
Enqueue Server Enqueue Server
SAPGUI
R/3 Data
Replicated
Database Server Enqueue Server
PowerHA WIKI
Network / TSA policies Functional Backends
Backbone
parallel DBs
liveCache
etc. hot-Standby
Transient Functions liveCache
Enterprise Portal
PI
ITS/IGS

Time for Questions …
Mail contact: isicc@de.ibm.com

Special Notices
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 (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.
Revised June 15, 2006

02 - SAP Availability Concepts

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

02 - SAP Availability Concepts

Enviado por

Direitos autorais:

Formatos disponíveis

SAP application availability

- High Availability & Disaster Recovery

Last update: 2010-09-09 by MK

© 2010 IBM Corporation

2 SAP application availability concepts © 2010 IBM Corporation

3 SAP application availability concepts © 2010 IBM Corporation

Hardware Failures Account for a Small Minority of System Outages

• Several studies place the proportion between 20% and 45%

4 SAP application availability concepts © 2010 IBM Corporation

The high availability scale

99,9999% 0,6 sec ?? 30 sec ??

One offline software

8 hours One offline backup per

Offline software 87,5

5 SAP application availability concepts © 2010 IBM Corporation

Classification via RTO and RPO

Recovery from a disk image Recovery from tape copy

1s Tier 7 – Sysplex (GDPS)

1-5 m Tier 6 – cluster

1-2 h Tier 5 – system automation

4-8 h Tier 4 – stand by

Recovery Time Objective

Classical SAP SPOFs

Global File Services

Critical NetWeaver infrastructure components

02/12/10 © 2010 IBM Corporation

A typical resilient SAP infrastructure

Transparent ABAP J2EE

Process oriented view on SAP application availability

Enterprise SAP NetWeaver

9 SAP application availability concepts © 2010 IBM Corporation

10 SAP application availability concepts © 2010 IBM Corporation

SAP application features to minimize downtime

Logon groups decouple physical servers from User front-end

Transaction & Data integrity on application side

11 SAP application availability concepts © 2010 IBM Corporation

Hardware Availability : IBM system x & BladeCenter

Chipkill & Memory ProteXion Technology

12 © 2010 IBM Corporation

New IBM hardware features to minimize downtime

POWER6 and newer generations

13 SAP application availability concepts © 2010 IBM Corporation

HA & D/R principles

One logical SAP Database

shared Replication Standby

Clustering alternatives: „shared Replication on database level

14 SAP application availability concepts © 2010 IBM Corporation

Tested 3rd party Clustering Solution on System x for SAP

Micorsoft Cluster Services VERITAS Storage Foundation HA SteelEye LifeKeeper

SAP Multi SID Support IP addresses (via virtual IP)

15 © 2010 IBM Corporation

Dual Stack SAP WebAS Architecture (Rel. 6.40ff)

Add-In Central Instance SCS

IGS MSG Server IGS

16 SAP application availability concepts © 2010 IBM Corporation

Basic NetWeaver 7.0 (MSCS) Cluster Configuration

MSCS Cluster 1 MSCS Cluster 2

17 SAP application availability concepts © 2010 IBM Corporation

Mulitple (A)SCS Instances in a Two Node MSCS Cluster

First MSCS Node MSCS Additional MSCS Node

Central Instance Dialog Instance

18 SAP application availability concepts © 2010 IBM Corporation

19 © 2010 IBM Corporation

Cold failover is slower since :