32
© 2011 SAP AG. All rights reserved. 2
SAP HANA - Naming Summary
SAP HANA appliance SAP HANA database
Application Name, powered by SAP HANA
SAP in-memory computing
Appliance Database
Applications
SAP HANA studio
Studio
Category
SAP HANA application
cloud
Cloud
© 2011 SAP AG. All rights reserved. 3
Disclaimer
This presentation outlines our general product direction and should not be relied on in making a
purchase decision. This presentation is not subject to your license agreement or any other agreement
with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to
develop or release any functionality mentioned in this presentation. This presentation and SAP's
strategy and possible future developments are subject to change and may be changed by SAP at any
time for any reason without notice. This document is provided without a warranty of any kind, either
express or implied, including but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this
document, except if such damages were caused by SAP intentionally or grossly negligent.
© 2011 SAP AG. All rights reserved. 4
Agenda
Introduction
What is SAP HANA
– Appliance
– Software
Data Acquisition
Replication using Trigger, Log, or ETL
SAP HANA Scale Out
SAP HANA Certified Hardware
Backup & Recovery
Demo
© 2011 SAP AG. All rights reserved. 5
SAP HANA - Implications of being an Appliance
Classic software delivery
on-premise solutions
SAP ships only the software
Customer is responsible for entire product lifecycle
Appliance delivery
kind of “SaaS on-site customer”
SAP defines the solution together with it partners
SAP & Partners handle product lifecycle
Ap
plia
nce
Op
era
tion
Co
nce
pts
Infrastructure *
Operation *
Setup / Consulting
Support (Software, Maintenance and
Infrastructure)
SAP Development Software and Licenses
HW- and Technology
Partners
SAP Hosting and Cloud
Delivery
Infrastructure
Operation
Setup/ Consulting
Support (Software, Maintenance and
Infrastructure)
SAP Development Software and Licenses
* Might be outsourced or owned by customerSAP responsibility
Customer’s
responsibility
Partners'
responsibility
© 2011 SAP AG. All rights reserved. 6
The SAP HANA appliance software from an installation point of view:
Enablement for factory pre-installation & on-site configuration
SAP HANA Installation
Following the SAP appliance delivery model
– The HW vendor provides factory pre-installation for HW, OS and SAP software
– The HW vendor may add specific best-practices and SAP HANA software configuration
– The HW vendor finalize installation by an on-site setup and configuration of the HANA components*
– Customer starts with establishment of replication / connectivity to data source systems and BI clients**
HW delivered
to customer
HANA System
set up
HANA Scenario
runs
factory pre-install on-site serviceon-site setup
HW & OS assemblySAP SW
installationFactory
Smoke testOn-sitesetup
Technical configuration
On-site smoke test
Setup Replication
Business Configuration
* Includes deployment of SAP HANA system in customer data center, connectivity to network, SAP system rename, Solution Manager and SAP Router connectivity, SSL Support
** Includes deployment of additional replication components e.g. on source system and/or BI client components like BOE and Explorer
© 2011 SAP AG. All rights reserved. 7
Data Sources Admin Workstations • SAP HANA studio• SAP HANA database clients • Data Services Designer • Information Designer • MS Excel 2010• Web access to BI admin tools
End users Workstations • MS Excel 2010• SAP HANA database clients 1.0• Web access to BI clients (1577128)
SAP HANA appliance (SLES 11 SP1)
• SAP HANA database, - clients, studio• SAP HANA Load Controller • SAP Host Agent 7.20 • Sybase Replication Server 15.5 + ECDA
Data Services
• Data Services 4.0• Data Services Job Server• Repository (shared with BOE)
BI4.0
• BI Platform• Explorer• WebApp server• Repository
SAP ERP System•• SAP ERP • SAP Host Agent 7.20• Sybase Replication Agent (HP UNIX, SLES, AIX)
SAP BW System
Non – SAP System
SAP HANA System Landscape
LT System•• NW7.02• Add-on DMIS 2010_1_700
© 2011 SAP AG. All rights reserved. 8
SAP
Host Agent
Sybase
Replication Server
SAP HANA
Studio
SAP HANA appliance software
SAP HANA
Load Controller
SAP HANA Component Architecture
SAP HANA 1.0 SPS 02
– SAP HANA database
– SAP HANA database clients
– SAP HANA studio (P2 repository)
– Sybase Replication Server
– SAP HANA Load Controller
– SAP Host Agent
– LM Structure files
– SAPCAR
– Operating system configuration
SL Toolset 1.0 SPS 02
– Software Update Manager
for SAP HANA
– SAP JVM
LM Structure filesSAP HANA
Database clients
SAPCARSAP HANA
Database
SLES 11 SP1
Server Management Tools (HW vendor specific)
Storage Subsystem
SAP SW Update
Manager (SUM)
for SAP HANA
SL Toolset 1.0
SAP JVM
The SAP HANA appliance software from an deployment point of view:
A well defined and validated stack of HW and SW components
© 2011 SAP AG. All rights reserved. 9
Port Numbers
Service Port SQL Port
Daemon 3xx00
Nameserver 3xx01
preprocessor 3xx02
indexserver 3xx03 3xx15
scriptserver 3xx04
statisticsserver 3xx05 3xx17
appserver 3xx07, 3xx08
remotesupportdaemon 3xx09
R 3xx19, 3xx20
The xx represents the System Number
© 2011 SAP AG. All rights reserved. 10
SAP HANA Operations Recommendations
For performance and security:
•Single server SAP HANA instances -> data files on SSA disk
• Recommended mount point /hana/data
•Distributed SAP HANA instances -> data files on shared storage
• Recommended mount point /hana/data
•SAP HANA database log files on SSD disk
• Recommended mount point /hana/log
Configure SAP Support connection (SAP Note 1058533)
Consider dedicated private network to data acquisition systems
Ensure that the SAP HANA database, client, and server are the same revision level
Demo
© 2011 SAP AG. All rights reserved. 12
Agenda
Introduction
What is SAP HANA
– Appliance
– Software
Data Acquisition
Replication using Trigger, Log, or ETL
SAP HANA Scale Out
SAP HANA Certified Hardware
Backup & Recovery
Demo
© 2011 SAP AG. All rights reserved. 13
SAP HANA Replication Technologies
© 2011 SAP AG. All rights reserved. 14
Supported Capability MatrixSee SAP Note 1513496 for up-to-date official release limitations
Capability Log File Replication SLT Replication (trigger) Data Services 4.0 (ETL)
Tab
les
Minimum ERP Version ECC 6.0 ERP 4.6c ERP 4.6c
Unicode/Non-Unicode Unicode Only Yes Yes
MDMP No Yes Yes
Transparent Tables Yes Yes Yes
Cluster & Pool Tables No Yes Yes
Non-SAP ERP Sources Yes No Yes
Compressed Values DB Table DB2 (9.1, 9.5, 9.7) Yes Yes
Row Compression DB Table DB2 9.7 only (no support for 9.1 or 9.5) Yes Yes
SAP ERP DB Support DB2 LUW/UDB Only* All DBs supported under ERP All DBs supported under ERP
SAP ERP OS SupportAIX, HP-UNIX, SUSE LINUX 10 & SUSE Linux 11, SPARC/Solaris, (see PAM
for version details)All OS supported under ERP All OS supported under ERP
Multi-Source Support Single Source System Multiple Source Systems Multiple Source Systems
Extr
acto
rs
Minimum ERP Version
N/A N/A
See SAP Note:1558737
Unicode/Non-Unicode Yes
MDMP Partial (Not recommended)
Transparent Tables N/A
Cluster & Pool Tables N/A
Non-SAP ERP Sources N/A
SAP ERP DB Support All DBs supported under ERP
SAP ERP OS Support All OS supported under ERP
Multi-Source Support Multiple Source Systems
© 2011 SAP AG. All rights reserved. 15
LT Replication Concept: Trigger-Based Approach
Architecture and Key Building Blocks
SAP HANA systemLT Replication Server
Application Tables
Source system
Write Modules
Controler
Modules
DB
Connection
RFC
Connection
Read
Modules
Logging
Tables
Application Tables
Efficient initialization of data
replication based on DB trigger
and delta logging concept
(as with NearZero downtime approach)
Flexible and reliable replication process,
incl. data migration
(as used for TDMS and SAP LT)
Fast data replication via DB connect
LT replication functionality is fully
integrated with HANA Modeler UI
LT replication server does not have to be a separate SAP system and can run on any SAP system with SAP NetWeaver
7.02 ABAP stack (Kernel 7.20EXT)
DB Trigger
© 2011 SAP AG. All rights reserved. 16
Technical Requirements and System Set-Up Information for LT
Replication Server
SAP HANA systemLT Replication ServerSource system
System Requirements:
-SAP Basis: Netweaver 702, with Kernel 7.20EXT
(64BIT Unicode) PL90
DB
Connection
RFC
Connection
System Requirements:
- SAP Basis 4.6C and higher
- All supported SAP ERP databases
Installation:
- respective DMIS 2010 version
- Minimum support pack level: latest available
Installation:
- Addon DMIS 2010_1_700
- Minimum support pack level: SP04
(released with HANA SPS02, consider
instructions of SAP Note 1602938)
Installation:
- HANA SPS02 or later: includes LT replication
functionality fully integrated into the UI of
the HANA modelerBasic Configuration:
- Define RFC connection to source system
- Define DB connection to HANA system
- Define max. number of jobs to be used
for data replication
Basic Configuration:
- Optional: define separate table space
for logging tables
- Define RFC user with appropriate authorization
Basic Configuration:
- Create a DB user (if required)
LT replication server can run on any SAP system with SAP NetWeaver 7.02 ABAP stack (using SAP Kernel 7.20EXT), for example on Solution Manager 7.1 or the source system
– it does not have to be a separate SAP system!
© 2011 SAP AG. All rights reserved. 17
Agenda
Introduction
What is SAP HANA
– Appliance
– Software
Data Acquisition
Replication using Trigger, Log, or ETL
SAP HANA Scale Out
SAP HANA Certified Hardware
Backup & Recovery
Demo
© 2011 SAP AG. All rights reserved. 18© SAP 2007 /
Page 18
High Availability Features
Scenarios
One data center fails (due to fire, power outage, earthquake, etc.)
One node fails (hardware failure)
Concept
Redundant data center (including redundant HANA system) – Hot Standby
Synchronous mirroring
Standby system within one NewDB landscape – Cold Standby
Failover is triggered automatically
© 2011 SAP AG. All rights reserved. 19© SAP 2007 /
Page 19
Disaster Tolerance
Redundant Hardware
2 independent landscapes
Data Center 1 Data Center 2
Source System Source System
SAP HANA SAP HANA
Storage System
Node 4
Node 1
Node 2
Node 3
Node 4
Node 1
Node 2
Storage System
Node 3
Switch
over
Mirroring
Mirroring
PROXY
© 2011 SAP AG. All rights reserved. 20
Distributed system
Multiple nodes utilizing shared filer for workload distribution
© 2011 SAP AG. All rights reserved. 21
What to check for distributed installation?
Adding a node using hdbaddhost:
• A system has been installed with its server software on a sapmnt shared file system (export options rw,
no_root_squash).
• This system is running.
• You are logged on to the new host as the root user.
• You have mounted the current host to the shared file system.
• Consistent user environment (uid, gid, system number).
• In an SAP system, the requirements for host names of SAP servers are met (SAP Note 611361)
Recommendation: Synchronize time between all HANA nodes and related components (e.g. NTP)
© 2011 SAP AG. All rights reserved. 22
Agenda
Introduction
What is SAP HANA
– Appliance
– Software
Data Acquisition
Replication using Trigger, Log, or ETL
SAP HANA Scale Out
SAP HANA Certified Hardware
Backup & Recovery
Demo
© 2011 SAP AG. All rights reserved. 23
Certified Hardware
Check http://service.sap.com/pam for latest
© 2011 SAP AG. All rights reserved. 24
Certified Hardware
Check http://service.sap.com/pam for latest
SAP HANA Sizing Information -> SAP Note https://service.sap.com/sap/support/notes/1514966
© 2011 SAP AG. All rights reserved. 25
Agenda
Introduction
What is SAP HANA
– Appliance
– Software
Data Acquisition
Replication using Trigger, Log, or ETL
SAP HANA Scale Out
SAP HANA Certified Hardware
Backup & Recovery
Demo
© 2011 SAP AG. All rights reserved. 26
In-memory computing is secure
The SAP HANA database holds the bulk of its data in memory for maximum performance, but still uses
persistent storage to provide a fallback in case of failure. The log is capturing all changes by database
transactions
Data and log are automatically saved to disk at regular savepoints, the log is also saved to disk after each
COMMIT of a database transaction
After a power failure, the database can be restarted like a disk-based database:
System is normally restarted („lazy“ reloading of tables to keep the restart time short)
System returns to its last consistent state (by replaying the log since the last savepoint)
Time
Data savepoint
to persistent storage
1 Log written
to persistent storage
(committed transactions)
2
Power failure
3
SAP HANA Backup and Recovery
© 2011 SAP AG. All rights reserved. 27
Recovery scenarios
There is an option for clearing the log during recovery. With this option, older data backups can be
restored (without running into problems with a gap between the older data backup and the log that is
still available in the system).
SAP HANA Backup and Recovery
Supported in SAP HANA GA, SPS02
Recovery to last data backup
Recovery to older data backup *
Recovery to last state before crash ()**
Point-in-time recovery
*requires clearing of the log during recovery **limited, requires undamaged log
© 2011 SAP AG. All rights reserved. 28
SAP HANA Operations Recommendations
Backup and Restore recommendations:
Perform a full backup after initial load
Never delete database log files on the filesystem
Perform a regular data backup to allow logs to be overwritten
Estimate backup size to avoid ‘disk full’ before executing the backup
Review available recovery options as documented in the ‘Backup and Recovery Guide’
Demo
© 2011 SAP AG. All rights reserved. 30
Further Information
SAP Public Web:
Service Market Place: http://service.sap.com/hana
SAP Help: http://help.sap.com/hana
SAP Developer Network (SDN): http://www.sdn.sap.com/irj/sdn/in-memory
Related SAP Education and Certification Opportunities
http://www.sap.com/education/ - classroom course TZHANA
SAP Teched – http://www.sapteched.com in Las Vegas, Bangalore, Madrid and Beijing
Upcoming SAP HANA related know-how callsAugust 24 – Replicating data into the SAP HANA database using SAP LT Replication Server
Addendum
