You are on page 1of 22

SAP HANA 1.

0
Revision Strategy
SAP HANA Product Management
July 2017
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]


The term “Revision” refers to
SAP HANA client [Revision 70 – 74] [Revision 80 – 85] [Revision 90 – 97] packages containing fixes for the
SAP HANA core components (SAP The “Support Package
SAP HANA studio [Revision 70 – 74] [Revision 80 – 85] [Revision 90 – 97] Stack (SPS)” marks the
HANA Database, Studio**, Clients,
AFLs**, Lcapps*, SDA, HWCC tool) point in time when new
SAP HANA AFL [Revision 70 – 74] [Revision 80 – 85] [Revision 90 – 97]
features and capabilities
SAP Host Agent SP171 SP180 SP194 are introduced by
All other parts of the SAP HANA implementing the Revisions
SAP HANA Smart Data Access SP001 SP001 SP004 platform become visible on SAP and SPs referenced in the
Service Marketplace as “Support SPS.
SAP HANA INA Toolkit SP007 SP008 SP008 Packages (SP)”.
… … …

This list had been simplified for illustration perspectives and does not show the entire bill of material of SAP HANA

*LCApps will move out of HANA Platform Edition with SPS11 **AFL and Studio may ship faster that HANA DB
© 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
shipments of the last SAP HANA Revision within a certain
SPS, for example 97.01, 97.02 or 102.01.
Ÿ Maintenance Revisions by definition provide 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 Bugs without known workarounds
Ÿ 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 stable 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.
• DSP is only declared one time after the initial delivery according to the above description. DSPs are not
declared during maintenance period

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 and enhancements 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 priority-
one support.

SPS 09 SPS 10
…. 84 85 90 91 92 … 100 101 102 …

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


SAP HANA SPS 09 SPS 10
planned maintenance, leveraging the SAP
HANA Datacenter Service Points Revision 84 85 90 91 96 97 100 ... 102 102.01…

DSP 09 DSP 10

• 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


SPS 09 SPS 10
bug fixing, using SAP HANA Maintenance SAP HANA
Revisions Revisions 83.. 85 90 91 96 97 100 101 102 102.01…

85.01 97.01
85.02 97.02
85.xx 97.xx

• To customers running SAP HANA in production (or with a planned Go-live of less than 8 weeks),
SAP provides SAP HANA Maintenance Revisions until the DSP of the next SPS is declared. These
Maintenance Revisions 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 Revision available on SAP Service
Marketplace to benefit from incremental, but non-disruptive improvements.
• Starting with SPS10, Maintenance Revisions will be delivered right after the DSP Revision e.g. 102.01
© 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 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


© 2015 SAP SE or an SAP affiliate company. All rights reserved. CUSTOMER 11
Overview of Capture and Replay Functionality
Current Features and Product Benefits

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
3rd party tools
• Reduces manual effort for testing changes in customer
deployments

© 2015 SAP SE or an SAP affiliate company. All rights reserved. CUSTOMER 12


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 8 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. They are provided once DSP is reached*.

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 *Starting with SPS10
© 2015 SAP SE or an SAP affiliate company. All rights reserved. CUSTOMER 13
SAP HANA Maintenance Strategy
Overview Timeline
• New capabilities are introduced twice a year, every time a new SAP HANA Support Package Stack (SPS) is
released. This happens normally in December and June
• Datacenter Service Point is declared about 3 month after RTC, normally in March and September
• SAP is not providing maintenance revisions for previous SPS anymore once the DSP of the next SPS is declared
• Critical bug fixes and security patches are provided as SAP HANA revisions for all HANA SPS that are still in
maintenance
• We recommend that maintenance timelines and project go live dates are adjusted to this release schedule

SPS nn +1 SPS nn +
RTC DSP
SPS nn SPS nn
RTC DSP
SPS nn -1 SPS nn -1
RTC DSP

Dec March June Sept Dec March

See SAP Note 2021789 for further details


© 2015 SAP SE or an SAP affiliate company. All rights reserved. CUSTOMER 14
SAP HANA Maintenance Strategy
Revision Strategy for SPS12
Customers running mission critical systems demand a longer provisioning of Maintenance Revisions
For SAP HANA SPS12:
• SAP will provide Maintenance Revisions for a period of 5 years after SPS12 RTC
• There will be regular upgrade paths from SPS12 to any newer SPS

SPS 12 SPS 12 SPS 12 Maintenance Revisions


RTC DSP SPS 12
… EoM
May
2021
SPS 11 SPS 11
RTC DSP
SPS 11
EoM

Dec March June Sept


2015 2016 2016 2016

DSP is only declared one time after the initial delivery. DSPs are not declared during maintenance period ŸSee SAP Note 2021789 for further details
© 2015 SAP SE or an SAP affiliate company. All rights reserved. CUSTOMER 15
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 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 downwards compatibility ability of SAP HANA)

See SAP Note 1913302 or Step-by-Step Implementation Guide for SAP HANA System Replication available
for https://scn.sap.com/docs/DOC-47702 for further details.

© 2015 SAP SE or an SAP affiliate company. All rights reserved. CUSTOMER 17


SAP HANA Business Continuity
Revision Update with SAP HANA Zero Downtime Maintenance

1 2 3
SAP NetWeaver SAP NetWeaver SAP NetWeaver
ABAP Server ABAP Server ABAP Server

DBSL DBSL DBSL


# Cluster Manager
(e.g. SUSE
Cluster)
# Connectivity
Suspend
Cluster Manager
(e.g. SUSE
Cluster)
#
Software
virtual 1. Update
Upgrade Take-
2. Reconfigure
virtual
IP over 3. Re-initiate IP
Order
SAP HANA Version SAP HANA Version +1 SAP HANA Version SAP HANA Version +1 SAP
SAP HANA
HANA Version
Version +1 SAP HANA Version +1
Walldorf Sync/Async mirrored Rot Walldorf Sync/Async mirrored Rot Walldorf Sync/Async mirrored Rot
redo log writing redo log writing redo log writing
Primary Secondary Primary Secondary Primary Secondary

Transport Transport Transport


incremental data incremental data incremental data
Data Log Data Log Data Log Data Log Data Log Data Log

© 2015 SAP SE or an SAP affiliate company. All rights reserved. CUSTOMER 18


SAP HANA Revision and Maintenance Strategy
Summary

Release of Datacenter Service Point


New SPS

SAP HANA 90 91 96 ... 97 100 101 102 102.01... …


Revisions:
97.01 Zero Downtime
97.02 Maintenance SAP HANA Revision Update
97.xx Revisions

Revision Type Schedule Comprises of Recommended to

RTC Revision Every 6 months New features and fixes Early adapters and
(e.g. Rev. 80, 90, …) Non-production systems
Standard Revision On demand Incremental fixes, Early adapters and Non-production
(e.g. Rev 81, 94, …) based on latest SPS feature set systems
DSP Revision Every 6 months, Incremental fixes, Production systems
(e.g. Rev. 82, 96, …) after having run in SAP production system for 2+ weeks based on latest SPS feature set (targeting planned maintenance)
Maintenance Revision On demand, Incremental critical fixes only, Production systems, (targeting
(e.g. 85.03, 97.01, Up to SPS09 provided for previous SPS between RTC and DSP only planned and unplanned
102.01…) As of SPS10: provided after DSP for the current SPS 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 19
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 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

• 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

© 2015 SAP SE or an SAP affiliate company. All rights reserved. CUSTOMER 20


Thank you
Contact information

Joerg Latza
VP, SAP HANA Product Management
Joerg.latza@sap.com
© 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 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.

© 2015 SAP SE or an SAP affiliate company. All rights reserved. CUSTOMER 22