Tips for Minimizing Downtime During

Your Upgrade

Lon Blake
SAP Americas

Enterprise Services / Enterprise SOA

Enhancement Packages

SAP ERP SRM SCM CRM PLM

6.0
Business Suite

NetWeaver

Business Process Platform (BPP)

 Legal Disclaimer

This presentation is not subject to your license

agreement or any other agreement with SAP.
SAP has no obligation to pursue any course of
business outlined in this presentation or to
develop or release any functionality mentioned in
this presentation. This presentation and SAP’s
strategy and possible future developments are
subject to change and may be changed by SAP at
any time for any reason without notice. This
document is provided without a warranty of any
kind, either express or implied, including but not
limited to, the implied warranties of
merchantability, fitness for a particular purpose, or
non-infringement. SAP assumes no responsibility
for errors or omissions in this document, except if
such damages were caused by SAP intentionally
or grossly negligent.

© SAP 2009 / 2
 Agenda

1. Downtime
1.1 Definition of Downtime
1.2 What are the elements of Production Downtime during an Upgrade?
1.3 Influencing Factors for Runtime & Downtime
1.4 Some Facts & Figures about Downtime
1.5 Costs vs. Downtime
1.6 Downtime Strategies
2. Improvements by SAP
3. Upgrade Tuning
3.1 Tuning within SAP Standard
3.2 Details on Incremental Conversion (ICNV)
3.3 Customer-Based Upgrade (CBU)
3.4 Incremental Upgrade & Unicode Conversion (IUUC)
4. Summary
© SAP 2009 / 3
 What Does Downtime Mean?

Production Uptime: End users can use the

system’s applications in
Operation
production

SAP system is not available

for end users Downtime

© SAP 2009 / 4
 Causes of Downtime

Unplanned Downtime Planned Downtime

System and infrastructure
HW, OS failures,
disasters maintenance
20% Application
failures Patches, upgrades, transports
40%
Operator ...
errors
40%
Source: Gartner Group

Hardware, OS, environment failures, disaster To be avoided with scalable

impact to be avoided by eliminating Single components which enable rolling
Points of Failure (SPOF) maintenance
Improved Upgrade and Patch
“Human errors” (= 80% of downtime causes)
Processes
to be addressed by ease of system
management and with improved change and Proven Software Life Cycle
problem management processes Management and Propagation
Engines (TMS, CMS)
Not solvable by automatic switchover!!

© SAP 2009 / 5
 Various Reasons for (Planned) Downtimes

New SAP version may require:

New database version
SAP
New operating system version
DB
Usually the start release of
SAP software runs on: OS
Target release DB
Target release OS
Destination
Release
Start Release
Configuration
Configuration

SAP
DB
OS

SYSTEM DOWNTIME
Recommendation: Split into different maintenance slots!
© SAP 2009 / 6
 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 5 min 1 yearly restart (?)
switchover

One offline software

99.99% 1 min Daily fast switchover 52 min
maintenance per year
ACHIEVABLE
ACHIEVABLE TODAY
TODAY
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

© SAP 2009 / 7
 Content and Goals

Availability Cost Curve

(Source: Gartner Group)
costs

Cost
Costs

95% 98% 99.5% 99.9%

downtime
Availability

Downtime costs not linear over the Redundant components

downtime Disaster recovery site
For longer downtimes, costs can System management tools
increase progressively
IT staff
Example: When SCM processes are
stuck longer than 3 hours, the whole Capacity planning
production will be stuck and cause Guaranteed SLA
even higher costs
Proactive services
© SAP 2009 / 8
 Agenda

1. Downtime
1.1 Definition of Downtime
1.2 What are the elements of Production Downtime during an Upgrade?
1.3 Influencing Factors for Runtime & Downtime
1.4 Some Facts & Figures about Downtime
1.5 Costs vs. Downtime
1.6 Downtime Strategies
2. Improvements by SAP
3. Upgrade Tuning
3.1 Tuning within SAP Standard
3.2 Details on Incremental Conversion (ICNV)
3.3 Customer-Based Upgrade (CBU)
3.4 Incremental Upgrade & Unicode Conversion (IUUC)
4. Summary
© SAP 2009 / 9
 Production Downtime During Upgrade

What are the elements of production downtime?

Upgrade technical runtime (SAPup) – not all of this is production downtime!
Post-upgrade transports & manual adjustments
Business validation & acceptance testing
Possibly pre- and post-upgrade system backups
Business ramp-down & ramp-up
ramp-
up

up up
SAPup: SAPup:
Business
PREPARE conversion, Transports &
validation
& XPRAS, etc. manual tasks
tests
down repository down
import

ramp- go/no-go decision backup?

backup?
down
Functional/
Basis Operations
business

© SAP 2009 / 10
 Potential to Reduce Downtime

ramp-
go/no-go decision up

up 1 2 up
SAPup: SAPup:
PREPARE conversion,
& XPRAS, etc.
repository
down import
down
Transports & backup?
ramp- manual tasks Basis
before down backup?
Business Functional/
validation ramp- business
tests up
Operations

up up
SAPup: SAPup:
PREPARE conversion,
& XPRAS, etc.
repository
down import
down

go/no-go decision
after backup?

© SAP 2009 / 11
Methods to Reduce Downtime During Upgrade

What are the elements of production 11.1. Run

RunSGEN
SGENLoad
LoadGeneration
Generationininparallel
parallelmode
mode
during
duringend
endphases
phasesof
ofthe
theupgrade
upgradeprocess
process
downtime?
Upgrade technical runtime (SAPup) – 22.2. Use
UseASU-Toolbox
ASU-Toolboxand
andUpgrade
UpgradeAccelerator
Acceleratorto
to
not all of this is production downtime! reduce/eliminate
reduce/eliminatetime
timerequired
requiredfor
formanual
manualpre-
pre-&&
Post-upgrade transports & manual post-upgrade
post-upgradeactions
actions
adjustments 33.3. Speed
Speedup
upimport
importtime
timeby
byrepackaging
repackagingaalarge
large
Business validation & acceptance testing number
numberofoftransport
transportrequests
requeststo
toaafew
fewtransports
transports
Pre- and post-upgrade system backups
Business ramp-down & ramp-up 44.4. Test
Testautomation
automationreduces
reducesvalidation
validationtest
testtime
time
business ramp-
validation up
tests
2 1 2 3
up Transports
up
SAPup: & manual
SAPup: conversion, 4
PREPARE XPRAS, etc. tasks
&
down repository down
import

ramp- go/no-go decision backup

backup
down
Functional/
Basis Operations
business

© SAP 2009 / 12
 Agenda

1. Downtime
1.1 Definition of Downtime
1.2 What are the elements of Production Downtime during an Upgrade?
1.3 Influencing Factors for Runtime & Downtime
1.4 Some Facts & Figures about Downtime
1.5 Costs vs. Downtime
1.6 Downtime Strategies
2. Improvements by SAP
3. Upgrade Tuning
3.1 Tuning within SAP Standard
3.2 Details on Incremental Conversion (ICNV)
3.3 Customer-Based Upgrade (CBU)
3.4 Incremental Upgrade & Unicode Conversion (IUUC)
4. Summary
© SAP 2009 / 13
 Influencing Factors for Runtime & Downtime

1 2 3 4
Hardware Software Configuration Strategy

Number and type of

Downtime

CPUs for the App. & Start & Target Upgrade Upgrade Strategy
DB Server Release Parameterization (downtime or
Version of the (e.g., number of resource minimized)
Type & performance
Upgrade Tools processes) Usage of Incremental
of the Storage
(I/O throughput) Number of clients Conversion (ICNV)

Start/Target Release Upgrade

Number and type of Parameterization
Number of included
Runtime

CPUs for the App. &

support packages Number of installed
DB Server Usage of Incremental
Number of mods on languages
Type & performance Conversion (ICNV)
standard SAP objects Import Destination
of the Storage
Upgrade tools Time
version

As each system is highly individual regarding its configuration and application data, a
forecast of runtime and downtime is only possible when analyzing results of a test
upgrade with a representative set of data (copy of Production)!

© SAP 2009 / 14
 Database Size vs. Upgrade Downtime

No direct impact of DB-Size on upgrade runtime/downtime!

Scatter plot Downtime vs. DB-Size

100
90
80
70
Downtime/h

60
50
40
30
20
10
0
0 100 200 300 400 500 600 700 800 900 1000
DB-Size/GB

Source: Analysis of RSUPGSUM reports

© SAP 2009 / 15
 Agenda

1. Downtime
1.1 Definition of Downtime
1.2 What are the elements of Production Downtime during an Upgrade?
1.3 Influencing Factors for Runtime & Downtime
1.4 Some Facts & Figures about Downtime
1.5 Costs vs. Downtime
1.6 Downtime Strategies
2. Improvements by SAP
3. Upgrade Tuning
3.1 Tuning within SAP Standard
3.2 Details on Incremental Conversion (ICNV)
3.3 Customer-Based Upgrade (CBU)
3.4 Incremental Upgrade & Unicode Conversion (IUUC)
4. Summary
© SAP 2009 / 16
 Downtime Statistic: Upgrade to SAP ERP 6.0
(Customer Feedback)

Downtime:
Downtime: Minimum
Minimum possible
possible technical
technical downtime,
downtime, ifif “downtime
“downtime minimized”
minimized” had
had been
been used
used as
as
an
an upgrade
upgrade strategy,
strategy, and
and there
there was
was no
no dialog
dialog time
time during
during procedure
procedure execution.
execution.

1080

# 256
960
14.9
14.9 h
h
840 Rem.; 195
# 778
720 10.2
10.2 h
h
Rem.
DT [min]

XPRA; 256 Rem.; 177

600
XPRA
# 959 TABIM
480
XPRA; 214
7.9
7.9 h
h # 111 PCON

360
TABIM; 135
Rem.; 128 7.2
7.2 h
h
Rem.; 151

240 TABIM; 169 XPRA; 166 XPRA; 114

PCON; 350
120
TABIM; 99 TABIM; 140
PCON; 154
PCON; 57 PCON; 37
0
SR0
1 SR1
2 SR2
3 SR3
3

Activities: Activities: Activities:

Improvements for Oracle Optimize upgrade packages to improve Import can be improved by
(DB patches, opt. for upgrade) parallelization parallel R3trans processes
5 AIM improved Less interruptions & repeats due to errors
© SAP 2009 / 17
 Downtime Minimization by Optimizing XPRA &
AIM Runtime

Current situation: Statistics about 1,355 customer upgrades to SAP ERP 6.0 SR2

4 hours of the total downtime (~44%) belong

to XPRA or AIM

© SAP 2009 / 18
 Downtime Minimization by Optimizing XPRA &
AIM Runtime (cont.)

Current situation: Statistics about 111 customer upgrades to SAP ERP 6.0 SR3

2 hours of the total downtime (~26%) belong

to XPRA or AIM

© SAP 2009 / 19
 Upgrades to SAP ERP 6.0:
Business Downtime by Source Release
Business Downtime:
Business downtime in hours
Total time that the
Source Release SAP R/3

Distribution of values system is not

available for end
Enterprise

users, including the

Range of values technical downtime
Median: 34.0
plus the time
necessary for data
Min: 13.2 Max: 63.0 backup, final tests,
etc.
0 12 24 36 48 60 72 84 96 108
Hours based on 45 upgrades
Source Release SAP R/3 4.6C

Business downtime in hours

Distribution of values

Range of values
Median: 48.0

Min: 23.6 Max: 88.4

0 12 24 36 48 60 72 84 96 108
Hours based on 99 upgrades

© SAP 2009 / 20
 Upgrades to SAP ERP 6.0 Support Release 3:
Technical Downtime

Downtime:
Downtime:
Minimum
Minimum possible
possible
technical
technical downtime
downtime
(if
(if “downtime
“downtime minimized”
minimized”
had
had been
been used
used as
as an
an
upgrade
upgrade strategy,
strategy, and
and
there
there was
was no
no dialog
dialog time
time
during
during procedure
procedure
execution)
execution)

Average 7.3 h
xx% < 10 h

63% < 7 h

© SAP 2009 / 21
 Agenda

1. Downtime
1.1 Definition of Downtime
1.2 What are the elements of Production Downtime during an Upgrade?
1.3 Influencing Factors for Runtime & Downtime
1.4 Some Facts & Figures about Downtime
1.5 Costs vs. Downtime
1.6 Downtime Strategies
2. Improvements by SAP
3. Upgrade Tuning
3.1 Tuning within SAP Standard
3.2 Details on Incremental Conversion (ICNV)
3.3 Customer-Based Upgrade (CBU)
3.4 Incremental Upgrade & Unicode Conversion (IUUC)
4. Summary
© SAP 2009 / 22
 Costs vs. Downtime

Influencing Factors Downtime with Downtime with some Downtime

special measures special measures without special
measures
Storage and CPU Usage of faster Upgrade Coaching
Type CPUs & Storage Use latest Upgrade tools
Customer-based Usage of Incremental
Start & Target upgrade Conversion (ICNV)
Release Downtime Parallelize tasks during
Optimization cutover
Version of
Service
Upgrade Tools Upgrade Coaching
Number of Clients Usage of new
backup tools &
Usage of backup strategy
Incremental Automate testing
Conversion for go-decision

No significant
influence by
Modifications
Database size

© SAP 2009 / 23
 Costs vs. Downtime (cont.)

1 2 3 4
Hardware Software Configuration Strategy

Number and type Start & Target Upgrade Upgrade Strategy

of CPUs for the Release Parameterization (downtime or
Downtime

App. & DB Server Version of the (e.g., number of resource

Type & Upgrade Tools processes) minimized)
performance of the Number of clients Usage of
Storage Incremental
Conversion (ICNV)

Avg. Techn. Donwtime

Standard Business
Downtime

Downtime
Tuning

© SAP 2009 / 24
 Costs vs. Business Downtime

Avg.
Technical
Downtime

© SAP 2009 / 25
 Agenda

1. Downtime
1.1 Definition of Downtime
1.2 What are the elements of Production Downtime during an Upgrade?
1.3 Influencing Factors for Runtime & Downtime
1.4 Some Facts & Figures about Downtime
1.5 Costs vs. Downtime
1.6 Downtime Strategies
2. Improvements by SAP
3. Upgrade Tuning
3.1 Tuning within SAP Standard
3.2 Details on Incremental Conversion (ICNV)
3.3 Customer-Based Upgrade (CBU)
3.4 Incremental Upgrade & Unicode Conversion (IUUC)
4. Summary
© SAP 2009 / 26
 Planning the Upgrade Strategy: Purpose

Im
su por
e bs t o
iv titu f
h s
pro t i tion
e
c de
Ar mo f e op duct
n
o as era ion
tab tio
da n

Upgrade Database
Strategy backup

Ma of
pe xim ze tain e
i
do rmit um S er as
wn ted c tab es
tim l
e da tab

© SAP 2009 / 27
 Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime Short downtime
Minimized Medium amount of space
required if you need to recover
the database
No offline backup required
after upgrade if archiving
deactivated at some stage
Increased demand on system
resources due to parallel
operation of production and
shadow system
Disk capacity for a possible
database recovery is monitored

Resource No additional system Long downtime

Minimized resources during upgrade Offline backup required after
No additional space upgrade
requirements for enabling
possible database recovery
Disk capacity for a possible
database recovery is not
monitored

© SAP 2009 / 28
Two Upgrade Strategies

“Downtime Minimized” “Resource Minimized”

Temporary SAP Web AS is used in parallel to Temporary SAP Web AS is used, when central
central instance instance is down
More resources are needed (CPU/Memory) No additional resources are needed
Same upgrades with "downtime minimized" method Downtimes 4.x to SAP R/3 Enterprise

50 20
18
40 16
Customers in %

Customers in %
14
30 12
10
20 8
6
10 4
2
0
0
4

4
2

10

-1

-1

-2

-2

-3

-3

-3

-4

-4

-5

-5
0-

4-

8-

12

16

20

24

28

32

36

40

44

48

52
Hours Hours
Avg.~8 Avg.~18
Downtime- Resource-
minimized minimized
EU_IMP0

EU_IMPORT START_SHDI

ACT
DIST... PRD SHD STOP_SHDI
SHD_IMP MODPROF_T

XCNV
PARCONV
TABIM NT I ME
XPRA DOW MODPROF_P
 System Switch Upgrade: Downtime Strategies

Downtime minimized Resource minimized

Temporary SAP instance is used in Temporary SAP instance is used when
parallel to central instance central instance is down
More resources are needed No additional resources are needed
(CPU/RAM)

Production Server Production Server

Central Upgrade Central Upgrade

Instance Shadow Instance Shadow
Instance Instance

running running offline running

Both instances running in parallel Both instances running exclusively

© SAP 2009 / 30
 System Switch Upgrade: The Timing Diagram
Binding SPs, EhPs, and Add-ons
does not significantly impact the Prod. Downtime
(on target release)

downtime!
Shadow Instance

Resourced minimized

Substitution Set
Support Packs

Adjustments
Modification

Distribution
Activation
Import of

Add-Ons
Inst. Prod. Downtime

EhPs
Downtime minimized

Upgrade
Uptime

ICNV
New
Prepare Upgrade Downtime minimized
Release

Backup
Backup
Downtime

Backup

Imp.
Resourced minimized Post
Stop of Production Upgrade
(strategy-dep.)
© SAP 2009 / 31
 Agenda

1. Downtime
1.1 Definition of Downtime
1.2 What are the elements of Production Downtime during an Upgrade?
1.3 Influencing Factors for Runtime & Downtime
1.4 Some Facts & Figures about Downtime
1.5 Costs vs. Downtime
1.6 Downtime Strategies
2. Improvements by SAP
3. Upgrade Tuning
3.1 Tuning within SAP Standard
3.2 Details on Incremental Conversion (ICNV)
3.3 Customer-Based Upgrade (CBU)
3.4 Incremental Upgrade & Unicode Conversion (IUUC)
4. Summary
© SAP 2009 / 32
 New Upgrade Tools and Developments

One-step Upgrade to SAP ERP 6.0 including SAP Enhancement

1 Package 4
Available
Details: Direct Upgrade path from SAP R/3 or SAPERP 2004 to SAP ERP 6.0 with since May
the option to include technical usages of Enhancement Package 4 2008 SAP
Benefit: Cost & downtime reduction, no additional implementation steps for EhP4 ERP 6.0/SR3
necessary

2 New Enhancement Package Installer utilizing System Switch Technology Available since
April 2009
Details: Advanced technology for EhP installation

Benefit: Significant downtime reduction for SAP Enhancement Package

installation (including support packages)

Incremental Upgrade & Unicode Conversion (IUUC)

3 Q4+/2009
Details: Combined Approach with Standard SAP Upgrade & SAP migration tools

Benefit: Significant downtime reduction for upgrade & Unicode conversion within
one downtime window

© SAP 2009 / 33
 Improvements for Technical Downtime

Business perspective

Business Uptime Business Downtime

Technical perspective
Upgrade Follow-up
Prepare Upgrade Uptime
Downtime activities

SAP reduced technical

downtime by ~50 % due SAP ERP 6.0 - SR0 (06/2005): 14.9 h
to incremental tuning of
Upgrade tools
SR1 (04/2006): 10.2 h
Further reductions via
improved Customer-
Based Upgrade (CBU) SR2 (04/2007): 8.3 h
possible
SR3 (05/2008): 7.3 h
SR = Service Release
© SAP 2009 / 34
 Downtime with System Switch Upgrade

Binding Support Packages to the upgrade does not impact significantly the downtime
of the upgrade process!

= Uptime!

Package System Switch

count: Upgrade
32 Technology
16
8

Without
packages
1h

DDIC ACT PCON TABIM XPRA Misc.

© SAP 2009 / 35 Uptime!
 Summary

System Switch upgrade with “downtime minimized” strategy minimizes

technical upgrade process downtime
Further downtime minimization beyond standard upgrade technology can be
achieved via utilization of Downtime Assessment Service and Customer-
based Upgrade Service
SAP is ready to assist you with comprehensive upgrade service offerings in
the planning and execution of your next upgrade
SAP Upgrade Roadmap provides the project team guidance on how to
manage the upgrade project successfully
SAP Upgrade Info Center is the initial access point to find key upgrade
information

© SAP 2009 / 36
 Agenda

1. Downtime
1.1 Definition of Downtime
1.2 What are the elements of Production Downtime during an Upgrade?
1.3 Influencing Factors for Runtime & Downtime
1.4 Some Facts & Figures about Downtime
1.5 Costs vs. Downtime
1.6 Downtime Strategies
2. Improvements by SAP
3. Upgrade Tuning
3.1 Tuning within SAP Standard
3.2 Details on Incremental Conversion (ICNV)
3.3 Customer-Based Upgrade (CBU)
3.4 Incremental Upgrade & Unicode Conversion (IUUC)
4. Summary
© SAP 2009 / 37
 Upgrade Tuning Within SAP Standard
Actions to Reduce Runtime & Downtime

Upgrade Follow-up
Prepare Upgrade Uptime
Downtime activities

Usage of new hardware

Usage of the latest Upgrade Software/Tools (SAP ERP 6.0 SR3/SAPup/Fixbuffer)

Usage of “Downtime minimized” upgrade strategy

Use as many parallel upgrade processes as possible

Include all required support packages into the upgrade

Include all required technical usages from EhP into the
upgrade
Use transport(s) created for automatic Modification
Adjustment (SPDD/SPAU)

Set import destination time

Hardware
Software & Tools Usage of ICNV
Create well thought-out Cutover Plan
Configuration
Strategy
Backup Strategy
Services

© SAP 2009 / 38
 Upgrade Tuning (in Addition to Standard)
To What Extent Can Downtime Be Minimized?

1 Service is provided by Active Global Support (AGS)

2 Gives guidance to reduce downtime

© SAP 2009 / 39
 Agenda

1. Downtime
1.1 Definition of Downtime
1.2 What are the elements of Production Downtime during an Upgrade?
1.3 Influencing Factors for Runtime & Downtime
1.4 Some Facts & Figures about Downtime
1.5 Costs vs. Downtime
1.6 Downtime Strategies
2. Improvements by SAP
3. Upgrade Tuning
3.1 Tuning within SAP Standard
3.2 Details on Incremental Conversion (ICNV)
3.3 Customer-Based Upgrade (CBU)
3.4 Incremental Upgrade & Unicode Conversion (IUUC)
4. Summary
© SAP 2009 / 40
 Goals of ICNV

ICNV is only available when using downtime minimized

Reduction of upgrade downtime

Large tables are now converted during uptime
Only switch to new structure during downtime
(in PARCONV)

Easy handling
Fully integrated into upgrade process

Configurable conversion process

Exclusion times
Progress prediction

© SAP 2009 / 41
 Overview

View T1
Create (4)

Table T1_old Table QCMT1

(New structure)
Table T1 Create (1)
Add
Field
(3)

Rename (2)

Update
Trigger
Create
(5)
Delete
Create (6)
Trigger

© SAP 2009 / 42
 Transaction ICNV: Initialization and ICNV
Assistant
ICNV Configuration:
Number of background
jobs
Selection of background
hosts
Exclusion times

Support through
ICNV Assistant:
Initialization
Start of data conversion

Monitor progress:
Computation of
conversion statistics
Estimation of time
to finish
Status display

Transition to new Repository structure is done by the upgrade!

© SAP 2009 / 43
 Aspects of ICNV

Conversion of large tables during system uptime

Conversion process can be stopped and restarted

Possible error situations occur during uptime

ICNV especially suited for WORM tables

ICNV is fully integrated into the upgrade

Tables to be processed by ICNV can be selected

Conversion process is configurable

Additional resource usage of DBMS

Sufficient number of background work processes

Execute ICNV as early as possible

© SAP 2009 / 44
 Agenda

1. Downtime
1.1 Definition of Downtime
1.2 What are the elements of Production Downtime during an Upgrade?
1.3 Influencing Factors for Runtime & Downtime
1.4 Some Facts & Figures about Downtime
1.5 Costs vs. Downtime
1.6 Downtime Strategies
2. Improvements by SAP
3. Upgrade Tuning
3.1 Tuning within SAP Standard
3.2 Details on Incremental Conversion (ICNV)
3.3 Customer-Based Upgrade (CBU)
3.4 Incremental Upgrade & Unicode Conversion (IUUC)
4. Summary
© SAP 2009 / 45
 Customer-Based Upgrade

Customer-Based Upgrade

Save additional downtime

spent by a large number of
post-upgrade imports!

Reasons Requirements
Large volume of transports for Fast copy of production system
modification adjustment, adaptation of Appropriate hardware for test
custom code, etc. upgrade

Benefits Risks & Issues

No transports after upgrade No development in production
Report loads pre-generated and part of system during upgrade (code
export data freeze)
Reductions in application adjustment
Accurate timing for production upgrade
© SAP 2009 / 46
 Further Reduction of Overall Technical
Downtime
Import of Customer
Upgrade Downtime includes:
Transport Requests after
Technical Upgrade Runtime (SAPup)
Upgrade
Modification Adjustments (SPAU) or via transport
(contains Repository &
Add-on upgrades (e.g., ST-PI)
Customizing objects)

Uptime

cross-client

specific
client-
DDIC ACT PCON TABIM XPRA Rest Imports after
Upgrade
© SAP 2009 / 47
 Customer-Based Upgrade: Process

Production
P@4.6
P@4.6 P@4.6
P@4.6 P@4.6
P@4.6 P@6.0
P@6.0

upgrade
copy copy
CBU
Support Packages
Support Packages Re-
Re-package
Add-on CBU
Add-onInstallation/Upgrade
Installation/Upgrade
Customer
Customerdevelopment
development Package
Modification
Modificationadjustment
adjustment

upgrade
C@4.6
C@4.6 C@6.0
C@6.0 C@4.6
C@4.6 C@6.0
C@6.0
upgrade test

SAP
SAP
Upgrade
Upgrade

© SAP 2009 / 48
 Summary: Customer-Based Upgrade

Uptime Inclusion of additional packages

Add-on installations (SAINT)
Add-on upgrades (SAINT)
Support Packages
Add-on patches, CRTs

cross-client
No modification adjustments
No transports after upgrade except for
customizing

specific
client-
Reductions in application adjustment
Accurate timing on production upgrade
DDIC ACT PCON TABIM XPRA rest Imports after
Upgrade

“Customer-Based Upgrade” for upgrading to SAP ERP

Upgrade to target release including customer-defined number of support packages, modification
adjustments, pre-generated loads, ...
Repackage large number of post-upgrade transport requests and bind them as single change request
into shadow import phase of upgrade (uptime!)
Note: Customer-Based Upgrade (CBU) is a Consulting Service delivered by SAP Technical
Consulting only with direct Backoffice support of upgrade development team.

© SAP 2009 / 49
 Agenda

1. Downtime
1.1 Definition of Downtime
1.2 What are the elements of Production Downtime during an Upgrade?
1.3 Influencing Factors for Runtime & Downtime
1.4 Some Facts & Figures about Downtime
1.5 Costs vs. Downtime
1.6 Downtime Strategies
2. Improvements by SAP
3. Upgrade Tuning
3.1 Tuning within SAP Standard
3.2 Details on Incremental Conversion (ICNV)
3.3 Customer-Based Upgrade (CBU)
3.4 Incremental Upgrade & Unicode Conversion (IUUC)
4. Summary
© SAP 2009 / 50
 Proposed Solution

Two workstreams
Optimization of existing standard procedures
Near Zero Downtime procedure in specific customer projects
Near Zero Downtime Procedure
(Solution part 2)
Project-based execution
Based on system clone and Migration
Database Size [TB] Workbench

Optimization of standard procedure

(Solution part 1)
5-10 out of these 30–100 customers and
all other customers
30 -100
MaxAttention
Customers
3-4 Standard combined UC and Upgrade
for all customers
2
max. business downtime [h]
3 48

© SAP 2009 / 51
 Customer Requirements

Customers’ requirements are

Business Downtime for an upgrade is 2-4 hours
In case of problems, the upgrade must be completely resettable
Upgrade procedure should be reusable for all critical SAP systems, initially
SAP R/3
Upgrades are technical upgrades. It must be ensured that all business processes
are running.
The procedures should also be (re)used for applying support packages
The business downtime for applying support packages should be 1-2 hours
It is acceptable that no customizing and repository changes (via transport requests)
occur during 24-36 hours

© SAP 2009 / 52
 Incremental Upgrade and Unicode Conversion

Consistent system split with the logging of database changes

Synchronization of the changes between the main system and the copy – delta replay
Optimization of the system validation and sign-off

(reduced) uptime downtime

PRD
SAP R/3 4.6C

Delta replay
Recording
clone

PRD
SAP ERP 6.0

Upgrade and Unicode Conversion

Validation,
sign-off
cloned
PRD

© SAP 2009 / 53
 Incremental Upgrade and Unicode Conversion
Tools and Technologies

Tools and Technologies used in the SAP Proposal:

Consistent Split: Hot Standby Databases (e.g., HADR)
Recording: Trigger Technology like in IMIG/MDS
Delta Replay: Migration Workbench (MWB) from System Landscape Optimization (SLO)

These tools and methods need to be adapted and enhanced

© SAP 2009 / 54
 Comparison to Standard Upgrade

Advantages
Strongly reduced downtime (4 hrs?)
Improved system availability
Re-usability for the implementation of Support Packages
Late go/no-go decision and very fast reset of the system
The standard Upgrade project remains unaffected

Drawbacks
Additional project effort – longer upgrade project (min. 6 months)
Additional Hardware requirements
Code freeze for 4-6 weeks prior to Go-Live
Restricted transport for 1-2 weeks prior to Go-Live

© SAP 2009 / 55
 Incremental Upgrade and Unicode Conversion
Delivery Model as Service

PLANNING BUILDING RUNNING

Complete Execution
Complete Execution Customer receives a “turnkey” solution by SAP
We deliver a complete solution
SAP Engagement

Expert Guidance
Expert Guidance
SAP is responsible for solving key challenges and critical issues for the customer
We solve key challenges
Frontoffice: Consulting, Active Global Support
Backoffice: Development, AGS, SLO

Max Attention/Safeguarding
Quality Management
SAP manages the quality assurance through continuous engagement
We audit and provide directions
Frontoffice: Consulting, Active Global Support
Backoffice: AGS, SLO

© SAP 2009 / 56
 Agenda

1. Downtime
1.1 Definition of Downtime
1.2 What are the elements of Production Downtime during an Upgrade?
1.3 Influencing Factors for Runtime & Downtime
1.4 Some Facts & Figures about Downtime
1.5 Costs vs. Downtime
1.6 Downtime Strategies
2. Improvements by SAP
3. Upgrade Tuning
3.1 Tuning within SAP Standard
3.2 Details on Incremental Conversion (ICNV)
3.3 Customer-Based Upgrade (CBU)
3.4 Incremental Upgrade & Unicode Conversion (IUUC)
4. Summary
© SAP 2009 / 57
 Resources

SAP ERP
Homepage: http://service.sap.com/erp *
Development News: http://service.sap.com/developmentnews *
Release Notes: http://service.sap.com/releasenotes *
Release Strategy: http://service.sap.com/releasestrategy *
Maintenance Strategy: http://service.sap.com/maintenance *
Scenario & Process Component List: http://service.sap.com/scl *

SAP NetWeaver®
Home page: http://sdn.sap.com/irj/sdn/NetWeaver
System Landscape Directory: www.sdn.sap.com/irj/sdn/nw-sld
Software Lifecycle Manager: www.sdn.sap.com/irj/sdn/lcm

SAP Enhancement Packages

Homepage: http://service.sap.com/erp-ehp *
* Requires login credentials to the
SAP Service Marketplace
© SAP 2009 / 58
 Resources (cont.)

SAP Upgrade Info Center

Home page: http://service.sap.com/upgrade *
SAP ERP Upgrade: http://service.sap.com/upgrade-erp *
SAP Upgrade Road Map: https://websmp202.sap-
ag.de/~sapidb/011000358700003618582003 *
SAP Upgrade News: http://service.sap.com/upgrade-news *

SAP Upgrade Tools

System Switch Technology: www.sdn.sap.com/irj/sdn/upgradetech
SAP Solution Manager: http://service.sap.com/solutionmanager *

SAP Upgrade Services

Services Overview: http://service.sap.com/upgradeservices *

* Requires login credentials to the

SAP Service Marketplace
© SAP 2009 / 59
 7 Key Points to Take Home

Downtime costs not linear over the downtime

Downtime minimized upgrade methodology
Customers should strongly consider this version and, if needed, some steps in the
CBU process to further reduce downtime
Use ASU Toolbox and Upgrade Accelerator to reduce/eliminate time
required for manual pre- & post-upgrade actions
Binding SPs, EhPs and Add-ons does not significantly impact the
downtime!
Incremental Table Conversion (ICNV)
Conversion of large tables during system uptime
Customer-Based Upgrade (CBU)
If you have a large volume of transports for modification adjustment, adaptation of
custom code, etc.
Incremental Upgrade & Unicode Conversion
Project-based execution based on system clone and Migration Workbench
© SAP 2009 / 60
 Thank You for Your Time

Questions?

Lon S Blake
Upgrade Principal
SAP Upgrade Competency
Center NA

SAP America
3999 West Chester Pike
Newtown Square, PA
19073

M 610-457-7473
E lon.blake@sap.com

© SAP 2009 / 61
 Copyright 2009 SAP AG
All Rights Reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
SAP, R/3, xApps, xApp, SAP NetWeaver®, Duet™, SAP Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos
are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned and associated logos
displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document
contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy,
and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or
other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of
merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation
shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these
materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch
SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.
Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet™, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die
dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen
von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu
Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.
Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen
Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten
Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die
Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder
ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck
sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.
SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung
dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.
Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks
zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über
Internetseiten Dritter ab.
Alle Rechte vorbehalten.

© SAP 2009 / 62