SAP on Linux the way to S/4HANA

SAP on Linux
the way to S/4HANA
Public

© 2015 SAP SE or an SAP affiliate company. All rights reserved. 3
SAP’s Next Big Thing
R/2
1979
R/3
1992
ERP
2004 2015 20251999
AIX HPUX
Solaris
https://www.youtube.com/watch?v=oi6deWvxzQk

© 2016 SAP SE or an SAP affiliate company. All rights reserved. 4Public
SAP HANA, the great simplifier of enterprise software
SAP HANA
SAP Business
Warehouse
powered
by SAP HANA
SAP Business
Suite powered
by SAP HANA
SAP Simple
Finance
powered
by SAP HANA
 Real-time analysis
 Real-time reporting
 Real-time business
 OLAP and OLTP together
 SAP HANA Enterprise
Cloud for SAP Business
Suite on SAP HANA
 In-memory
platform
 Instant financial insight
 No aggregates
 Single source of truth
 Simplified data model
 New user experience
 Advanced processing
 Choice of deployment
2011 20132012 2014 2015

Paradigm shift where analytics can support business applications
Embedded Analytics
in S/4HANA
applications
 Offers operational
reporting in all
processes to support
decisions
 Operational reporting
can be delegated to
Active/Active Secondary
 S4 development is
adapting its applications
 Completely different
situation than with
classical SAP
application  Extracting
all reporting to SAP BW
or Datamarts

ABAP Platform Today
Foundation for SAP Business Suite
SAP Business Suite
& Suite on HANA
SAP Suite AnyDB SAP Suite on Hana
SAP NW AS ABAP 7.x SAP NW AS ABAP 7.5
AnyDB SAP HANA
ABAP Platform in 2015 – Some numbers
 40.400 Productive ERP 6.0 systems (NW 7x)
 6630 Productive ERP systems on new EhP 7 (NW 74x)
 3,5 million registered ABAP Developers
Key Assets
 Rock solid and scalable - Built for mission critical business
systems
 Effective programming environment - Built for the
complete life cycle of business apps
 Continuously extended to serve new business scenarios

ABAP Platform
The transformation to SAP S/4HANA
SAP S/4HANA – cloud
SAP S/4 HANA
SAP NW AS ABAP
SAP HANA
Classic Suite & Suite on HANA
SAP Suite AnyDB SAP Suite on Hana
SAP NW AS ABAP SAP NW AS ABAP
AnyDB SAP HANA
SAP HANA
Real-time simplified
SAP Fiori
Cloud
SAP S/4HANA on premise
SAP S/4HANA
SAP NW AS ABAP
SAP HANA

S/4HANA
Migration & Upgrade Paths
Suite on HANAUnicode
ECC 6, EhP x..7
AnyDB, Unicode
Start-Release Matrix for one-step Conversion
sFIN 1.0
sFIN 1503EhP 7
EhP 7
S/4HANA
S/4HANA 1511
In-place Upgrade
DMO: Upgrade including DB migration
(Database Migration Option of Software Update Manager) S/4HANA 1605
> 60% of installed
customer systems

S/4HANA
Migration & Upgrade Paths
<=46C 470, ERP 2004 ECC 6, EhP x..7
Suite on HANA
Unicode
Non-Unicode
ECC 6, EhP x..7
AnyDB, Unicode
Upgrade
required
Unicode
Migration
required
Unicode
Migration
required
Start-Release Matrix requiring two-step Conversion
Fastest path: Use “DMO” (Database Migration Option of Software Update Manager)
incl. Unicode-Migration to EhP 7 Suite on HANA for Start Releases down to 46C.
sFIN 1.0
sFIN 1503EhP 7
DMO
EhP 7
S/4HANA
S/4HANA 1511
4.70, ERP 2004
AnyDB, Unicode
Upgrade
required
DMO
1
2
S/4HANA 1605
Details
~37% (22% on ERP 6) of
installed customer systems
~3% of
inst. systems

SIMPLE DATA MODEL
» Only main tables remaining, no redundancies
» Clear separation of master data from transactional data
» Reduction of memory footprint
THROUGHPUT INCREASE
» INSERT only on database level (MM-IM),
no locks for standard price valuation
BusinessSuite
MATDOC ACDOCAMaterial
Prices
Material
MBEW
OBEW
QBEW
OBEW
MBEWH
OBEWH
QBEWH
OBEWH
MLHD
MLPP
MLIT
MLCR
Document
MLPPF MLCRF
CKMLPP CKMLCR
Totals
CKMI1
Index
GLPCA
ZZFISLA
FAGLFLEXA
GLFUNCA
COFIS
BKPF
BSEG
COBK
COEP
ANEK
ANEP
GLPCT
ZZFISLT
FAGLFLEXT
GLFUNCT
COSP
COSS
COFIT
BSIMBSID
BSAD
BSIK
BSAK
BSIT
BSAT
BSIS
BSAS
MARD
MARC
MSTQH
MSTEH
MSTBH
MSSQH
MSSAH
MSPRH
MSLBH
MSKUH
MSKAH
MKOLH
MCHBH
MARDH
MARCH
MSTQ
MSTE
MSTB
MSSQ
MSSA
MSPR
MSLB
MSKU
MSKA
MKOL
MCHB
MKPF
MSEG
Totals
MM-IM
Document
Totals
Totals
Indices
Documents
BKPF
SIMPLE PROCESSES
» Only one valuation method (Material Ledger)
instead of 2 (IM + ML)
» Flexible rebate management instead of
cumbersome and expensive redundancies
Inventory Mgmt.
(Quantities)
Inventory Mgmt.
(Valuation via „MBEW)
Material Ledger
(multi GAAP, multi currency)
Accounting
Master Data Inventory Mgmt
(Quantities)
Material Ledger
(multi GAAP, multi currency)
Accounting
VBAK LIKP VBRK
LIPSVBAP VBRP VBFA
VBUK
VBUP
VAPMA
VAKPA
VLPMA
VLKPA
VRPMA
VBOX
S066
S067
EIKP
EIPO
NAST
Sales and Distribution
VRKPA
Primary
Document tables
Index
tables
Sales and Distribution
Status tablesLIS tables
Rebate index Output mgmt
Export/import
tables
VBAK LIKB VBRK
LIPSVBAP VBRP VBFA
Conversion to S/4HANA: Why do we have new challenges for the Upgrade?

AnyDB or HANA
Problem Space Overview
SAP
Content 1.0
HANA
ABAP Runtime
System v1.0
Software Update
Manager
(SUM)
ABAP Runtime
System v2.0
ABAP System
Schema
Customer
Data
SAP
Content 2.0
ABAP System
Schema
- temporary -
Problem Statements
• Downtime: System Conversion migrates customer data
• PROBLEM: To include customer data migration in online phase of upgrade, customer
tables/data in shadow system required (formerly, plain ABAP basis was enough)
• SOLUTION APPROACH: include set of customer tables in shadow system creation (online
phase)
• Memory: Start of temporary Shadow System requires memory
• PROBLEM: Sufficient free main memory for 2nd System in HANA required
• SOLUTION APPROACH: smart views with shadow columns
• DB Migration to HANA: Source System might be on any DB
• PROBLEM: HANA Migration needs to be part of the conversion process
• SOLUTION: Use Database Migration Option (DMO) of SUM
• Data Migration: Data needs to be migrated to new structures
• PROBLEM: Data type and content transformation needs to be done
• SOLUTION APPROACH:
• Push execution to HANA for maximum performance.
• Move to “uptime” using shadow column / shadow system approaches
Customer
Data
Original System Shadow System

SAP BW/4HANA is the Innovation Code Line
Time
Innovation/Features
Initial SAP BW
release
First SAP BW
release on
SAP HANA
SAP
BW/4HANA
release
SAP BW on Any DB
SAP BW/4HANA
2012 20161998
SAP BW
powered by
SAP HANA

SAP BW/4HANA – Differences
SAP HANA or AnyDB
SAP BW
SAP NetWeaver
SAP HANA
SAP BW
SAP NetWeaver
SAP HANA
BW
• Built on SAP NetWeaver
• Supports classic objects and
HANA-optimized objects
• Supports AnyDB and SAP HANA
• Built on SAP NetWeaver
• Supports HANA-optimized objects
• Classic objects are disabled
• Supports SAP HANA only
SAP BW/4HANA
AS ABAP
• Based on lean ABAP application server
• Supports only HANA-optimized objects
• Built for and available only for SAP HANA
SAP BW
powered by SAP HANA
SAP BW,
edition for SAP HANA
SAP BW/4HANA
Disabled

SAP BW and SAP BW/4HANA Releases
SAP BW on any database
 SAP BW + Any supported database platform (other than SAP HANA)
SAP BW powered by SAP HANA
 SAP BW 7.3 or higher + SAP HANA
SAP BW, edition for SAP HANA
 SAP BW 7.5 SP 4 or higher + SAP BW/4HANA Starter Add-on + SAP HANA
SAP BW/4HANA
 SAP BW/4HANA 1.0 + SAP HANA 1.0 SPS 12 or higher

SAP BW History – Continuous Innovation
BW 1.2 BW 7.0
#ObjectTypes
BW 7.3
10
BW 7.5BW 7.4BW 3.x
15
20
25
InfoObject
InfoCube
InfoPackage
Update Rule
Transfer Rule
MultiProvider
Query
InfoSpoke
ODS Object (DSO)
InfoSet
VirtualProvider
APD
OpenHub Destination
Transformation
Data Transfer Process
TransientProvider
CompositeProvider
HybridProvider
Semantic Part. Obj.
Data Flow
DataStore Object (advanced)
(New) CompositeProvider
Open ODS View
HANA Analysis Process
+
+
+
+
30

SAP BW powered by SAP HANA – Simplified but Compatible
BW 1.2 BW 7.0
#ObjectTypes
BW 7.3
10
BW 7.5BW 7.4BW 3.x
15
20
25
InfoObject
InfoCube
InfoPackage
Update Rule
Transfer Rule
MultiProvider
Query
InfoSpoke
ODS Object (DSO)
InfoSet
VirtualProvider
APD
OpenHub Destination
Transformation
TransientProvider
CompositeProvider
HybridProvider
Semantic Part. Obj.
Data Flow
Open ODS View
+
+
+
+
30
Recommended Object Types

SAP BW/4HANA Today – Completely Simplified
BW 1.2 BW 7.0
#ObjectTypes
BW 7.3
10
BW 7.5BW 7.4BW 3.x
15
20
25
InfoObject
InfoCube
InfoPackage
Update Rule
Transfer Rule
MultiProvider
Query
InfoSpoke
ODS Object (DSO)
InfoSet
VirtualProvider
APD
OpenHub Destination
Transformation
TransientProvider
CompositeProvider
HybridProvider
Semantic Part. Obj.
Data Flow
Open ODS View
+
+
+
+
30
BW/4HANA 1.0
Simplified Object Types

SAP BW/4HANA - Removed Legacy Functionality
SAP BW SAP BW/4HANA
BEx Analyzer, BEx Web Templates, BEx Tools
BW Query (BEx Query Designer)
Classic Object Types (InfoCube, DSO, MultiProvider, InfoSet, …)
SAPGUI Modeling & Workbench
Source System types DB Connect, Extractor (S-API), BW
Source System types UD Connect, Data Services, Partner ETL
BI Content Packages
PSA / InfoPackages
Easy Query
Analysis Process Designer
Virtual InfoProvider
Near-line Storage Partner Solutions
SAP BusinessObjects Cloud & Enterprise Clients & Tools
BW Query (BW Modeling Tools Query Designer)
New Object Model: DataStore Object (adv.) & CompositeProvider
HANA Studio based BW Modelling Tools
Consolidation to new HANA Source System & ODP
Consolidation to new HANA Source System
New HANA-optimized SAP BW/4HANA Content Packages
Operational Delta Queue, field-based DataStore Object (adv.)
OData Query
HANA Analysis Process, new Data Flow
HANA Calculation Views, Open ODS View
New HANA-based Data Temperature Management
with SAP IQ & Hadoop
Tool-Based
Manual
Semi-Automated

SAP BW/4HANA – Path 1
New Implementation
Scenario Description
• New installation of SAP BW/4HANA e.g. for customers converting from a legacy system or
• Build a system from scratch, with a new data model and load only relevant data from source
systems
• For customers, who want a fresh start, we are planning to offer an option to transport certain
objects from the existing SAP BW system to a newly installed SAP BW/4HANA system
Benefits for Customers
• Re-engineering and process simplification based on modern data warehouse architecture
• Eliminate old data and shrink system size
• Reap full benefits of SAP HANA platform
Target Group
• SAP Business Warehouse customers or net new customers

SAP BW/4HANA
New Implementation
SAP BW/4HANA Modeling Tools
SAP BusinessObjects Suite or Cloud
SAP HANA
SAP BW/4HANA
SAP BW
or
Any Customer Legacy System
Any Database
Installation & Transport of Objects
Data Load & Quality Check
* See appendix
SA SAP
or non-SAP
Data Warehouse
SA
or
What
• Install SAP BW/4HANA, selective transport of BW objects (optional *), implement HANA-optimized data
models and flows, followed by data load and quality checks
How
• Software Provisioning Manager (SWPM), system connection (SAP source), SAP BW/4HANA ETL, file
upload and/or SAP HANA EIM (legacy sources)

SAP BW/4HANA
New Implementation - SAP First Guidedance for SAP BW/4HANA
SAP BW/4HANA
 SAP BW 7.5 SP 5 is almost equal with
SAP BW/4HANA 1.0 SP 1 based on
SAP Basis Apps (no SAP NetWeaver
Stack)
 Only HANA-optimized code, leaner SP
stack overall
 No Java stack required
 SAP BW/4HANA modelling
environment built to run on SAP HANA
 All new SAP BW 7.5 developments on
SAP HANA can be used without
changes
 Conversion to SAP BW/4HANA via
SPAM/SAINT instead of SUM

SAP BW/4HANA – Path 2
System Conversion
• Customers who want to change their current SAP BW system into a SAP
BW/4HANA system *
• Tool support for database, release, and application transition
• Options for in-place conversion (keep SID) or remote conversion (new SID) **
• Conversion without reimplementation
• No disruption for existing business processes
• Re-evaluation of customization and existing data models and flows
Target Group
• SAP Business Warehouse customers
* For multiple systems, see Path 3
** Planned

SAP
BW/4HANA
Next Steps:
SAP BW/4HANA Transfer Toolbox *
 Full system conversion of an existing SAP BW
installation (keep same SID)
 Step-by-step in-place transfer of classic objects into
their HANA-optimized counterparts
 Followed by a system conversion to
SAP BW/4HANA
 Minimum start release:
SAP BW 7.5 SP 5 powered by SAP HANA
 Start with SAP BW/4HANA as green field installation
(new SID)
 Support of carve-out and consolidation scenarios
 Transport data models and remote data transfer
(including Unicode conversion)
 Risk mitigation due to parallel system
 Minimum start release:
SAP BW 7.0 or higher on AnyDB
In-Place
Conversion
Remote
Conversion
SAP BW
SAP BW
SAP
BW/4HANA
* Availability Planned for Q2/2017

In-place Conversion
Path to Convert Your System
 All SAP BW customers can start NOW
 Customers on SAP BW powered by SAP HANA have a head-start
 Customers can convert at their own pace – benefiting gradually from HANA-optimizations
Step 1: Classic
DB migration and
upgrade to latest
SAP BW release
using DMO
Step 2: Implement
add-on, use
transfer tools to
make system
BW/4HANA-ready
Step 3:
System
conversion
SAP BW
on any DB
SAP BW
on SAP HANA
SAP BW 7.5
on SAP HANA
+ SAP BW/4HANA
Starter Add-On
SAP BW/4HANA

SAP BW/4HANA
In-place Conversion
SAP HANA 1.0 or 2.0
SAP BW/4HANA 1.0
Release Upgrade, Install Add-on,
System Conversion
Pre-Checks, Transfer Toolbox,
Custom Code Adjustments
What
• Migrate and/or upgrade to SAP BW 7.5 powered by SAP HANA (if necessary), install SAP BW/4HANA
Starter Add-on, transfer data models and data using transfer toolbox, adjust custom code, check
prerequisites and perform system conversion
How
• SAP BW/4HANA Transfer Toolbox, Custom Code Analysis, SPAM/SAINT
Any UI
Any Database / SAP HANA
SAP BW / SAP BW powered by SAP HANA
SA SAP
Business
Warehouse
SA
or *
* Move from on premise to cloud is not part of the conversion process

Simplification List for
SAP BW/4HANA
SAP Readiness Check *
System
Requirements
Discover / Prepare Phase Explore / Realize / Deploy Phase
t2
Maintenance
Planner
Pre-
Checks
Custom Code
Check
In-place
Conversion
t1 t3 t4
System
Conversion
SPAM/SPAINT
Post Conversion
Tasks
t5 t6 t7
SAP BW powered by SAP HANA SAP BW/4HANADowntime
Transfer
Toolbox
Custom Code
Adjustments
t8
* Planned
Go-Live
In-place Conversion
Basic Sequence
Starter
Add-on

In-Place Conversion
SAP BW/4HANA Starter Add-On
SAP BW/4HANA Starter Add-on (f.k.a. “SAP BW, edition for SAP HANA”) is prerequisite for In-Place
Conversions. After the installation, the system can be set to the following modes:
 Unsupported object
types cannot be created
 Existing scenarios can
continue running as
before
 Unsupported objects can
be changed when adding
them to a white list
 No imports of
unsupported object
types
 White list is not relevant
any more
 System is ready for
conversion
Compatibility
Mode
B4H
Mode
Ready-For-
Conversion
BW
Mode
 System works like
regular SAP BW system
without restrictions

SAP BW/4HANA
Remote Conversion
SAP HANA 1.0 or 2.0
SAP BW/4HANA 1.0
Installation of SAP BW/4HANA,
Transport of Custom Developments
Pre-Checks, Transfer Toolbox,
Custom Code Adjustments
What
• Install SAP BW/4HANA, transfer data models and data using transfer toolbox, and transport custom
developments (might need adjustments to work with SAP BW/4HANA).
How
• Software Provisioning Manager (SWPM), SAP BW/4HANA Transfer Toolbox
Any UI
Any Database
SAP BW 7.x
SA SAP
Business
Warehouse
SA
or
* Move from on premise to cloud is not part of the conversion process
*

Simplification List for
SAP BW/4HANA
SAP Readiness Check *
System
Requirements
Discover / Prepare Phase Explore / Realize / Deploy Phase
t2
Maintenance
Planner
Pre-
Checks
Custom Code
Check
System
Provisioning
t1 t3 t4
Remote
Conversion
Post Conversion
Tasks
t5 t6 t7
SAP BW on Any Database
SAP BW/4HANA
Installation
t8
* Planned
Go-Live
Remote Conversion
Basic Sequence
Transfer
Toolbox
Custom Code
Adjustments

Path 3: Landscape Transformation

SAP BW/4HANA – Path 3 *
Landscape Transformation
• Customers who want to consolidate their SAP BW landscape (multiple production systems)
or carve out selected data models or flows into a global SAP BW/4HANA system
• Customer-specific conversion project re-using standard tools (planned service offering from
SAP’s Data Management & Landscape Transformation group)
• Stay with current data warehouse landscape and move gradually to SAP BW/4HANA
innovations
• Harmonized data models and shared master data through consolidation
• Carve out of single entities of the company to SAP BW/4HANA and leverage process
simplification
Target Group
• SAP customers with multiple SAP BW, or SAP BW on SAP HANA systems, or hybrid cases
* Planned

SAP BW/4HANA
Landscape Transformation
SAP HANA 1.0 or 2.0
SAP BW/4HANA 1.0Installation & Data Transfer
What
• Install SAP BW/4HANA, implement consolidated and HANA-optimized data models and flows, followed
by data load and quality checks
How
• Selective Data Transfer, SAP Landscape Transformation (SLT), SAP Data Services, SAP BW/4HANA
ETL or SAP HANA EIM
Any UI
Any Database
SAP BW 7.x
SA
SAP
Business
Warehouse
Any UI
Any Database
SAP BW 7.x
SA
SAP
Business
Warehouse
…
SA
or

SAP BW/4HANA
Which Path is Right for You?
Starting Point
Path 1
New Install
Path 2 *
System Conversion
Path 3*
Landscape
TransformationIn-place Remote
One or more legacy systems    
SAP BW on any database    
SAP BW powered by SAP HANA    
SAP BW 7.5 powered by SAP HANA
w/ SAP BW/4HANA Starter Add-on
   
Multiple SAP BW systems    
Legend:
 Highly recommended path
 Recommended path
 Possible alternative path
 Not supported * Planned

Blogs about Transitioning to SAP BW/4HANA
The Road to SAP BW/4HANA – Part 1 & 2
https://blogs.saphana.com/2016/09/07/the-road-to-sap-bw4hana-part-1/
https://blogs.saphana.com/2016/09/18/the-road-to-sap-bw4hana-part-2/
On the Road to SAP BW/4HANA – Part 1 & 2
https://blogs.sap.com/2016/12/15/on-the-road-to-bw4hana-first-stage-accomplished/
https://blogs.sap.com/2016/12/15/on-the-road-to-bw4hana-second-stage-ahad/

SAP BW/4HANA
Further Information

More Information about SAP BW4/HANA
SAP BW/4HANA Landing Page
http://sap.com/bw4hana
SAP BW/4HANA Community / Product Page
http://sap.com/bw4hana10
SAP BW/4HANA Documentation
http://help.sap.com/bw4hana10
SAP BW/4HANA FAQ
http://go.sap.com/documents/2016/08/c4458a08-877c-0010-82c7-eda71af511fa.html
SAP First Guidance – SAP BW/4HANA complete functional scope (CFS)
http://www.sap.com/documents/2016/09/b001a9de-8a7c-0010-82c7-eda71af511fa.html
Why #BW/4HANA?
http://scn.sap.com/community/bw-hana/blog/2016/09/05/why-bw4hana
Replay of the SAP BW/4HANA Launch Event
http://events.sap.com/sap-amazon-web-services/en/home

SAP BW/4HANA in a Nutshell
Open Online Course
English
Training for SAP BW4/HANA
 4 Units – 2-3 hours in total
 No prerequisites
 Free participation & certification
For details, go to openSAP
DBW4H – Data Warehousing with
SAP BW/4HANA - Delta from SAP
BW powered by SAP HANA to SAP
BW/4HANA
Classroom or Virtual Live Classroom
German (English coming soon!)
BW462
SAP BW/4HANA
BW462 – SAP BW/4HANA
Classroom or Virtual Live Classroom
German (English coming soon!)
training@SAPtraining@SAP
 5 days
 Prerequisites:
 Hands-on experience in data modeling with SAP BW 7.x
 BW310 (SAP BW Enterprise Data Warehousing non-HANA)
For details, go to SAP Training
openSAP
 2 days
 Prerequisites:
 SAP BW 7.4 / 7.5 and SAP HANA 1.0 knowledge is necessary
 DBW74, BW362, HA100 or HA100e, BW310H
For details, go to SAP Training

BREAK

Mission Critical DC Operation – What’s New in HANA 2.0?
Agenda
Backup & Recovery Backend Functionality (Contact: Stephanie
Lewellen)
 Optimized workload of Backint-based log backups (strong customer demand)
 Recover single db (class. setup) backup to tenant database
 Option to write the backup catalog to a separate location
Scale-Out, High Availability (Host Auto-Failover)
 Extension Node with different size restrictions for SAP BW/4HANA
(very detailed description on SCN)
 During installation worker groups for extension node classes can be defined
Disaster Recovery & High Availability
 SAP HANA System Replication Active/Active Read-Enabled
SAP HANA Dynamic Tiering (contact: Courtney Claussen)
 Co-Deployment of SAP HANA and DT on a single host
 Delta Backups for dynamic tiering
 Basic HANA System Replication for dynamic tiering
 Data volume encryption for dynamic tiering
 Multi-store tables
DataCenter Infrastructure – Minimal releases for HANA 2.0
 SUSE SLES 12 SP1, RedHat RHEL 7.2
 SAP HANA SPS10 minimal start release for upgrade
DataCenter Infrastructure – IBM Power (Contact: Paul Henter)
 SUSE SLES 12 with move to Little Endian (After migration easy exchange with other
Little-Endian infrastructure)
 New Certification for Backint tools for IBM Power Little Endian (LE) flavor
 NFS support
Deployment Options
Multi-Tenant Database Containers (Contact: Joerg Hoffmeister)
 Optimized copy/move for trusted environments (no need for certificates)
 SQL commands for kill/restart tenants
Virtualization, HW Partitioning (Contact: Jan Teichmann)
 Ongoing extension of options: After SingleVMs are released with vSphere 6.0 also
MultiVMs and Scale-Out with VMs are in preparation
SAP HANA Security & Persistence (Contact: Andrea Kristen)
 Redo log encryption for SAP HANA
Smart Data Streaming (Contact: Jeff Wootton)
 Enhanced HANA MDC support
SAP Landscape Management (LaMa) 3.0 (Contact: Adarsh S Kapoor)
 Now supporting SAP HANA with automatic orchestration for more complex HSR
processes like shadow updates (nZDM), switch-back re-enablement of replaced boxes
etc.

What’s New in SAP HANA 2.0: Backup & Recovery
Overview
Backup & Recovery Backend Functionality (contact: Stephanie Lewellen)
 Optimized workload of Backint-based log backups (strong customer demand)
 Recover single db (class. setup) backup to tenant database
 Option to write the backup catalog to a separate location
SAP HANA
Database
3rd Party
Backup
Server
3rd Party
Backup
Agent
hdbsql
SAP HANA
studio
Create backup
Log Area
Log
Volume
Log Volume
Log
Segment
Data Area
Data
Volume

What’s New in SAP HANA 2.0: Backup
Optimization for 3rd party backup tools
Optimized workload of Backint-based log backups (strong
customer demand)
 With a well operated SAP HANA system a lot of log backups are created
 Numbers above 2000 backup files per day are not rare
 External backups tools can have problems with digesting so many files
SAP HANA uses several options to reduce the number of
created backup files
 By checking if several services have to write backups at the same time
and collect these files into one package
 Results in one backup activity instead of several before
 Alternatively, for older SAP HANA releases the log segment size can be
increased to 4 gigabytes (max.) per segment
SAP HANA
Database
3rd Party
Backup
Server
3rd Party
Backup
Agent
hdbsql
SAP HANA
studio
Create backup
Log Area
Log
Volume
Log Volume
Log
Segment
Data Area
Data
Volume

SAP HANA Backup and Recovery
Backint-certified tools as of 2016.11.
Certification is an installation prerequisite for tools using the “Backint for SAP HANA” API
 See SAP Note 1730932 (Using backup tools with Backint)
Online listing of certified tools: Application Development Partner Directory
 Enter the search term HANA-BRINT and click on a partner name  ”SAP Certified Solutions” for further details
Vendor Backup tool Intel Arch. POWER Arch. BE
HANA 1.0
POWER Arch. LE
HANA 2.0
Support process
(SAP Notes)
Allen Systems ASG-Time Navigator 4.4  2212571
Commvault Simpana 10.0;
Hitachi Data Protection Suite 10.0


1957450, 2345177
Commvault 11.0;
Hitachi Data Protection Suite 11.0


EMC NetWorker 8.2;
Interface for Data Domain Boost 1.0


1999166, 1970559
HP Data Protector 7.0, 8.1, 9.0;
StoreOnce Plug-in for SAP HANA 1.0


1970558
IBM Tivoli Storage Manager for Enterprise 6.4 
1913500
Spectrum Protect for Enterprise Resource Planning 7.1 
Libelle BusinessShadow 6.0.6  2212575
Mindtree NBU CONNECTOR for SAP HANA 1.0  2330945
SEP SEP Sesam 4.4   2024234
Veritas (Symantec) NetBackup 7.7  1913568
New
New
New

What’s New in SAP HANA 2.0: Recovery
Direct recovery of class. backups into Multi-Tenant Database Containers
Recover single db (class. setup) backup to tenant database
To move easier from a classical setup to Multi-Tenant Database
Containers, SAP HANA now offers to use backups from “classical
setup” for a direct recovery into MDC
 No time consuming use of a transfer systems:
o Creation of temporary SAP HANA systems in classical setup
o Do a recovery and subsequently transformation to MDC on that
system
o Take another backup for the final transfer into Multi-Tenant Database
Containers target setup
 Simplifies the use of old backups as soon as Multi-Tenant Database
Containers becomes default installation option (planned for HANA 2
SPS01)
AS
ABAP
App 1
System DB
Shared HANA Hardware
DB
Schema
Tenant 1
DB
Schema
Tenant 2
DB
Schema
Tenant N
App N
SAP HANA Instance
SchemaSchema
SAP HANA Instance
App
HW
OS
Database
App
Recovery
class. Setup
backup
Classical Setup
Multi-tenant
Database
Containers

Scale-Out & Host Auto-Failover

What’s New in SAP HANA 2.0: Scale-Out & Host Auto-Failover
Overview
Scale-Out, High Availability (Host Auto-Failover)
 Extension Node with different size restrictions for SAP BW
(very detailed description on SCN)
 During installation worker groups for extension node classes
can be defined
Data & Logs
BW/4HANA
Data Archives
Archiving
HANA
Failover
Node
for local
HA
HANA
Node
HANA
Failover
Node
for local
HA
persistent
oper
persis-
tent
oper-
ration
persis-
tent
oper-
ration
persis-
tent
oper-
ration
Compute
Node
Compute
Node
Compute
Node
HANA
Node
persistent
oper
Extension
Node
Extension
Node
Extension
Node
Scale-Out with
asymmetric Setup

Disaster Recovery & High
Availability

What’s New in SAP HANA 2.0: Disaster Recovery & HA
Overview
Disaster Recovery & High Availability
 SAP HANA System Replication Active/Active Read-Enabled
 Concept Demo: https://aasimsdcbihana.hana.ondemand.com/activeactive.html

SAP HANA System Replication
Active/Active operation mode planned for SAP HANA
Feature description
General
 Active/Active is based on continuous log replay
feature and inherits its features of
o fast take-overs,
o reduced need for bandwidth in continuous
operation and
o existing replication modes (SYNC, SYNCMEM,
ASYNC, and full_sync option) etc.
 A/A, like Continuous Log Replay, always offers
integrated consistent, but possibly delayed views of
data on Secondary
o Secondary knows the exact delay (statement
snapshot isolation)
 In case of an outage, all functions will concentrate on
secondary system
 sizing of Secondary is important for the right
performance in disaster scenarios
Secondary
 Allows read (r/e – read enabled) access (SQL and
admin), if Secondary runs same SAP HANA software
version (different software will simply cancel r/e until
same software again – no setup changes necessary)
 No write access with redo-log creation
 Internal processes for operations like ColumnStore delta
merges are also happening on Secondary
 Like with Continuous Log Replay, redo log replay runs
as an asynchronous process on Secondary  consider
latency for business
 XS classic engine service port remains closed until
take-over
 XS advanced supported as every other SQL client
 Export of tables is possible with CSV as target.
 New operation mode logreplay_readaccess
 Secondary gets his own virtual IP address representing
the secondary function
 Load balancing e.g. based on delay situation
Restrictions for first release
 Management for new connections stays in Primary until
possible take-over
 Existing connection can continue on Secondary until
take-over allows new connections again.
 Not yet A/A support for production in Tier-3 of multi-tier
SAP HANA System Replication, planned to follow later
 Not yet Scale-Out and Dynamic Tiering
 Not yet binary exports on Secondary
 Columnar store and system tables available for read
access, Row store tables give an error on Secondary
Primary
HANA
Secondary
HANA
HANA Client Library
r/er/w
Log
Application
Log
SYNC
SYNCMEM
ASYNC
ASYNC

SAP HANA Active/Active read-enabled
Feature description
General
 Active/Active is based on continuous log replay feature and inherits its features of
o fast take-overs,
o reduced need for bandwidth in continuous operation and
o existing replication modes (SYNC, with and without full_sync option, SYNCMEM, ASYNC)
 Active/Active, like Continuous Log Replay, always offers integrated consistent, but possibly delayed views
of data on Secondary
o Secondary knows the exact delay (statement snapshot isolation)
o Redo log replay runs as an asynchronous process on Secondary  consider latency for business
processes
o HANA can support here  Load balancing e.g. based on delay situation
o SQL and administration access to Secondary
 In case of an outage, all functions will concentrate on secondary system
 Sizing of Secondary is important for the right performance in disaster scenarios
 Secondary is strongly recommended to have the same resources or more as Primary offers
 Single host and Scale-Out setups supported
 Supports setup with same kind of processors on Primary and Secondary both either Intel-based or Power-
based with the same byte order (Little Endian or Big Endian)
o Underlying technology SAP HANA System Replication can offer more combinations as long as byte
order is the same
Primary
HANA
Secondary
HANA
HANA Client Library
r/er/w
Log
Application
Log
SYNC
SYNCMEM
ASYNC
ASYNC
Concept Demo

SAP HANA Active/Active read-enabled Secondary
Secondary
 Allows read (r/e – read enabled) access (SQL and administration)
o Secondary runs same SAP HANA software version
o Different software will simply cancel r/e until same software again – no setup changes necessary
 No write access with redo-log creation
o No DDL, no DML or Access Control on Secondary
o Internal processes for operations, like ColumnStore delta merges are also happening on
Secondary – not redo log relevant
 Stored procedures, views and session-local temporary tables
o Created and exist on Primary, replicated to Secondary
o Can also be executed on Secondary as long as read operation
 XS classic engine service port remains closed until take-over
 XS advanced supported as every other SQL client
 Export of tables is possible with CSV as target.
 New operation mode logreplay_readaccess
 Secondary gets his own virtual IP address representing the secondary function
 Memory for r/e queries on Secondary limited to 50%
o Log Replay needs right resources as a back-bone technology
 Table verify (structure check) can be executed on Secondary
Primary
HANA
Secondary
HANA
HANA Client Library
r/er/w
Log
Application
Log
 Views, Stored
Procedures
 Exports e.g.
CSV, extracts
 Table structure
check

SAP HANA Active/Active read-enabled - Restrictions
Restrictions for first release
 Management for new connections stays in Primary until possible take-over
o Existing connection can continue on Secondary until take-over executed
o Finished take-overs allow new connections again
o Existing connections need an (automatic) reconnect and can be promoted to
read and write access
 Not yet A/A support for Tier-3 of multi-tier SAP HANA System Replication,
planned to follow
o But a Tier-3 can be connected with continuous log replay to an A/A setup of
Tier-1 and Tier-2
 Not yet Dynamic Tiering (planned)
 Not yet binary exports on Secondary
 Columnar store and system tables available for read access on Secondary
o Row store table accesses still give an error on Secondary
Primary
HANA
Secondary
HANA
HANA Client Library
r/er/w
Log
Application
Log
 Connection
Management
 Exports CSV,
Binary
 CS & RS
 Table structure
check
 Exports CSV
 CS r/e

SAP HANA Active/Active read-enabled – Access modes
Two connection types:
Explicit
 Used via secondary connection to Secondary,
 BI tools like Dashboards can use Secondary
Implicit
 Hint based SQL statement routing
 Adaption of S/4 HANA ongoing (140 Apps already transformed in 1610)
 Custom developments can easily reshaped
Hint based SQL statement routing
SQL Statement contains hint that it may be executed on secondary
 No routing in case statement is part of write TA,
 No routing of stored procedures (due to session context issues)
 Optional delay-driven routing if demanded by application
Primary
HANA
Secondary
HANA
HANA Client Library
r/er/w
Log
Application using secondary connect
Primary
HANA
Secondary
HANA
HANA Client Library
r/er/w
Log
Application, SQL Hint enabled
Explicit
Implicit

Paradigm shift where analytics can support business applications

Concept Demo
Concept Demo

SAP on Linux the way to S/4HANA

Recommended

Recommended

More Related Content

What's hot

What's hot (16)

Similar to SAP on Linux the way to S/4HANA

Similar to SAP on Linux the way to S/4HANA (20)

More from Finceptum Oy

More from Finceptum Oy (20)

Recently uploaded

Recently uploaded (20)

SAP on Linux the way to S/4HANA