Martin Herrmann, Product Management Cloud & Lifecycle...

Martin Herrmann, Product Management Cloud & Lifecycle Management

SUM SL Toolset SP12

Downtime Minimization Capabilities of SUM

© 2014 SAP AG. All rights reserved. 2 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

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.

Legal disclaimer


Minimization of downtime is business critical


SUM is the tool: target system releases

Upgrade, EHPs, SPs for target releases

SAP Business Suite 7 Innovations 2011

SAP NetWeaver 7.3 and higher

EHPs and SPs for target releases

SAP Business Suite 7 Innovations 2010

SAP NetWeaver Process Integration (PI)

SAP NetWeaver CE, MI 7.1 and above

Example: SAP ERP 6.0

7.0 7.01 7.31

7.02 SAP BASIS

04 7.0 SAP NetWeaver

4.6C…6.40

7.0 EHP3 7.0 EHP2 7.0 EHP1

SAP ERP 6.0

SAP ERP 6.0 EHP 1

SAP ERP 6.0 EHP 2

Bottom line versions are only

relevant for ABAP stack

7.4

7.4

R/3 4.6C & 4.7

BASIS 4.6D

SAP ERP 5.0

SAP Business

Suite (BS) 7

SAP BS 7

Innovations 2010

SAP BS 7

Innovations 2011

Version for

SAP HANA

No path to

EHP 6H

EHP5

EHP4

EHP3

EHP6

EHP6H

EHP7

SAP BS 7

Innovations 2013

Applying SPs

Update/Upgrade

Using SUM for System Maintenance:


Basic concept regarding downtime minimization capabilities of

SUM

SUM replaces tools

for upgrade, update, and implementing SPs.

Consolidated to SP Stacks SAP EHPs

UP

Software

Update Manager

SAPehpi

SAPup

Upgrade

ABAP

ABAP

SAP EHPs SPS

UP

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.

https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1589311


Business criticality of downtime for SAP systems

Version 1 as-is

procedure

business downtime productive use

cool down system maintenance by

Software Update Manager

(SUM)

tests /

verification

ramp

up

Minimizing the planned business downtime

is in focus

of downtime minimization capabilities of SUM

cust.

trsp.

technical downtime


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


Configuration to minimize downtime


Focus on downtime minimization in SUM Big picture

Uptime

Installation

preparation

SUM

standard

mode

Uptime

Shadow

operation

Business Downtime

SUM

advanced

mode

Extended

shadow

operation

Business Downtime

Installation

preparation Shadow

operation

Savings of

40-60%

Savings

app. 50%

obsolete

SGEN Technical

downtime

(system update)

Te

st &

ve

rifica

tion

Customer

transports.,

add-ons,...

Sys

tem

ram

p u

p

Sys

tem

co

ol d

ow

n

Technical

downtime

(system update +

custom transports)

Te

st &

ve

rifica

tion

Sys

tem

ram

p u

p

Sys

tem

co

ol d

ow

n

nZDM

Customer

transports

import


Downtime minimization for AIMs and SGEN

Uptime

Co

nv

ers

ion

,

main

imp

ort, X

PR

A’s

Valid

atio

n

Ram

p u

p

Co

ol d

ow

n

Shadow operation

Business Downtime

Rep

osito

ry

ob

jects

AIM

s

Sw

itch

Po

st-p

rocessin

g

No

n re

po

sito

ry

ob

jects

Cu

st.. X

PR

A’s

, AIM

s

Customer trsp.

SG

EN

Minimum

downtime

Move the most intensive time consuming

AIMs to shadow

Optional parameter to run SGEN in Shadow


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

http://scn.sap.com/docs/DOC-32544




Maintenance downtime improvements realized with nZDM Reference customer example (SAP ERP system, EHP update)

EHP Installer

(Feb. 2012)

Cool down Validation &

ramp up

2:00 h

SUM with nZDM

(July 2012)

SUM with nZDM

(July 2013)

Cool down Technical downtime Transports &

manual steps

Validation &

ramp up

2:45 h 9:00 h 4:30 h 2:00 h

Technical

downtime

Transports

&

manual steps

Cool down Technical

downtime

2:45 h

Transports

&

manual steps

2:15 h

Validation &

ramp up

2:00 h

2:45 h

2:45 h

18:15 h

11:15 h

9:45 h

4:00 h 2:30 h

Business Downtime

Business Downtime

Business Downtime


TCO Lab Preview: nZDM for SAP ERP 6.0 EHP6

System Details:

• OS/DB: AIX/Oracle

• DB size: 1,7 TB

• System clone from a customer

Source:

ERP 6.0 SR3

Target:

ERP 6.0 with EHP6

Technical Usages:

• Central Applications

• Human Capital Management

• IS-Utilities

• Strategic Enterprise Management

Generation of ABAP loads during uptime Source: TIP Core LM TCO Lab measurements

hours

Minimum

Downtime

Overall

Uptime

5:41

2:31

Update with nZDM

Update w/o nZDM

Significant downtime reduction when using the nZDM capabilities of

Software Update Manager for the Business Suite 7i2011


Downtime minimization with nZDM of SUM how it works

Uptime

Shadow

operation

Technical Downtime

• 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

Extended shadow

operation

Sw

itch

tab

les

an

d

Kern

el

Ex

ec

ute

XP

RA

s / A

IMs

(XP

RA

s U

PG

)

Imp

ort c

on

ten

t

ap

pl. T

ab

les

(Ta

bim

UP

G)

Ad

just c

en

tral

SA

P N

W ta

ble

s

(xn

cv-p

ha

se

s)

Ad

jus

t ap

plic

atio

n

tab

les

(pa

rcon

v u

pg)

Conversion, main import, XPRAs

Po

st-p

roc

es

sin

g

DD

Ls


Newest info + Troubleshooting nZDM

Information about:

Database/SUM SP specific restrictions

Solution (reference to guide)

Troubleshooting

note 1678564 “Restrictions, Database-specific Settings, and Troubleshooting of nZDM for SUM”


Quick facts: import customer transports in SUM

Technical details:

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 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

SCN blog:

customer transports import

https://service.sap.com/sap/support/notes/1759080

http://scn.sap.com/community/it-management/alm/software-logistics/blog/2013/07/04/considering-of-customer-transports-to-minimize-the-downtime-for-sap-business-suite-updates-and-upgrades


Import Customer transports to SUM How it works

Customer transport objects

not enabled to run in uptime

are integrated into the

SUM downtime operations

Customer transport objects

enabled to run in uptime

are integrated into the

shadow operations

Uptime Business Downtime

Te

st &

ve

rifica

tion

Sys

tem

ram

p u

p

…

Shadow

operation

Cu

sto

me

r

rep

os

itory

ob

jec

ts

Po

st-p

roc

es

sin

g

Cu

sto

me

r

no

n re

po

sito

ry

ob

jec

ts

Cu

sto

me

r XP

RA

’s,A

IMs

Min

imu

m d

ow

ntim

e

Cust. transports Technical

downtime


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,

– Customizing Uptime Bus. downtime

buffer


How to get customer transports import in SUM

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

Import of customer transports is available on request: see SAP note 1759080


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)

– …


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”


Requirements using nZDM/SUM Calculation example

40 GB for SUM installation directory on central instance

12 GB for Download Directory with EHP data, kernel, stack XML

~ 10 GB free space in /trans (DIR_TRANS) directory (recommended)

~ 80 GB for temporary shadow system installation

total ~ 140 GB

total ~ 80 - 350 GB

Total estimated files space requirements using SUM nZDM:

for development or test system : ~ 170 – 290 GB

for production system : ~ 220 – 490 GB

Temporary space requirements using SUM:

~ 30 – 150 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 for logging tables

Note: Depends on user workload (update, insert, delete) and active recording time of relevant appl. tables.

Additional temporary space requirements using SUM with nZDM:

Database

and

File System


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

Considering of customer transports to minimize

the downtime of SAP Business Suite updates

Settings to activate downtime minimization

capabilities in SUM

Software Update Manager (SUM): introducing the

tool for software maintenance

near-Zero Downtime Maintenance

Import customer transports

Settings of downtime minimization capabilities

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

http://scn.sap.com/community/business-continuity



http://scn.sap.com/community/it-management/alm/software-logistics








http://scn.sap.com/community/it-management/alm/software-logistics/blog/2013/07/04/considering-of-customer-transports-to-minimize-the-downtime-for-sap-business-suite-updates-and-upgrades


http://scn.sap.com/community/it-management/alm/software-logistics/blog/2012/11/07/software-update-manager-sum-introducing-the-tool-for-software-maintenance

http://scn.sap.com/community/it-management/alm/software-logistics/blog/2012/11/07/software-update-manager-sum-introducing-the-tool-for-software-maintenance

http://websmp201.sap-ag.de/sltoolset



http://service.sap.com/roadmap

Thank You!

Contact information:

Martin Herrmann

email: [email protected]

mailto:[email protected]


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.

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.

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.

Martin Herrmann, Product Management Cloud & Lifecycle...

Documents

Transcript of Martin Herrmann, Product Management Cloud & Lifecycle...