SAP HANA
Revision Strategy
SAP HANA Product Management
August 2015
Table of Contents
SAP HANA Terminology
 Understand the difference between Support Package Stack, Support Packages and SAP HANA Revisions
 What are SAP HANA Maintenance Revisions, what is the SAP HANA Datacenter Service Point?
SAP HANA Maintenance Strategy
 Understand the SAP HANA product availability and maintenance strategy
 When to implement which type and release of an SAP HANA Revision?
SAP HANA Business Continuity
 Revision Update with SAP HANA Zero Downtime Maintenance
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
CUSTOMER
2
Terminology
Related to SAP HANA Revision and Maintenance Strategy
SAP HANA Terminology
What is a Revision? What is a Support Package Stack?
In the context of the SAP HANA platform:
•
•
•
Corrections are shipped in the form of Revisions and Support Packages of the product’s components.
New capabilities are only introduced twice a year, every time a new SAP HANA Support Package Stack
(SPS) is released.
For easier handling, the numbering of SAP HANA SPS and Revisions had been aligned.
Revision 90 for example refers to the first SAP HANA Revisions which contains SPS 09 related capabilities.
Component
SPS 07
SPS 08
SPS 09
SAP HANA database
[Revision 70 – 74]
[Revision 80 – 85]
[Revision 90 – 97]
SAP HANA client
[Revision 70 – 74]
[Revision 80 – 85]
[Revision 90 – 97]
SAP HANA studio
[Revision 70 – 74]
[Revision 80 – 85]
[Revision 90 – 97]
SAP HANA AFL
[Revision 70 – 74]
[Revision 80 – 85]
[Revision 90 – 97]
SAP Host Agent
SP171
SP180
SP194
SAP HANA Smart Data Access
SP001
SP001
SP004
SAP HANA INA Toolkit
SP007
SP008
SP008
…
…
…
The term “Revision” refers to
packages containing fixes for the
SAP HANA core components (SAP
HANA Database, Studio, Clients,
AFLs, LCapps, SDA, HWCC tool)
All other parts of the SAP HANA
platform become visible on SAP
Service Marketplace as “Support
Packages (SP)”.
The “Support Package
Stack (SPS)” marks the
point in time when new
features and capabilities
are introduced by
implementing the Revisions
and SPs referenced in the
SPS.
This list had been simplified for illustration perspectives and does not show the entire bill of material of SAP HANA
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
CUSTOMER
4
SAP HANA Terminology
What does the SAP HANA Maintenance Revision offer?
 The SAP HANA Maintenance Revisions are minor-version
shipments of the last SAP HANA Revision within a certain
SPS, for example 85.01, 85.02 or 74.01.
 Maintenance Revisions by definition only provides fixes for:
o Major bugs concerning critical functionality in key SAP HANA
scenarios (Business Suite on SAP HANA, SAP BW on SAP
HANA, SAP HANA Data Marts)
o Production systems or endangered Go-lives
within the next 6 weeks
o Bugs with non existing workaround
o Minor code dependencies and code changes or impact
 More details on possible update paths from SAP HANA
Maintenance to standard SAP HANA Revisions can be
found in SAP Note 1948334.
* ) will be further explained on the next slide
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
CUSTOMER
5
SAP HANA Terminology
What does the SAP HANA Datacenter Service Point stand for?
The SAP HANA Datacenter Service Point (DSP):
•
Is a point in time, providing customers with more guidance as to when and on the base of which revision
they should plan their production SAP HANA maintenance.
•
Is based upon the availability of a certain SAP HANA revision, which – as a proof of SAP’s commitment and
belief in the quality of its own software – had been running within SAP production enterprise
applications for at least two weeks before it is officially released.
•
As customers have to schedule their maintenance between quarterly end closings, and to allow a certain
period of time to apply and run these revisions within SAP’s production enterprise applications,
the DSP has been defined to lie between the SAP HANA SPSs, i.e. in March and in September.
Further information about which SAP HANA revision is referenced by
a certain DSP can be found in SAP Note 2021789.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
CUSTOMER
6
Maintenance Strategy
Recommendations for planned and unplanned maintenance of SAP HANA
SAP HANA Maintenance Strategy
Incremental, non-disruptive innovation
• Updates to the SAP HANA Platform will be released in the form of SAP HANA Support Package
Stacks twice per year, delivered from within a single delivery stream.
• As updates shipped for the SAP HANA Platform are strictly downward compatible, earlier Revisions may
be removed from SAP Service Marketplace with availability of a newer SAP HANA Revision of the
same SPS. Incompatible changes may be considered for legal or security reasons, but are subject to a
strict exception approval process.
• The SAP HANA Platform product remains in maintenance as long as any SAP business application
releases built on top of SAP HANA are in mainstream maintenance, extended maintenance, or priorityone support.
SPS 08
…. 73 74
SPS 09
80 81 82 …
90 91 92 …
Updates are cumulative
and strictly downward compatible
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
CUSTOMER
8
SAP HANA Maintenance Strategy
SAP HANA system - Planned Maintenance
Recommended path for production systems
planned maintenance, leveraging the SAP
HANA Datacenter Service Points
SPS 08
SAP HANA
80 81 82 ...
Revision 73 74
DSP 08
SPS 09
85
90 ...
96 97 …
DSP 09
•
To customers running SAP HANA in production (or with a planned Go-live of less than 6 weeks),
SAP recommends to stay on the current SAP HANA Support Package Stack until the next SAP HANA
Datacenter Service Point is reached.
•
Past this point, SAP strongly recommends to update to the SAP HANA revision, shipped as a DSP revision,
or any newer SAP HANA revision of the same SPS, available on SAP Service Marketplace.
•
Customers running SAP HANA in a non-production environment (or planning for initial system setup)
may adapt new SAP HANA SPS at any time.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
CUSTOMER
9
SAP HANA Maintenance Strategy
SAP HANA system – Bug Fixing (“Unplanned Maintenance”)
Recommended path for production systems
bug fixing, using SAP HANA Maintenance
Revisions
SPS 08
SAP HANA
80 81 82 ...
Revisions 73 74
74.01
74.02
74.xx
SPS 09
85
90 91 ... 96 97 …
85.01
85.02
85.xx
•
To customers running SAP HANA in production (or with a planned Go-live of less than 6 weeks),
SAP provides SAP HANA Maintenance Revisions, allowing them to stay on an older SPS for up to
three months longer. These Maintenance Revision contain only a subset of available fixes, identified to
be relevant in particular for production environments.
•
To customers running SAP HANA in a non-production environment (or planning for initial system setup)
SAP proposes the implementation of the highest SAP HANA Revisions available on SAP Service
Marketplace to benefit from incremental, but non-disruptive improvements.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
CUSTOMER
10
SAP HANA Maintenance Strategy
Test Requirements
All updates shipped for the SAP HANA Platform are strictly downward compatible
•
Incompatible changes may be considered for legal or security reasons, but are subject to a strict exception
approval process and documented in SAP notes.
•
SAP executes regression tests for applications shipped by SAP; known regressions are documented in the
SAP HANA release note of a Revision
•
We suggest that customers consider regression tests based on their actual setup and usage of SAP
applications.
•
If customer consider doing regression tests, than they might consider technical regression tests only, Business
Acceptance tests are normally not required if no new features are used on application level
•
For self-written or 3rd Party Applications we recommend to run full regression tests before updating to a never
HANA Revisions
•
SAP offers customers to include their HANA scenario in the SAP HANA regression tests
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
CUSTOMER
11
SAP HANA Maintenance Strategy
Recommendation for customers running SAP HANA in production
In a nutshell:
•
The early SAP HANA revisions of each new SPS - from RTC until DSP – are supported and can
be used for productive usage. For customers running SAP HANA productively (or with a
planned go-live of less than 6 weeks) however, SAP recommends waiting until DSP is reached.
•
Once the SAP HANA DSP is reached, SAP strongly recommends going live with the DSP
revision, or updating production systems to the DSP revision, or any newer SAP HANA
revision of the same SPS.
•
The SAP HANA Maintenance revisions are recommended for productive usage, while only
containing critical fixes / a subset of available fixes.
Note: Customers who have already downloaded or run a certain SAP HANA revision, shipped as a
DSP revision, do not need to update to a successor revision unless they are facing an issue or a
SAP Note reports a critical bug which applies to the specific scenario the customer is running.
RTC: Release for Customer | DSP: Datacenter Service Point | SPS: Support Package Stack
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
CUSTOMER
12
Business Continuity
In regards to SAP HANA maintenance activities
SAP HANA Business Continuity
Revision Update with SAP HANA Zero Downtime Maintenance
SAP offers the SAP HANA Zero Downtime Maintenance capability
based on connectivity suspend feature of the SAP NetWeaver AS ABAP stack:
 DBSL of the database interface decouples transaction management of AS ABAP stack and of SAP HANA
database
 This keeps transaction on AS ABAP layer alive and allows to change components (software versions) on the
layers below on secondary (shadow) SAP HANA instance
 Important is to understand that the software upgrade order is to be started on end of chain and continued to
the head of chain (ensuring use of the downwards compatibility ability of SAP HANA)
See SAP Note 1913302 or Step-by-Step Implementation Guide for SAP HANA System Replication available
here for further details.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
CUSTOMER
14
SAP HANA Business Continuity
Revision Update with SAP HANA Zero Downtime Maintenance
1
2
SAP NetWeaver
ABAP Server
DBSL
Cluster Manager
(e.g. SUSE
Cluster)
Software
Upgrade
Order
SAP HANA Version
Walldorf
Primary
Log
DBSL

Connectivity
Suspend
SAP HANA Version +1 SAP HANA Version
Sync/Async mirrored
redo log writing
Rot
Walldorf
Secondary
Primary
Sync/Async mirrored
redo log writing
Rot
Walldorf
Secondary
Primary
Log
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Data
Log
virtual
IP
3. Re-initiate
SAP HANA Version +1 SAP
SAP HANA
HANA Version
Version +1
Transport
incremental data
Data

Cluster Manager
(e.g. SUSE
Cluster)
1. Update
2. Reconfigure
Takeover
Transport
incremental data
Data
SAP NetWeaver
ABAP Server
DBSL

virtual
IP
3
SAP NetWeaver
ABAP Server
SAP HANA Version +1
Sync/Async mirrored
redo log writing
Rot
Secondary
Transport
incremental data
Data
Log
Data
Log
Data
CUSTOMER
Log
15
SAP HANA Revision and Maintenance Strategy
Summary
Release of
New SPS
SAP HANA
Revisions:
80
Datacenter Service Point
81
82
...
85
90
91 …
85.01
Zero Downtime
SAP HANA Revision Update
85.02
85.xx
Revision Type
Schedule
Comprises of
Recommended to
RTC Revision
(e.g. Rev. 80, 90, …)
Every 6 months
New features and fixes
Early adapters and
Non-production systems
DSP Revision
(e.g. Rev. 82, 96, …)
Every 6 months,
after having run in SAP production system for 2+ weeks
Incremental fixes,
based on latest SPS feature set
Production systems
(targeting planned maintenance)
Standard Revision
(e.g. Rev 81, 94, …)
On demand
Incremental fixes,
based on latest SPS feature set
Systems on DSP Revision
and Non-production systems
Maintenance Revision
(e.g. 74.01, 85.03, …)
On demand,
provisioned for previous SPS between RTC and DSP only
Incremental critical fixes only,
based on predecessor SPS feature set
Production systems,
(targeting unplanned maintenance)
RTC: Release for Customer | DSP: Datacenter Service Point | SPS: Support Package Stack
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
CUSTOMER
16
References
•
SAP HANA Revision and Maintenance Strategy
SAP Note 2021789
•
Recommended update paths for SAP HANA Maintenance Revisions
SAP Note 1948334
•
SAP Release Strategy Brochure
https://service.sap.com/releasestrategy
•
SAP Product Availability Matrix
https://service.sap.com/pam
•
SAP HANA Product Page
http://www.saphana.com
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
CUSTOMER
17
Thank you
Contact information
Joerg Latza
SAP HANA Product Management
[email protected]
© 2015 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.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
CUSTOMER
19