SAP’s New Zero Downtime Option:
Now Ready-to-Go!
Dr. Bernd Kohler, SAP Development Manager, SAP on IBM z Systems & DB2 for z/OS
zSAP Technical Briefing, Chicago, 8-Jun-2016
Public
Continuous Availability
A Must Have for Many Companies
Provides access to
business functions
Planned downtime
 24x7 business
 Examples: ecommerce, PoS,
mobile devices, global
business, deployments
 SP & release upgrades
 Customer transports &
enhancements
Continuous
availability
Enables access to
innovations
 currently introduction of new
functions requires a system
outage
 functions are developed but not
implemented
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Unplanned downtime
 Hardware failure / Malfunction
including Networks
 Software Malfunction /
security threat / update
 Natural / Man-made disasters
 Failure of compliance &
operation
 Unplanned outages
Public
2
Roadmap to Business Continuity
BUSINESS DOWNTIME
SUM Options for ABAP Based Business Suite Products
standard mode
advanced mode (nZDM)
Software Update Manager
(SUM)
Zero Downtime Option
of SUM (ZDO)*
2010
2012
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
2013
2014
2015
2016
2017
Public
3
ZDO Technical Details
Zero Downtime Option (ZDO) of Software Update Manager
Solution approach
The idea
under construction
All common cars can take
the lanes
use existing lanes
restricted speed
The ZDO solution approach
release 1
By default all daily processes can
be used during upgrade procedure
maintenance
release 1
release 2
No system copy / clone
use existing DB (minimal DB footprint)
restricted use
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Public
5
Zero Downtime Option of SUM
Maintenance Procedure without Technical Downtime
upgrade procedure
starts in shadow
technical
validation
(optional)
Instances
SUM
Shadow
technical
validation
/
upgrade
business
validation
(optional)
V1->V2
SUM
Upgrade
Production
V1->V2
V1
V2
V2
V1
bridge phase
transition to bridge
back on
productive
system
last point
to rollback
ramp up
cool down
incl. restart
uptime (maintenance mode)
V1 = start release
bus.
down
time
uptime
V2 = target release
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Public
9
Coexistence of Production and Upgrade
Production System V1
Persistent.
enq
V1
Repo
Persistent.
enq
V2
V1
Temp
V2
V1
Temp~~
Temp
Shared~~
Shared
V1=V2
V1
Shared
V1
Config
V1
Except
V1
Config~~
V1
Except~~
Bridge Schema
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Trig
V2
Appl~~
Delta
Import
Config
replicate
V2
Table
Migration
Except
V1~V2
V1
Appl
Upgrade system sets
Persisted Enqueue locks
in production system.
Instance V2
Repo
Repo~~
V1
DIDI
Upgrade System V2
RFC
Appl
No access!
Org Schema
Public
10
Zero Downtime Option of SUM
Maintenance procedure without technical downtime
SUM Roadblock
steps
Config./Checking
cool down of start
release and ramp up
of target Release
soft reconnect to
Bridge schema
Instance(s)
Prod.
dialog instance
Shd./
Upgr
bridge phase
original
schema
Production DB schema
shadow
bridge
views
original
schema
update instance
original
schema
Upgrade DB schema
uptime (maintenance mode)
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Post-processing
Execution
Pre-processing
down
time
uptime
Public
11
Continuity of your Standard Business During Upgrade
Shadow operation
ZDO
of
SUM
production V1
business
downtime
bridge phase
maintenance V1  V2
Version 1(SAP Update + customer release)
cool
down
ramp
Tests /
up
Verification
Production
V2
ZDO considers customer
transport requests:
Zero Downtime Option of SUM
performs the phases of the
execution roadmap step in
uptime
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Use of customer buffer to add
customer transport requests to
ZDO procedure
All customer transports are
imported and activated in
uptime
SUM calls main manual postprocessing steps after update
automatically in uptime, e.g.
RGZZGLUX, RV80HGEN
Public
12
Cool Down for Restart
Optimizations
bridge phase
ZDO
of
SUM
production V1
V1 = source release
Version 1maintenance V1  V2
business downtime
ramp production
cool
validation
V2
up
down
V2 = target release
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Public
13
Cool Down for Restart
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
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Public
14
ZDO – Further Ideas
Concept to Tackle Remaining Downtime
Plans for a future ZDO version (*)
Most importantly for Banking, Gateway and EWM
Version 2 fully operational
Version 2
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
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
(*) These ideas describe work in progress. No statements about if an when this will be delivered can be made at this time.
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Public
15
ZDO Prereqs
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
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Public
17
ZDO on DB2 for z/OS
Prerequisites and Recommendations
 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
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Public
18
ZDO Availability
Focus of ZDO*
ZDO Enablement for Products & Databases
Updates for SAP Business Suite, minimum start release:
SAP ERP – ERP 6.0 EHP7 SP6 / NW 7.40 SP8

1
1 Available
on request with
SUM 1.0 SP16
1

SAP NetWeaver 7.40 SP8

SAP EWM – EWM 9.1 SP2 / NW 7.40 SP8

SAP CRM – CRM 7.0 EHP3 SP8 / NW 7.40 SP8

SAP GTS – GTS 11.0 SP0 / NW 7.40 SP8

SAP Banking Services – BaS 9.0 SP00 / NW 7.50 SP1
1
2
2 available
2
2
on
projects basis
Minimum database release:


SAP HANA 1.00.9
SAP ASE 16.0.02.03
Oracle 11.2.0.4
DB2 for z/OS 11.1.5

Further DBs on project basis:


Pre-requisites: Unicode system required

MS SQL 11.0
 IBM DB2 LUW (DB6) 10.5 FP5
 MaxDB, DB2 iSeries
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
* For detailed enablement details see SAP note 2163060
Regarding used AddOns, a pre-check is needed
Public
20
Availability Details
What does “available on project basis” mean?


The project is based on a service contract; SAP Support (AGS) or SAP Consulting are involved

Workshop to define scope, functionality and schedule

Direct support as defined

Cookbook optimization
SAP Development supports your project directly in close cooperation with SAP AGS / Consulting
What does “available on request” mean?

The product / DB combination is enabled and validated with SUM 1.0 SP16

Proven strategy for shipping new SUM functionality: Technically it is GA, but SAP Lifecycle Management wants to control it

SAP Software Lifecycle department is still in close cooperation with you and needs your feedback

Request to use ZDO via OSS message

Telco to verify scope, answer questions, explain tasks for prep and execution

Productive support on request

Service support still recommended for knowledge ramp up / cookbook optimization
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Public
21
Zero Downtime Option of SUM
Key Messages

ZDO considers the overall business downtime of our customers
 Today: reduce business downtime to a restart
 Goal: reduce business downtime to some minutes

ZDO is an option of SUM in SL Toolset

Customer transports are included
 Adopts release cycles from partners and customer releases much faster
ZDO
is available for customers since January 2016
ZDO
is successfully tested for customer upgrades
ZDO
is verified for SAP ERP and SAP NetWeaver on most common DB
ZDO is available on request with SUM 1.0 SP16 (SAP note 2163060)
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Public
22
Key Links for More Information
SCN Blog:
Zero Downtime Option of SUM (ZDO) is “available on request”
Zero Downtime Option of Software Update Manager
SAP News:
http://www.news-sap.com/getting-one-downtime
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Public
23
ZDO & z
Continuous Availability as Key Differentiator for z Systems
Zero Downtime Maintenance for the Complete z Stack
Frequency
Server
Failure
+5 Years
2 Years
Disaster
ZDO
Storage
Data
Corruption
Failure
SAP
HW & OS
Upgrades
Refresh
DR
Test
Yearly
Half Yearly
Data Center
EHPI
Maintenance
Kernel
Big
Upgrades
Transports
SAP
Support
Packs
Quarterly
Infrastructure
Zero Downtime!
Failures
HW & OS
Maintenance
Monthly
Profile
Changes
(Online)
Weekly
Database
REORG
Small
Transports
Daily
Ultimate Goal within Reach!
Online
Backup
Zero DT
SUM Zero Downtime Option
Successful POCs done in 2015
Controlled availability in 2016
Minutes
<1 Hours
<2 Hours
< 4 Hours
< 8 Hours
<16Hours
Critical
DT Area
<24Hours
Downtime
Source: Martin Dvorský et al. (IBM)
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Public
25
Continuous Availability as Key Differentiator for z Systems
Situation in a Distributed Environment (UNIX, Windows) with ZDO
Frequency
Disaster
ZDO
+5 Years
SAP
Upgrades
2 Years
Data
Corruption
Storage
Failure
HW & OS
Refresh
Server
Failure
Yearly
DR
Test
DatabaseData Center
REORGMaintenance
EHPI
Kernel
Upgrades
Half Yearly
SAP
Big
Transports
Support
Packs
Infrastructure
HW & OS
Maintenance
Quarterly
Monthly
Weekly
Daily
Failures
Profile
Changes
(Online)
Small
Transports
Offline
Backup
Online
Backup
Zero DT
Minutes
Only IBM z Systems customers
will fully benefit from
SAP Zero Downtime Option!
<1 Hours
<2 Hours
< 4 Hours
< 8 Hours
<16Hours
Critical
DT Area
<24Hours
Downtime
Source: Martin Dvorský et al. (IBM)
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Public
26
Thank you!
Contact information:
[email protected]
© 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 forwardlooking 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.
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Public
28