sap corporate ppt template

Dr. Matthias Gimbel, SAP SE

Business continuity: the SAP Zero Downtime

option on the home stretch

Customer

© 2016 SAP SE or an SAP affiliate company. All rights reserved. 2 Public

Continuous

availability

Hardware failure / Malfunction

including Networks

Software Malfunction /

security threat / update

Natural / Man-made disasters

Failure of compliance &

operation

Unplanned outages

Continuous availability – a must have for many companies

Provides access to

business functions

24x7 business e.g. ecommerce, PoS, mobile devices,

global business, deployments

Enables access to

innovations currently introduction of new

functions requires a system outage – functions are developed but not

implemented

Planned downtime

Unplanned downtime

SP & release upgrades

Customer transports &

enhancements


2010 2013 2012 2014

DO

WN

TIM

E

201X

advanced mode (nZDM)

Zero Downtime Option

of SUM (ZDO)*

Roadmap to Business Continuity* SUM options for ABAP based Business Suite products

standard mode

*This is the current state of planning and may be changed by SAP at any time.

Software Update Manager

(SUM)

2015


SUM Options Status in 2015

V2 = target release

business

downtime

business downtime

Version 1 Cool

down maintenance V1 V2

(SAP Update + customer release) validation

ramp

up production V1

technical downtime

ZDO

of SUM (current state

in 2015)

production

V2

business downtime

Version 1 Cool

down maintenance V1 V2

(SAP Update only) validation

ramp

up

prod.

V1

technical downtime

Standard

mode prod.

V2

Advanced

mode

(nZDM)

customer

transports SGEN

Version 1 production

V2 maintenance V1 V2

(SAP Update + customer release)

cool

down production V1

bridge phase

ramp

up

Tests /

Verification

V1 = source release


Normal production

No restrictions

ZDO Basic Idea

Customer System Shadow/Upgrade System

Normal production

No restrictions

Upgrade uptime

System used productively

Restrictions apply

Shadow system

Export/Cloned content

Adapt Repository Tables

Shadow Import

Bridge Setup

Bridge Phase Online User switch to

different Schema Tables either

– Copied – Cloned w/replay – Shared w/views – Read-only

time

Sh

ad

ow

Upgrade

Application Import

Conversions

AIMs and XPRAs

Customer transports

Brid

ge

S

ch

em

a

Release n+m

Release n

Release n

Release n + m

Release n + m

Release n

Alias +

View

Smart Switch

User Switch

Smart Switch

Release n+m Test


Coexistence of Production and Upgrade

Org Schema

Shared

Except

Config

Appl

Repo

Temp

V2

Bridge Schema

Repo

Temp

Shared

Except

Config

Appl

Repo~~

Temp~~

Shared~~

Except~~

Config~~

Appl~~

V1

V1

V1

V1

V1

V1

DI

DI

V1

V1

V1

V1

V1=V2

V1~V2

Production System V1

V2

V2

V2

Trig

Instance V2

Delta

Import

Table

Migration

Upgrade System V2

Persistent.

enq

Upgrade system sets

Persisted Enqueue locks

in production system.

RFC

No access!

replicate

Persistent.

enq


Continuity of your standard business during upgrade

Version 1 Production

V2 maintenance V1 V2 (SAP Update + customer release)

cool

down production V1

bridge phase

business

downtime

ramp

up

ZDO

of

SUM

Tests /

Verification

The ZDO considers customer

transport requests:

Use of customer buffer to add

customer transport requests to

ZDO procedure

All customer transports are

imported and activated in

uptime

The SUM calls main manual

post-processing steps after

update automatically in uptime,

e.g. RGZZGLUX, RV80HGEN

The Zero Downtime Option of

SUM performs the phases of

the execution roadmap step in

uptime

Shadow operation


Optimize the cool down activities

V1 = source release V2 = target release

Version 1 maintenance V1 V2 production V1

bridge phase

business downtime

*This is the current state of planning and may be changed by SAP at any time.

2015*

ZDO

of

SUM

production

V2

cool

down

ramp

up validation


Cool down improvements based on NW 7.40

http://service.sap.com/sap/support/notes/2050677

Empty queues

– Report RLFW_SD_PROCESS_QUEUES

Suspend batch jobs

– Report: RLFW_SD_SUSPEND_BATCH_JOBS

Notify end user log off

– Report: RLFW_SD_NOTIFY_USERS

Restrict logon to selected users

– Report: RLFW_SD_DISABLE_LOGON

Log off all users

– Report: RLFW_SD_LOGOFF_USERS

Finalize queues

– Report. RLFW_SD_FINALIZE_QUEUES

http://service.sap.com/sap/support/notes/2050677


ZDO Planning Size & Time

Reference: recommended size for the shadow instance in the SUM advanced mode

Software Update Manager procedure: ca. 140 GB

Advanced mode (incl. nZDM, customer transports): ca. 80 – 350 GB

The hardware resource demand for ZDO is expected to be comparable

Factors of ZDO procedure runtime

upgrade procedure (SUM standard mode)

setup of bridge system

customer transports

The overall runtime is only predictable with comparable tests / history


Restricted Availability of ZDO within Standard SL Toolset SP on request, planned for 1Q2016*

Pre-requisite: Unicode system required

Updates for SAP Business Suite Minimum Start Release:

ERP – ERP 6.0 EHP7 SP6 / NW 7.40 SP8

CRM – CRM 7.0 EHP3 SP8 / NW 7.40 SP8

EWM – EWM 9.1 SP2 / NW 7.40 SP6 (**)

GTS – GTS 11.0 SP0 / NW 7.40 SP8 (**)

SAP NetWeaver 7.40 SP8

Minimum Database Release:

IBM DB2 for z/OS (DB2) 11.1.5

SAP HANA 1.00.9

SAP ASE 16.0.00.05

Oracle 11.2.0.4

Further DBs planned for 2016:

– MS SQL 11.0,

– IBM DB2 LUW 10.5 FP5,

– SAP MaxDB

(*)This is the current state of planning and can be changed by

SAP at any time. Regarding industry enablement of SAP

ERP, a detailed check of SAP component version is needed

(**) available on project base


DB2 specifics

See SAP Note 2202047 - DB2-z/OS:SUM: Prereqs and recommendations for ZDO with DB2

for z/OS

DB2 requirements (DB2 11 + PTFs)

DB2 zParm settings (RENAME TABLE with views)

dbsl requirements (Reconnect to Bridge)

UTS requirement for shared tables getting new columns (DROP COLUMN)

Information on resetting the procedure


ZDO – further ideas Concept to Tackle Remaining Downtime

Plans for a future ZDO version (*) Most importantly for Banking, Gateway and EWM

Controlled parallel use ~3 min • Login to version 2 possible

• Read scenarios possible in version 2

• Changes to shared and cloned

tables disabled on version 2

• Finalizing transactions on version 1

Managed System cool down ~ x h - Batch jobs only if runtime fits to switch time

- Use LIS with “direct delta”, synchronous execution

- Use “update task local”: synchronous execution

- Fully automated and standardized

Version 1

Version 2

Version 2 fully operational

(*) These ideas describe work in progress. No statements about if an when this will be delivered can be made at this time.

Thank you Contact information:

Dr. Matthias Gimbel

[email protected]

mailto:[email protected]?subject=DSAG Technologietage 2016 - Frage


© 2016 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate

company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its

affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and

services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as

constituting an additional warranty.

In particular, SAP SE or its affiliated companies have 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 SE’s or its affiliated companies’ strategy and possible future

developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies 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. 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.

http://global12.sap.com/corporate-en/legal/copyright/index.epx



sap corporate ppt template

Documents