Downtime Minimization Capabilities of SUM
Martin Herrmann, Product Management Cloud & Lifecycle Management
SUM SL Toolset SP12
Legal disclaimer
The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the
permission of SAP. This presentation is not subject to your license agreement or any other service or subscription
agreement with SAP. SAP has no obligation to pursue any course of business outlined in this document or any related
presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation
and SAP's strategy and possible future developments, products and or platforms directions and functionality are all
subject to change and may be changed by SAP at any time for any reason without notice. The information in this
document is not a commitment, promise or legal obligation to deliver any material, code or functionality. 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. This document is for informational
purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this
document, except if such damages were caused by SAP´s willful misconduct or gross negligence.
All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements,
which speak only as of their dates, and they should not be relied upon in making purchasing decisions.
© 2014 SAP AG. All rights reserved.
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
2
Minimization of downtime is business critical
© 2014 SAP AG. All rights reserved.
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
3
SUM is the tool: target system releases
Example: SAP ERP 6.0
Upgrade, EHPs, SPs for target releases


SAP Business Suite 7 Innovations 2011
SAP NetWeaver 7.3 and higher
SAP ERP 6.0
SAP ERP 6.0 EHP 1
SAP ERP 6.0 EHP 2
SAP Business
Suite (BS) 7
SAP BS 7
Innovations 2010
SAP BS 7
Innovations 2011
SAP BS 7
Innovations 2013
R/3 4.6C & 4.7
BASIS 4.6D
SAP ERP 5.0
EHP7
EHP6H
EHP6
EHPs and SPs for target releases



Version for
SAP HANA
SAP Business Suite 7 Innovations 2010
EHP5
EHP4
SAP NetWeaver Process Integration (PI)
SAP NetWeaver CE, MI 7.1 and above
No path to
EHP 6H
EHP3
Using SUM for System Maintenance:
Update/Upgrade
Applying SPs
SAP BASIS 4.6C…6.40
SAP NetWeaver
04
© 2014 SAP AG. All rights reserved.
7.0
7.0
7.01
7.0 EHP1
7.02
7.3
Bottom line versions are only
relevant for ABAP stack
7.0 EHP2
7.01 EHP3
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
7.4
7.4
4
Basic concept regarding downtime minimization capabilities of
SUM
SUM replaces tools
for upgrade, update, and implementing SPs.
ABAP
UP
SPS
SAP EHPs
SAPehpi
Consolidated to
ABAP
UP
Upgrade
SAP EHPs
SP Stacks
Software
Update Manager
SAPup
For maintenance activities that are supported by the SUM,
the usage of the substituted tool is no longer supported
starting Q1/2013 (except for SPAM),
see SAP Note 1589311.
© 2014 SAP AG. All rights reserved.
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
5
Business criticality of downtime for SAP systems
Minimizing the planned business downtime
is in focus
of downtime minimization capabilities of SUM
business downtime
productive use
technical downtime
as-is
procedure
© 2014 SAP AG. All rights reserved.
Version
1
cool down
system maintenance by
Software Update Manager
(SUM)
cust.
trsp.
tests /
verification
ramp
up
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
6
Downtime minimization capabilities of SUM for ABAP based SAP
systems
•
Parallel operation of production system and shadow system
•
Import of the substitution set into the shadow tables during production
operation (extended shadow) enables the following in uptime
Activation ABAP loads (SGEN)
–
near-Zero Downtime Maintenance (nZDM)
Customer transports import (available on request, see note 1759080)
TODAY
© 2014 SAP AG. All rights reserved.
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
7
Configuration to minimize downtime
© 2014 SAP AG. All rights reserved.
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
8
Focus on downtime minimization in SUM
Big picture
Uptime
SUM
Technical
downtime
(system update)
Savings of
40-60%
Customer
transports.,
add-ons,...
SGEN
Savings
app. 50%
System
ramp up
Shadow
operation
Test &
verification
Installation
preparation
System
cool down
standard
mode
Business Downtime
obsolete
Business Downtime
Uptime
SUM
Extended
shadow
operation
Technical
downtime
(system update +
custom transports)
System
ramp up
© 2014 SAP AG. All rights reserved.
Shadow
operation
Test &
verification
Installation
preparation
System
cool down
advanced
mode
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
nZDM
Customer
transports
import
9
Downtime minimization for AIMs and SGEN
Uptime
Ramp up
Validation
SGEN
Cust.. XPRA’s, AIMs
Non repository
objects
© 2014 SAP AG. All rights reserved.
Repository
objects
Move the most intensive time consuming
AIMs to shadow
Post-processing
Minimum
downtime
AIMs
Conversion,
main import, XPRA’s
Switch
Cool down
Shadow operation
Business Downtime
Customer trsp.
Optional parameter to run SGEN in Shadow
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
11
Downtime minimization capabilities of SUM
Quick facts: near-Zero Downtime Maintenance (nZDM) feature of SUM
This feature enables the main import running in the shadow during uptime to minimize the
business downtime significantly by using the shadow instance for the main import
Technical details:

Record & Replay technique for business transactions based on database trigger
technology to ensure synchronization between shadow and productive system

Minimizes manual effort:
 all steps run automatically in background
 needed tables are selected automatically

Minimal additional hardware requirement due to shadow-technique:
 DB space is independent from system size
 only some additional DB space needed (80 – 350 GB)

Is available for all ABAP-based Business Suite products and for SAP Process
Integration (dual-stack)
SCN: DOC-32544
© 2014 SAP AG. All rights reserved.
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
12
Maintenance downtime improvements realized with nZDM
Reference customer example (SAP ERP system, EHP update)
Business Downtime
EHP
Installer
(Feb. 2012)
Technical downtime
Cool down
2:45 h
Transports &
manual steps
9:00 h
4:30 h
Validation &
ramp up
18:15 h
2:00 h
Business Downtime
SUM with
nZDM
(July 2012)
Cool down
2:45 h
Transports
Technical
downtime
&
manual steps
4:00 h
Validation &
ramp up
11:15 h
2:00 h
2:30 h
Business Downtime
SUM with
nZDM
(July 2013)
Cool down
2:45 h
© 2014 SAP AG. All rights reserved.
Technical
downtime
2:45 h
Transports
&
manual steps
2:15 h
Validation &
ramp up
9:45 h
2:00 h
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
13
TCO Lab Preview: nZDM for SAP ERP 6.0 EHP6
Significant downtime reduction when using the nZDM capabilities of
Software Update Manager for the Business Suite 7i2011
System Details:
•
OS/DB: AIX/Oracle
•
DB size: 1,7 TB
•
System clone from a customer
Minimum
Downtime
Source:
2:31
5:41
ERP 6.0 SR3
Target:
Overall
Uptime
ERP 6.0 with EHP6
Technical Usages:
• Central Applications
• Human Capital Management
hours
• IS-Utilities
• Strategic Enterprise Management
Generation of ABAP loads during uptime
© 2014 SAP AG. All rights reserved.
Source: TIP Core LM TCO Lab measurements
Update with nZDM
Update w/o nZDM
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
14
Downtime minimization with nZDM of SUM
how it works
Uptime
Post-processing
Execute
XPRAs / AIMs
(XPRAs UPG)
Import content
appl. Tables
(Tabim UPG)
Adjust application
tables
(parconv upg)
Adjust central
SAP NW tables
(xncv-phases)
DDLs
Extended shadow
operation
Switch tables and
Kernel
Shadow
operation
Technical Downtime
Conversion, main import, XPRAs
• Move application tables that are touched by the upgrade/update to the shadow system (ca. 8.000 tables)
• Equip them with a change recording replication (Record & Replay technique)
• DB changes in productive system during maintenance create triggers, changes are recorded
• Replication of DB changes: shadow instance tables are updated after the update phases
© 2014 SAP AG. All rights reserved.
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
15
Newest info + Troubleshooting nZDM
note 1678564 “Restrictions, Database-specific Settings, and Troubleshooting of nZDM for SUM”
Information about:
© 2014 SAP AG. All rights reserved.

Database/SUM SP specific restrictions

Solution (reference to guide)

Troubleshooting
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
19
Quick facts: import customer transports in SUM
This feature integrates the customer transports in the installation procedure. The business downtime is
reduced significantly by using the shadow instance for certain customer transport objects
Technical details:
SCN blog:
customer transports import
© 2014 SAP AG. All rights reserved.

All customer transports are considered, incl. SPAU & Add-Ons

Depending on the transport object types, objects are automatically
managed in uptime or downtime of the standard SUM maintenance
procedure

Flexible regarding size and quantity of customer transports

No additional hardware requirement

Integration into Transport Management System (STMS), SPAU & SPDD,
Change Request Management (ChaRM)

Available on request, see SAP note 1759080
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
20
Import Customer transports to SUM
How it works
Business Downtime
Uptime
System ramp up
Test & verification
Customer XPRA’s,AIMs
© 2014 SAP AG. All rights reserved.
Customer
non repository
objects
Customer transport objects
enabled to run in uptime
are integrated into the
shadow operations
Customer
repository objects
Technical
downtime
Post-processing
Minimum downtime
…
Shadow
operation
Cust. transports
Customer transport objects
not enabled to run in uptime
are integrated into the
SUM downtime operations
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
21
How to identify shadow enabled customer transport orders?
Based on a white list approach the transport orders are checked :
 Objects with object type listed in the white list are moved to shadow instance
 White list currently contains about 100 entries of objects types
 Examples for shadow enabled objects
– Dictionary objects (e.g. tables, view types, search help),
– ABAP objects (e.g. classes, programs, screens)
 Examples for objects transported in downtime
– Roles,
– Authority objects,
– Forms,
Uptime
– Customizing
© 2014 SAP AG. All rights reserved.
buffer
Bus. downtime
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
22
How to get customer transports import in SUM
Import of customer transports is available on request: see SAP note 1759080
 Request functionality by CSS ticket
 Registration is managed by SAP development team
 Support by SAP Active Global Support or SAP Consulting
 Close cooperation with SAP development team ensured
 1-2 pre-tests recommended (planned runtime ca. 5 days for EHP
Implementation)
Combined forces from SAP Active Global Support / SAP Consulting, SAP
development and the customer specialists leads to successful execution
© 2014 SAP AG. All rights reserved.
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
23
Downtime minimization capabilities of SUM for SAP Business Suite
release and platform coverage
Downtime minimization capabilities of SUM are available for the following standard software maintenance
activities:

Apply a Support Package on …
... any ABAP-System with a target release based on SAP NetWeaver 7.0 Enhancement Package 2, SP8 or higher, e.g.
– Apply Support Package 8 or higher (NW 7.02 SP8) on a SAP NetWeaver 7.0 Enhancement Package 2 system
– Apply Support Package 5 or higher on a SAP ERP 6.0 Enhancement Package 5 System
– …

Install an Enhancement Package on top of …
… any ABAP-System with a target release based on SAP NetWeaver 7.0 Enhancement Package 2, SP8 or higher, e.g. :
– Install SAP Enhancement Package 5 on a SAP ERP 6.0 system with SAP Enhancement Package 4
– Install SAP Enhancement Package 2 on SAP NetWeaver 7.0 (ABAP)
– …

Upgrade your system to …
… any ABAP-System with a target release based on SAP NetWeaver 7.0 Enhancement Package 3 or higher, e.g.:
– Upgrade SAP R/3 4.6C to SAP ERP 6.0 Enhancement Package 6 (SAP Business Suite 7 Innovations 2011)
– …
© 2014 SAP AG. All rights reserved.
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
27
Database platforms for downtime minimization
capabilities of SUM
Available for

Oracle, 10g or higher

IBM DB2 LUW, 9.7 FP4 or higher

Microsoft SQL, 2005 or higher

SAP MaxDB 7.9 or higher

IBM DB2 z/OS 10.1 or higher

SAP HANA 1.00.52 or higher

SAP Adaptive Server Enterprise (ASE) 15.7.0.103 (details see SAP note 1926697)

DB2 for IBM i 7.1 (details see SAP note 1809339)
Most current status
• for nZDM see SAP note 1678565 – “Prerequisites, Terms and Conditions for nZDM/SUM”
• For customer transports import see SAP note 1759080 – “Conditions for SUM including customer transport
requests”
© 2014 SAP AG. All rights reserved.
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
28
Requirements using nZDM/SUM
Calculation example
Temporary space requirements using SUM:

40

12
 ~ 10
 ~ 80
GB
GB
GB
GB
for SUM installation directory on central instance
for Download Directory with EHP data, kernel, stack XML
free space in /trans (DIR_TRANS) directory (recommended)
for temporary shadow system installation
Additional temporary space requirements using SUM with nZDM:

total ~ 140 GB
~ 30 – 150 GB
total ~ 80 - 350 GB
for selected application tables which are transferred to shadow system
Note: Depends on individual customer system (selected large tables). Pre-installation analysis possible.

~ 50 – 200 GB
Database
and
File System
for logging tables
Note: Depends on user workload (update, insert, delete) and active recording time of relevant appl. tables.
Total estimated files space requirements using SUM nZDM:

for development or test system : ~ 170 – 290 GB

for production system
© 2014 SAP AG. All rights reserved.
: ~ 220 – 490 GB
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
31
Key links for more information
For customers and partners
Key links SCN

Business Continuity Community
http://scn.sap.com/community/business-continuity

Software Logistics
http://scn.sap.com/community/it-management/alm/software-logistics
SCN Blogs

Near-Zero Downtime Maintenance for SAP
Business Suite Systems
near-Zero Downtime Maintenance

Considering of customer transports to minimize
the downtime of SAP Business Suite updates
Import customer transports

Settings to activate downtime minimization
capabilities in SUM
Settings of downtime minimization capabilities

Software Update Manager (SUM): introducing the
tool for software maintenance
Software Update Manager
Key Links SAP Service Marketplace

Software Update Manager, Update Guide
http://websmp201.sap-ag.de/sltoolset

Road maps on SAP Service Marketplace
http://service.sap.com/roadmap
© 2014 SAP AG. All rights reserved.
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
32
Thank You!
Contact information:
Martin Herrmann
email: Martin.Herrmann@sap.com
© 2014 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.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft
Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,
System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer,
z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER,
OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP,
RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered
trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or
registered trademarks of Adobe Systems Incorporated in the United States and/or other
countries.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
®
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C , World
Wide Web Consortium, Massachusetts Institute of Technology.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,
StreamWork, 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 other
countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports,
Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and
services mentioned herein as well as their respective logos are trademarks or registered
trademarks of Business Objects Software Ltd. Business Objects is an
SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase
products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of Sybase, Inc. Sybase is an SAP company.
All other product and service names mentioned 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. No part of this document may be
reproduced, copied, or transmitted in any form or for any purpose without the express prior
written permission of SAP AG.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are
trademarks or registered trademarks of Citrix Systems, Inc.
© 2014 SAP AG. All rights reserved.
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
35