SAP_HANA_strategy.pdf learn about sap ha

ppt

1. SAP HANA 2.0
Revision Strategy
SAP HANA Product Management
September 2018
See SAP Note 2378962for additional
information and recommendations on
SAP HANA Revision and Maintenance Strategy.

2. 2CUSTOMER©2017 SAP SE or an SAP affiliate company. All rights reserved.
Table ofContents
SAP HANA Terminology
ŸUnderstand the difference between Support Package Stack, Support Packages and SAP HANA Revisions
ŸWhat are SAP HANA Standard and Maintenance Revisions?
ŸHow is upward compatibility defined ?
SAP HANA Maintenance Strategy
ŸUnderstand the SAP HANA product availability and maintenance strategy
ŸWhen to implement which type and releaseof anSAP HANA Revision?
SAP HANA Business Continuity
ŸRevision Update with SAP HANA Zero Downtime Maintenance

3. Terminology
Related to SAP HANA Revision and Maintenance Strategy

4. 4CUSTOMER©2017 SAP SE or an SAP affiliate company. All rights reserved.
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 RevisionsandSupport Packagesof the product’s components.
•New capabilities are only introduced once 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 000 for example refers to the first SAP HANA Revision which contains HANA 2.0 SPS 00 related capabilities.
ComponentSPS 00SPS 01SPS 02
SAP HANA database[Revision 000 –00n] [Revision 010 –01n] [Revision 020 –02n]
SAP HANA client[Revision 000 –00n] [Revision 010 –01n] [Revision 020 –02n]
SAP HANA studio[Revision 000 –00n] [Revision 010 –01n] [Revision 020 –02n]
SAP HANA AFL[Revision 000 –00n] [Revision 010 –01n] [Revision 020 –02n]
SAP Host AgentSPnnSPnnSPnn
SAP HANA Smart
Data Access
SPnnSPnnSPnn
SAP HANA INA ToolkitSPnnSPnnnSPnn
… … …
The term “Revision” refers to a
maintenance package of a SAP
HANA core component (SAP HANA
Database, Studio, Clients, AFLs*,
SDA, HWCC tool).
Each Revision and Support Package
has its own release cycle and can be
installed/upgraded separately.
This list had been simplified for illustration perspectives and does not show the entire bill of material of SAP HANA
A “Support Package
Stack (SPS)” is the SAP
HANA PLATFORM release
that bundles new features
and functions thru a set of
component Revisions and
SPs being entirely validated
and provided as a single
media for consumption.
All other parts of the SAP HANA
platform become visible on SAP
Service Marketplace as “Support
Packages (SP)”.
*AFL and Studio may ship faster that HANA DB

5. 5CUSTOMER©2017 SAP SE or an SAP affiliate company. All rights reserved.
SAP HANA Terminology
What does the SAP HANA Standard Revision offer?
ŸThe SAP HANA Standard Revisions are shipments after RTC of the initial Revision for a certain SPS,
for example 000, 001 or 011.
ŸStandard Revisions are shipped till RTC of the next SPS
ŸStandard Revisions by definition provide incremental fixes based on the initial SPS feature set

6. 6CUSTOMER©2017 SAP SE or an SAP affiliate company. All rights reserved.
SAP HANA Terminology
What does the SAP HANA Maintenance Revision offer?
ŸThe SAP HANA Maintenance Revisions are minor shipments after the last SAP HANA Standard
Revision for a certain SPS, for example 002.01, 012.01 or 022.01.
ŸMaintenance Revisions are shipped after RTC of the next version until end of maintenance of the
respective SPS
ŸMaintenance Revisions by definition provide fixes for:
oMajor bugs concerning critical functionality in key SAP HANA scenarios (Business Suite on SAP HANA, SAP BW
on SAP HANA, S/4 HANA, BW/4 HANA, SAP HANA Data Marts)
oBugs without known workarounds

7. 7CUSTOMER©2017 SAP SE or an SAP affiliate company. All rights reserved.
SAP HANA Terminology
Upward compatibility
ŸBy upward compatibility, it is understood that
oIn changing from software version n of a product to a product version n+1, existing functions of version n
continue to be supported (or replaced by equivalent functions in case a function was deprecated and is finally
removed)
oData from version n can be transformed to and used with version n+1 without major changes
oInterfaces of version n (APIs, Interfaces for other Systems/Products) remain unchanged
[Kittlaus/Clough09, Software Product Management and Pricing]

8. Maintenance Strategy
Recommendations for planned and unplanned maintenance of SAP HANA

9. 9CUSTOMER©2017 SAP SE or an SAP affiliate company. All rights reserved.
SAP HANA Maintenance Strategy
Incremental, non-disruptive innovation
•Updates and enhancements to the SAP HANA Platform will be released in the form of SAP HANA
Support Package Stacks once a year, delivered from within a single delivery stream.
•As updates shipped for the SAP HANA Platform are strictly upward 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 priority-
one support.

10. 10CUSTOMER©2017 SAP SE or an SAP affiliate company. All rights reserved.
SAP HANA Maintenance Strategy
Revision Strategy for SAP HANA 1.0 SPS12
•SAP will provide Maintenance Revisions for SAP HANA 1.0 SPS12 for a period of 5 years after RTC
•Maintenance Revisions for SAP HANA SPS12 are not scheduled, they are delivered on demand
SPS 11
RTC
SPS 12
RTC
SPS 11
DSP[1]
SPS 12
DSP[1]
DecMarch
2016
JuneSept
2016
ŸSee SAP Note 2378962for further details
20152016
SPS 12 Maintenance Revisions
…
May
2021
•[1](D)atacenter(S)ervice(P)oint, see note SAP Note 2021789

11. 11CUSTOMER©2017 SAP SE or an SAP affiliate company. All rights reserved.
SAP HANA Maintenance Strategy
Revision Strategy for SAP HANA 2.0
•New capabilities are introduced once a year, every time a new SAP HANA Support Package Stack (SPS) is
released. This happens normally beginning of April
•SAP is providing bug fixes and security patches for every SPS for 2 years after RTC*
•The last SPS of a major product version is in maintenance for 5 years after RTC
•We recommend that maintenance timelines and project go live dates are adjusted to this release schedule
SPS 00
RTC
SPS 01
RTC
SPS 02
RTC
Nov AprilAprilJuly
SPS 03
RTC
SPS 04
RTC
April
20162017201820192020
April
*except for SPS 00 and SPS01
July

12. 12CUSTOMER©2017 SAP SE or an SAP affiliate company. All rights reserved.
SAP HANA Maintenance Strategy
Revision Strategy for SAP HANA Cockpit
§Cockpit initially delivered with SAP HANA 2.0 SPS 00 in November 2016
§The cockpit periodically releases Support Packages (SP) delivering new functionalityas well as fixes and
security patches. Each SP includes all the features of the previous SP
§The cockpit also provides patchesfor the most recently released SP for fixes and security patches. Once a
new SP is released, SAP provides no patches for earlier SPs
§When an SAP HANA 2.0 SPS is released, cockpit also releases an SP (i.e. synchronizes with SAP HANA)
SAP HANA
Cockpit
Feb
2017
SP 01 SP 05
Jan
2018
SP 04
Oct
2017
SP releases
+patches
SP 07
Aug
2018
SAP HANA 2.0
Apr
2018
SP 06
SPS 03
Jul
2017
SP 03
SPS 02
Apr
2017
SP 02
SPS 01
Nov
2016
SP 00
SPS 00
Apr
2019
SP ??
SPS 04

13. 13CUSTOMER©2017 SAP SE or an SAP affiliate company. All rights reserved.
SAP HANA Maintenance Strategy
Upgrade to SAP HANA 2.0
ŸCustomers running mission critical systems might stay on SPS12 until May 2021
ŸSAP HANA 2.0 is upward compatible, customers just have to do a normal upgrade, no migration
ŸUpgrade from any SAP HANA system running on SPS10 or newer is possible
•Customers on SAP HANA SPS09 or lower first need to upgrade to a HANA SPS ≧SPS 10*
•However we recommend to first upgrade to the latest SPS12 revision before upgrading to SAP HANA 2.0 to be able to
use Capture & Replay tool for regression tests
SPS 10
RTC
SPS 12
RTC
SPS 11
RTC
May
2021
HANA 2.0
SPS 00
RTC
SPS 12 Maintenance Revisions
HANA 2.0
SPS 01
RTC
*For details on possible update paths see note 1948334

14. 14CUSTOMER©2017 SAP SE or an SAP affiliate company. All rights reserved.
SAP HANA Maintenance Strategy
SAP HANA system -Planned Maintenance
•Customer can upgrade to any available Revision of a new SPS at any point in time
•Starting with SAP HANA 2.0 SPS00, SAP will not explicitly declare a DSP anymore.
•SAP is running DSP[1]qualification validation before RTC of a new SPS
•DSP[1]status is automatically given with RTC of the SPS
Recommended path for production systems
planned maintenance*
*For details on possible update paths see note 1948334
SPS 12
2.0 SPS 00 RTC
2.0 SPS 01 RTC
DSP[1]Quality Validation
DSP[1]Quality Validation
•[1](D)atacenter(S)ervice(P)oint, see note SAP Note 2021789

15. 15CUSTOMER©2017 SAP SE or an SAP affiliate company. All rights reserved.
SAP HANA Maintenance Strategy
SAP HANA system –Bug Fixing (“Unplanned Maintenance”)
•SAP provides SAP HANA Standard Revisionsuntil the RTC of the next SPS is declared.
These Standard Revisions contain only incremental fixes.
•SAP provides SAP HANA Maintenance Revisionsbetween RTC of the following SPS and end of maintenance of the
respective SPS. These Maintenance Revisions contain only major bug fixes, identified to be relevant in particular for
production environments.
•SAP proposes the implementation of the highest SAP HANA Revision available on SAP Service Marketplace to benefit from
incremental, but non-disruptive improvements.
SPS 01
010 011 012 ... 016
SPS 02
020021 022 ...
007.01
007.02
007.xx
016.01
016.02
016.xx
Maint
. Revisions
Maint
. Revisions
Recommended path for production
systems bug fixing, using SAP
HANA Maintenance Revisions
SPS 00
000 001 ... 007
Revision Number are examples only

16. 16CUSTOMER©2017 SAP SE or an SAP affiliate company. All rights reserved.
SAP HANA Maintenance Strategy
Test Requirements
All updates shipped for the SAP HANA Platform are strictly upward 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 customers consider doing regression tests, then 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.*
*Reach out to HANA Product Management for details

17. 17CUSTOMER©2017 SAP SE or an SAP affiliate company. All rights reserved.
OverviewofCapture and Replay Functionality
CurrentFeatures andProductBenefits
Features
•Capture real system workload in productive environments
•Pre-process & replay captured workload on target systems
•Analyze runtimes and compare performance between
system setups
Benefits
•Provides competitive replay, analysis and tuning capabilities
for SAP HANA Database
•Helps ensure that landscape changes do not degrade
system performance
•Enables real simulation of workload without the use of other
3rdparty tools
•Reduces manual effort for testing changes in customer
deployments
Pre
-process
Replay
Capture
Analyze

18. Business Continuity
In regards to SAP HANA maintenance activities

19. 19CUSTOMER©2017 SAP SE or an SAP affiliate company. All rights reserved.
SAP HANA Business Continuity
Revision Update with SAP HANA Zero Downtime Maintenance
SAP offers the SAP HANA Zero Downtime Maintenancecapability
based on connectivity suspend feature of the SAP NetWeaverAS 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 the secondary (shadow) SAP HANA instance
ŸImportant is to understand that the software upgrade order is to be started on end of replication chain and
continued to the head of chain (ensuring use of the upwards compatibility ability of SAP HANA)
See SAP Note 1913302or Step-by-Step Implementation Guide for SAP HANA System Replication available
for https://scn.sap.com/docs/DOC-47702for further details.

20. 20CUSTOMER©2017 SAP SE or an SAP affiliate company. All rights reserved.
Zero Downtime Maintenance for SAP HANA
Revision Update
1 2 3
#
Sync/Async mirrored
redo log writing
Transport
incremental data
Walldorf
Primary
Rot
Secondary
SAP HANA VersionSAP HANA Version +1
Software
Upgrade
Order
SAP NetWeaver
ABAP Server
DBSL
SAP
HANA
LogData
SAP
HANA
LogData
Sync/Async mirrored
redo log writing
Transport
incremental data
Walldorf
Primary
Rot
Secondary
SAP HANA VersionSAP HANA Version +1
SAP NetWeaver
ABAP Server
DBSL#
SAP
HANA
LogData
SAP
HANA
LogData
#
Walldorf
Primary
Rot
Secondary
SAP HANA VersionSAP HANA Version +1
SAP NetWeaver
ABAP Server
DBSL
SAP
HANA
LogData
SAP
HANA
LogData
Cluster Manager
(e.g. SAP LaMa,
SUSE Cluster)
Take-
over
Connectivity
Suspend
Cluster Manager
(e.g. SAP LaMa,
SUSE Cluster)
c. Re-initiate
â. Update
b. Reconfigurevirtual
IP virtual
IP
SAP HANA Version +1
Sync/Async mirrored
redo log writing
Transport
incremental data
HANA
Planned Downtime
virtual
IP
1
2
4
3
56

21. 21CUSTOMER©2017 SAP SE or an SAP affiliate company. All rights reserved.
SAP HANA High Availability: Takeover Procedure
In case of outage
1 2 3
Sync/Async mirrored
redo log writing
Transport
incremental data
Walldorf
Primary
Rot
Secondary
SAP NetWeaver
ABAP Server
DBSL
SAP
HANA
LogData
SAP
HANA
LogData
Sync/Async mirrored
redo log writing
Transport
incremental data
Walldorf
Primary
Rot
Secondary
SAP NetWeaver
ABAP Server
DBSL
SAP
HANA
LogData
SAP
HANA
LogData
Cluster Manager
(e.g. SAP LaMa,
SUSE Cluster)
DNS -
virtual
Hostname
virtual
IP
DNS -
virtual
Hostname
virtual
IP
SAP NetWeaver
ABAP Server
DBSL
DNS -
virtual
Hostname
Walldorf
Secondary
SAP
HANA
LogData
Rot
Primary
SAP
HANA
LogData
Take-
over
Cluster Manager
(e.g. SAP LaMa,
SUSE Cluster)
a) Rebuild
b) Reconfigurec) Re-initiate
Sync/Async mirrored
redo log writing
Transport
incrementaldata
HANA
Unplanned Downtime
1
2
3
45 virtual
IP

22. 22CUSTOMER©2017 SAP SE or an SAP affiliate company. All rights reserved.
SAP HANA Revision and Maintenance Strategy
Summary
Revision TypeSchedule Comprises of
RTC Revision
(e.g. Rev. 000, 010, …)
Beginning of AprilNew featuresand fixes
Standard Revision
(e.g. Rev 001, 011,…)
On demand Incremental fixes,
based on latest SPS feature set
Maintenance Revision
(e.g. 007.01,015.01,…)
On demand,
Provided after RTC ofthe next SPS until end of maintenance of the respective SPS
Incremental criticalfixes only
Maintenance
Revisions
SAP HANA
Revisions:
000001 002 ...007
007.01
007.02
007.xx
Release of
New SPS ZDM
Zero Downtime
SAP HANA Revision Update
010011 012 …
RTC: Release for Customer | SPS: Support Package StackRevision Number are examples only

23. 23CUSTOMER©2017 SAP SE or an SAP affiliate company. All rights reserved.
References
•SAP HANA 1.0 Revision and Maintenance Strategy
SAP Note 2021789
•SAP HANA 2.0 Revision and Maintenance Strategy
SAP Note 2378962
•Recommended update pathsforSAP 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
•SAP HANA Supported Operating Systems
SAP Note 2235581
•SAP HANA Certified and Supported SAP HANA®Hardware
http://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/index.html

24. Thank you
Contact information
Joerg Latza
VP, SAP HANA Product Management
[email protected]

25. ©2016 SAP SE or an SAP affiliate company. All rights reserved.25Public
© 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 ofSAP 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.epxfor 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 orwarranty 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 anymaterial, 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.
© 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 ofSAP 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.epxfor 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 orwarranty 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 anymaterial, 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.
© 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 ofSAP 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.epxfor 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 orwarranty 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 anymaterial, 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.