Uwe Heinz Product Management (SAP LinuxLab) - SUSE · PDF fileSAP HANA Appliance vs. Tailored...
Transcript of Uwe Heinz Product Management (SAP LinuxLab) - SUSE · PDF fileSAP HANA Appliance vs. Tailored...
© 2013 SAP AG. All rights reserved. 1
SAP HANA on SUSE Linux Enterprise ServerOperating, Maintaining and Optimizing
Uwe HeinzProduct Management (SAP LinuxLab)
© 2013 SAP AG. All rights reserved. 2
Disclaimer
This presentation outlines our general product direction and should not be relied onin making a purchase decision. This presentation is not subject to your licenseagreement or any other agreement with SAP.
SAP has no obligation to pursue any course of business outlined in thispresentation or to develop or release any functionality mentioned in thispresentation. This presentation and SAP's strategy and possible futuredevelopments are subject to change and may be changed by SAP at any time forany 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 aparticular purpose, or non-infringement. SAP assumes no responsibility for errors oromissions in this document, except if such damages were caused by SAPintentionally or grossly negligent.
© 2013 SAP AG. All rights reserved. 3
SAP HANA on SLES:Agenda
Introduction & Overview (SAP and LINUX)
SAP HANA on SLES (Platform & Appliance methodology )
Deployment
High Availability (SAP and HA certification and outlook)
Backup & Recovery (System Copy)
Monitoring & Administration
© 2013 SAP AG. All rights reserved. 4
SAP HANA on SLES:Agenda
Introduction & Overview (SAP and LINUX)
SAP HANA on SLES (Platform & Appliance methodology )
Deployment
High Availability (SAP and HA certification and outlook)
Backup & Recovery (System Copy)
Monitoring & Administration
© 2013 SAP AG. All rights reserved. 5
Introduction & Overview (SAP and LINUX)
Foundationof Linuxlab
SAPNetweaver
Linuxdevelpomentplattform
SAP BWA
SAP HANA
1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013
CeBit99
and growing ...
SAP supports only : SLES, RHEL and Oracle Linux
© 2013 SAP AG. All rights reserved. 6
Introduction & Overview (SAP and LINUX)Open Standards (support of multiple solutions)
HA solutions•SUSE HA•RH Cluster•Veritas•Steeleye•HP Service Guard
Database•SAP HANA•Sybase ASE15 / IQ•SAP MaxDB•Oracle RDBMS• IBM DB2 LUW
OS/Distributions•SUSE Linux Enterprise Server (SLES)•Red Hat Enterprise Linux ( RHEL )•Oracle Linux (OL)
Hardware• Intel / AMD X86_64•Linux on IBM Power•Linux on IBM System z
© 2013 SAP AG. All rights reserved. 7
SAP Solutions on Linux - Trends
Reasons for deploying Linux:
- Cost Reduction
- High availability
- Performance improvement
- Low training efforts (Unix-> Linux)
0102030405060708090
costreduction
HA Perf Training other* Source RAAD
© 2013 SAP AG. All rights reserved. 8
SAP Solutions on Linux - Trends
1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013
LinuxQA and Dev
Linux ApplServer
Linux DBServer
Today >15000 DB
installationson LinuxToday > x APP
installations onLinux
Today Linux isfavoured target forSAP OS Migrations
20000 andmore
Reliability,stability virtualization
LCM/LVM
HA and DR
© 2013 SAP AG. All rights reserved. 9
Linux Benchmarks
Windows:
12930 SD UserReferenz *2013018
Linux:
12735 SD UserReferenz *2013017
Same HW4 socket
Linux:
23250 SD UserReferenz *2013014
8 socketServer
© 2013 SAP AG. All rights reserved. 10
SAP rely on Linux
Speed
Scale
FlexibilityFlexibility
SpeedSpeed
Scale
Flexibility
http://youtu.be/qB3Z6PLGHgY http://youtu.be/oLbHMpYkKUUhttp://youtu.be/HQbaKSVezx8
Major new SAP development projects like HANA or BWA happen on LinuxSAP‘s own ERP system runs on HANA (SUSE SLES)Linux is Reference Platform for SAP software development
© 2013 SAP AG. All rights reserved. 11
SAP HANA on SLES:Agenda
Introduction & Overview (SAP and LINUX)
SAP HANA on SLES (Platform & Appliance methodology )
Deployment
High Availability (SAP and HA certification and outlook)
Backup & Recovery (System Copy)
Monitoring & Administration
© 2013 SAP AG. All rights reserved. 12
SAP HANA on SLES (Platform & Appliance methodology )
1998 LiveCache
2000TREX
2005PTime
2006BWA
2006KickoffHANA
2010HANARTC
© 2013 SAP AG. All rights reserved. 13
SAP HANA Platform
SAP HANA Technology Partners
SAP HANA Product Flavors
SAP HANA Enterprise Edition
SAP HANA Platform Edition
- incl data provisioning (SLT)
SAP HANA for BW/Suite- BW/Suite database only
SAP HANA Hardware Partners
© 2013 SAP AG. All rights reserved. 14
SAP HANA scalabilityScales from very small servers to very large clusters
Single Server• 2 CPU 128GB to 8 CPU 1TB
(Special layout for Suite on HANAfor up to 4 TB per host)
• Single SAP HANA deployments fordata marts or accelerators
• Support for high availabilityand disaster recovery
Scale Out Cluster• 2 to n servers per cluster
• Each server is either 4 CPU/512GB or 8CPU/1TB
• Largest certified configuration: 56 servers
• Largest tested configuration: 100+servers
• Support for high availabilityand disaster recovery
Cloud Deployment• SAP HANA instances can be
deployed to AWS
• Limited to developer license
• SAP HANA Enterprise Cloud
© 2013 SAP AG. All rights reserved. 15
SAP HANA on SLES:Agenda
Introduction & Overview (SAP and LINUX)
SAP HANA on SLES (Platform & Appliance methodology )
Deployment
High Availability (SAP and HA certification and outlook)
Backup & Recovery (System Copy)
Monitoring & Administration
© 2013 SAP AG. All rights reserved. 16
SAP HANA – Variety of deployment options
In the CloudHANA developer editionfree of chargeSAP HANA One / HANA one premiumpay per useSAP HANA Enterprise Cloud24/7 mission critical / Enterprise Support
In the Data CenterBare metal single Serverpre-configured & validated stackScale-Out / HA & DR clusterscalable from single node to Geo clusterVirtualized with VMwareVMware vSphere 5.1 or newer
© 2013 SAP AG. All rights reserved. 17
SAP HANA - Implications of being an Appliance
Classic software deliveryon-premise solutions
SAP ships only the softwareCustomer is responsible for entire product lifecycle
Appliance deliverykind of “SaaS on-site customer”
SAP defines the solution together with its partnersSAP & partners control product lifecycle
ApplianceO
perationC
oncepts
Infrastructure *
Operation *
Setup / Consulting
Support(Software, Maintenance andInfrastructure)
SAP Development Software and Licenses
HW- and TechnologyPartnersInfrastructure
Operation
Setup/ Consulting
Support(Software, Maintenance andInfrastructure)
SAP Development Software and Licenses
* Might be outsourced or owned by customerSAP responsibilityCustomer’sresponsibility
Partners'responsibility
© 2013 SAP AG. All rights reserved. 18
(onlyChina)
XS: 128GB X X X X X X X
S: 256GB X X X X X X X
S+: 256GB X X X X X X
M: 512GB X X X X X X X X X
M+: 512GB X X X X
L: 1.0TB X X X X X X
Scale Out (BW) X X X X X X X planned
SoH: 1/2/4TB 1/2/4 1/2/4 2/4 1 1 1/2/4 2
HighAvailability X X X X X X X planned
DR – StorageRepl.: Async
DR – StorageRepl.: Sync X X X X X
Certified HANA Hardware – June 2013*
* For most up to date list please go to the SAP Product Availability Matrix
© 2013 SAP AG. All rights reserved. 19
SAP HANA Tailored Data Center IntegrationCustomer Feedback & Challenges and alternative Concept
SAP HANA tailored data center integration is an additional option to theexisting appliance model
HANAServer
HANAServer
Storage
HANAServer
HANAServer
HANAServer
(Corp.)Storage
HANAServer
Reduce hardware and operationcost at installed based customersMitigate risk and optimize time tovalue by taking more responsibilityGain additional flexibility inhardware vendor selection *
Limited flexibility in server/ storagecombinations (well defined packages)Established IT operation processeshave to be adapted slightlyWell defined HW and performanceKPIs
* Please contact for joining pilot phase: [email protected]
© 2013 SAP AG. All rights reserved. 20
SAP HANA Appliance vs. Tailored Data Center IntegrationDifferentiating Capabilities
More Flexibility & Responsibility
• Additional efforts throughverification test
• Preferred combinations ofserver and storage possible
• Installation and validationneeds to be done bycustomer
• HANA installation certificationnecessary
• Customer ensures support forall stack components
Save IT budget and existing investmentsSupport fully provided by SAP
HANAServer
HANAServer
(Corp.)Storage
HANAServer
Fast Implementation
• Solution validation doneby SAP and Partner
• Preconfigured hardwareset-up
• Defined performance &KPIs out of the box
• Preinstalled software
HANAServer
HANAServer
Storage
HANAServer
© 2013 SAP AG. All rights reserved. 21
SAP HANA SP Stack UpdateProcess Description
SAP HANA appliance software
SAP HANA database & clientSAP HANA studio repositorySAP HANA load controller
SAP HostAgent
SUM for SAPHANA
SAP HANA studio(Eclipse)
LMperspective
Maintenance Optimizer
Service Marketplace
All remote connections are done via secure web services.
1. Perform Software Update Manager for SAP HANA self-update2. Detect components in the SAP HANA landscape3. Get latest SP stack information from SAP Service Marketplace (SMP)4. Download required component updates5. Update components on the SAP HANA system
InternetLocal patch
directory
© 2013 SAP AG. All rights reserved. 22
Fulfilling IT compliance (IT policies) for Data Centers
Data Center compliances usually define specific topics toManaging, Monitoring and Backup & Restore toolsCentral user management with IDM toolsAnti Virus software usage mandatesOS security patches, firewallsEtc.
Additional 3rd party tools required to complete thesecompliances are tolerated with following restrictions
Neither SAP nor hardware vendor offers support for tools which arenot official part of the SAP HANA BOM.The hardware vendor is tolerating the installation and operation ofthis compliance-related software.Customers might be asked to stop these tools in case of a supportissue and to enable reproduction of the problem
HW Partner
Customer
Tool Vendor
SAP
HW Partner Tool set
© 2013 SAP AG. All rights reserved. 23
Technical Operational Manual for SAP HANA
SAP offers a technical operational manual (TOM) with all kinds of topics aboutoperating SAP HANA as an appliance (http://help.sap.com/hana_appliance).
This manual should be taken as input for further adaptations of the operation ofSAP HANA in customers’ Data Centers.
The needed regular duties aroundthe operation of SAP HANA can bederived from this document.
Usually HANA needs lesser administrationthan other databases, typical duties are:
Regular backups (Database, Bare-Metalsoftware and configuration backup)Patches; usually on demand in case ofproblems or known issues (DB, OS)Monitoring (automated or manual)
Task Responsible
SAP HANA appliance installation Hardware Partner
Hardware Hardware Partner
OS installation Hardware Partner
OS updates Customer
SAP HANA updates Customer
Data source connectivity Customer
BI Client installation Customer
SAP HANA software support SAP
Table: Cited from SAP HANA TOM
© 2013 SAP AG. All rights reserved. 24
Cloud & Virtualization
SAP HANA in the CloudSAP HANA Developer Editiono For product evaluations, trials, students, data exploration projects, etc.o Software is free, developers pay cloud provider for server usage.o Community supported through http://saphana.com/cloudo Available of choice on 4 public cloud providers
SAP HANA Oneo Non-productive and productive usageo Option 1 - with community support according SAP Note 1798212o Option 2 - with full SAP support through OSS as part of
SAP HANA One premium licenseo Available of choice on 4 public cloud providers
SAP HANA – Virtualization On PremiseNon productive usageRestrictionso Vendors (Note 1788665 - SAP HANA running on VMware vSphere VMs)o Maximum HANA performance is only reached on “bare metal” (non-virtualized)o VMWare Vmotion (hot move) is not supported
© 2013 SAP AG. All rights reserved. 25
SAP HANA Cloud Offerings Today
Private Cloud Public Cloud
HANA Hosting Developer Edition HANA ONE
Korea Telecom
Savvis
Portugal Telecom
Telstra
Amazon Web Services
VirtuStream
Cloudshare
IBM
HP
VMware
© 2013 SAP AG. All rights reserved. 26
SAP HANA on SLES:Agenda
Introduction & Overview (SAP and LINUX)
SAP HANA on SLES (Platform & Appliance methodology )
Deployment
High Availability (SAP and HA certification and outlook)
Backup & Recovery (System Copy)
Monitoring & Administration
© 2013 SAP AG. All rights reserved. 27
High Availability – Disaster Recovery
High AvailabilityBusiness function fail over between two or more physical frames within the same data center using a single shared
storage location.Elimination of single points of failure (SPOF's) are a necessary part of HA.The goal is to minimize downtime for business functions, not computer systems.
This is NOT non-stop computing, downtime will be experienced during fail over.
Disaster RecoveryBusiness function recovery between geographically separated data centers using a storage replication system between
the data centers.The output of disaster recovery planning is a disaster recovery project plan.The goal is to minimize downtime for business functions, not systems.Business function recovery times and maximum allowable data loss is specified during the business impact analysis.
BC
HA
DR
© 2013 SAP AG. All rights reserved. 28
High Availability – Disaster Recovery
Business Continuity
High Availability
per Data Center
Disaster recovery
between Data Centers
SAP HANA Host Auto-Failover(Scale-Out with Standby)
SAP HANA System Replication
SAP HANA Storage Replication
SAP HANA System Replication
© 2013 SAP AG. All rights reserved. 29
SAP HANA Architecture
SAP HANA Appliance
Software Update Manager
SAP Host Agent
SAP HANA Studio Repository
SAP HANA Database Node 2 Node n
…Name Server
Index Server
Statistics Server
Preprocessor
Index Server
Preprocessor
Index Server
Preprocessor
Single host configuration
Multi-node cluster configuration
Maintains landscape information
Holds data and executes all operations
Collects performance data about HANA
Text analysis pre-processor
Repository for HANA Studio updates
Enables remote start/stop
Manages SW updates for HANA
Shared storage for fail-over and recovery
SAP Host Agent SAP Host Agent
Name Server Name Server
XS engine XS engine XS engineXS engine
© 2013 SAP AG. All rights reserved. 30
Scale OutHigh Availability
High Availability configuration• N active servers in one cluster• M standby server(s) in one cluster• Shared file system for all servers
Services• Name and index server on all nodes• Statistics server (only on one active server)• Name server active on Standby
Failover• Server X fails• Server N+1 reads indexes from shared storageand connects to logical connection of server X
Server 1
Server 2
Server 3
Server 4
Server 5
Server 6
Standby Server
Shar
edSt
orag
e
© 2013 SAP AG. All rights reserved. 31
In-Memory
SAP HANA Database Landscape
Persistence Layer
LOGDISK
DATADISK
LOGDISK
DATADISK
LOGDISK
DATADISK
LOGDISK
DATADISK
LOGDISK
DATADISK
*Standby Host:
Name Server (active)
Index Server (standby)
Distributed HANAdatabase even on asingle host with sharednothing concept
Standby without ownpersistence
© 2013 SAP AG. All rights reserved. 32
HANA High AvailabilityHost Auto-Failover (standby)
Different implementation of High Availability by HW partners
Using storage solution inside Using internal disk
NameServer
IndexServer
StandbyNameServerIndexServer
NameServer
IndexServer
DataDisks
LogDisks
DataDisks
LogDisks
DataDisks
LogDisks
GPFS
GPFS
© 2013 SAP AG. All rights reserved. 33
HANA High AvailabilityVideo to present functionality of Auto Host Failover
Video: https://www.saphana.com/videos/1417
© 2013 SAP AG. All rights reserved. 34
SAP HANA High AvailabilityMinimal Setup for Host Auto-Failover
Minimal setup for a Host Auto-Failover(Scale-Out):
2 Servers including one Standby
External storage or similar technologynecessary which ensures the data provisioningto second node via external data location
This setup aims for High Availability notperformance scaling or size.
Note:Some use cases (e.g. SAP BW powered byHANA) might have different requirementsor recommendations for minimal setups(e.g. BW has a defined setup for SAP HANAScale-Out – SAP note 1637145 attachedPDF).
MasterNameServer
IndexServer
DataDisks
LogDisks
active standby
IndexServer
NameServer
© 2013 SAP AG. All rights reserved. 35
SAP HANA High AvailabilityClient Management with Scale-Out
Clients:During installation the clients get initial information about how tocontact to HANA database – often only one host is offeredTo prevent single point of failure, more host should be offered incase of Scale-OutThe list is only necessary to establish a first connect to HANA cluster– afterwards the client gets the full topology from the databaseName Server anywayThe complete list of hostnames including the standby host should bestored
User store:Contains the list of host names like “hana1;hana2;hana3” etc. nextto user and encrypted password informationAll tools based on this database interface named sqdbc (SAP Appl.Server, hdbsql, ODBC, python, etc.) can use this user store.
Algorithm:Round robin process is used to find this first contact point
SQL clients:SAP Appl. Server
hdbsql
User Storehana1;hana2;hana3
round robinhana1 hana2 hana3
HANA Scale-Out
DataDisks
LogDisks
hana1NameServer
Indexserver
hana2NameServer
Indexserver
hana3standby
NameServer
Indexserver
© 2013 SAP AG. All rights reserved. 36
High Availability – Disaster Recovery
© 2013 SAP AG. All rights reserved. 37
Data Center 1
System ReplicationAsynchronous Data and Synchronous Redo Log Shipping
Data Center 2
Clients
Primary(Online)
NameServer
Indexserver
NameServer
Indexserver
NameServer
Indexserver
Secondary
NameServer
Indexserver
NameServer
Indexserver
NameServer
Indexserver
Load and rebuildmain indexes as
loaded in primary
Incremental datareplication
based on HANAsnapshots
Synchronous mirroredredo log writing
DataVolumes
LogVolume
DataVolumes
LogVolume
DataVolumes
LogVolume
DataVolumes
LogVolume
© 2013 SAP AG. All rights reserved. 38
HANA System Replication versus Disk Replication
Pro:No I/O latency issue for data writing, less data transportationRedo-Log write latency only at EOT time, non-EOT log writing is asynchronousFaster availability after takeovero Load main tables in memory during standby modeo Data transported via incremental backup is already in memory
No dependency on hardware solutions / VMsHigh flexibilityLower license costs
Contra:Higher hardware costs: servers in secondary data center cannot be used for test/QA-systems when using the table preload featureNo HANA integrated full automatic failoverNo consistency groups with other related systems (e.g. ERP)Doesn’t replicate binaries, config (so far) and trace files
© 2013 SAP AG. All rights reserved. 39
Setup (Example Locations: Walldorf – Rot)Configuration Steps
Walldorf
Primary
NameServer
Indexserver
NameServer
Indexserver
NameServer
Indexserver
DataVolumes
LogVolume
DataVolumes
LogVolume
Rot
Secondary
NameServer
Indexserver
NameServer
Indexserver
NameServer
Indexserver
DataVolumes
LogVolume
DataVolumes
LogVolume
Start with two system on different hostsSID, system-number and host topology are equalSecondary additionally uses port range (system-number + 1)
Stop secondary, primary stays onlinePrimary: hdbnsutil -sr_enable --name=WALLDORFSecondary: hdbnsutil -sr_register --remoteHost=<walldorf_host>
--remoteInstance=50--mode=syncmem --name=ROT
Secondary: Start system
Synchronous mirroredredo log writing
Complete datareplication
© 2013 SAP AG. All rights reserved. 40
Walldorf Rot
Clients
Primary(Online)
NameServer
Indexserver
NameServer
Indexserver
NameServer
Indexserver
Secondary
NameServer
Indexserver
NameServer
Indexserver
NameServer
Indexserver
Backup primary data,transport and restore
into secondaryData
VolumesLog
VolumeData
VolumesLog
VolumeData
VolumesLog
VolumeData
VolumesLog
Volume
Store Info aboutcurrently loaded
main tablesLoad and rebuildmain indexes as
loaded in primary
Synchronous mirroredredo log writing
Use virtual hostnames,etc.
SetupTransport Complete Data Backup and Load Columns into Memory
© 2013 SAP AG. All rights reserved. 41
Walldorf
SetupPeriodic Transport of Incremental Backup
Rot
Clients
Primary(Online)
NameServer
Indexserver
NameServer
Indexserver
NameServer
Indexserver
Secondary
NameServer
Indexserver
NameServer
Indexserver
NameServer
Indexserver
Load and rebuildmain indexes as
loaded in primary
Asynchronoustransport of
incremental databackup.
Check loaded andunloaded main tables
DataVolumes
LogVolume
DataVolumes
LogVolume
DataVolumes
LogVolume
DataVolumes
LogVolume
Store Info aboutcurrently loaded
main tables
Synchronous mirroredredo log writing
© 2013 SAP AG. All rights reserved. 42
Check ConfigurationHANA Studio
© 2013 SAP AG. All rights reserved. 43
Check ConfigurationSystem View
PUBLIC.M_SERVICE_REPLICATIONCOLUMN_NAME COMMENTSHOST Host namePORT Internal portVOLUME_ID Volume IDSITE_ID Generated site IDSITE_NAME Logical site nameSECONDARY_HOST Secondary Host NameSECONDARY_PORT Secondary PortSECONDARY_SITE_ID Generated ID of secondary siteSECONDARY_SITE_NAME Secondary logical site nameSECONDARY_ACTIVE_STATUS Secondary Active StatusSECONDARY_CONNECT_TIME Time the connection was established from the secondarySECONDARY_RECONNECT_COUNT Secondary Reconnect CountSECONDARY_FAILOVER_COUNT Secondary Failover CountREPLICATION_MODE Replication ModeREPLICATION_STATUS Replication StatusREPLICATION_STATUS_DETAILS Replication Status DetailsLAST_LOG_POSITION Current Log PosLAST_LOG_POSITION_TIME Current Log Pos TimestampLAST_SAVEPOINT_VERSION Current Savepoint VersionLAST_SAVEPOINT_LOG_POSITION Current Savepoint Log PositionLAST_SAVEPOINT_START_TIME Current Savepoint TimestampSHIPPED_LOG_POSITION Shipped Log PositonSHIPPED_LOG_POSITION_TIME Shipped Log Position TimestampSHIPPED_LOG_BUFFERS_COUNT Shipped Log Buffers CountSHIPPED_LOG_BUFFERS_SIZE Shipped Log Buffers Size in BytesSHIPPED_LOG_BUFFERS_DURATION Shipped Log Buffer Duration in microsecondsSHIPPED_SAVEPOINT_VERSION Shipped Savepoint VersionSHIPPED_SAVEPOINT_LOG_POSITION Shipped Savepoint Log PositionSHIPPED_SAVEPOINT_START_TIME Shipped Savepoint Start TimeSHIPPED_FULL_REPLICA_COUNT Shipped Full Replica CountSHIPPED_FULL_REPLICA_SIZE Shipped Full Replica Size in BytesSHIPPED_FULL_REPLICA_DURATION Shipped Full Replica Duration in microsecondsSHIPPED_LAST_FULL_REPLICA_SIZE Shipped Last Full Replica Size in BytesSHIPPED_LAST_FULL_REPLICA_START_TIME Shipped Last Full Replica Start TimeSHIPPED_LAST_FULL_REPLICA_END_TIME Shipped Last Full Replica End TimeSHIPPED_DELTA_REPLICA_COUNT Shipped Delta Replica CountSHIPPED_DELTA_REPLICA_SIZE Shipped Delta Replica Size in BytesSHIPPED_DELTA_REPLICA_DURATION Shipped Delta Replica Duration in microsecondsSHIPPED_LAST_DELTA_REPLICA_SIZE Shipped Last Delta Replica Size in BytesSHIPPED_LAST_DELTA_REPLICA_START_TIME Shipped Last Delta Replica Start TimeSHIPPED_LAST_DELTA_REPLICA_END_TIME Shipped Last Delta Replica End Time
© 2013 SAP AG. All rights reserved. 44
Check ConfigurationManagement Console
hdbcons –e hdbindexserver “replication info”walldorf:HA1:ha1adm /usr/sap/HA1/HDB50 53>hdbcons -e hdbindexserver "replication info"
Executable: hdbindexserver (PID: 17602)
[OK]
--
Dumping replication statistics ...
Replication Primary Information
===============================
System Replication Primary Configuration
[system_replication] preload_column_tables = true
[system_replication] logshipping_timeout = 30
- lastLogPos : 17957627520
- lastLogPosTimestamp : 03.10.2012-12.31.27 (1349267487672283)
- lastSavepointVersion : 2331
- lastSavepointLogPos : 17953754050
- lastSavepointTimestamp : 03.10.2012-12.28.32 (1349267312948713)
1 session registered.
Session index 0
- SiteID : 2
- RemoteAddress : 10.21.68.20/35103_tcp
…
© 2013 SAP AG. All rights reserved. 45
Restart
Restart of PrimarySecondary reconnects automatically if it was connected after restart
Restart of SecondarySecondary reconnects automatically if primary is online
Primary sends incremental data backupRedo log history can get lost in secondary !(Future releases will ship missing redo log if possible)
Walldorf
Primary
NameServer
Indexserver
NameServer
Indexserver
NameServer
Indexserver
DataVolumes
LogVolume
DataVolumes
LogVolume
Rot
Secondary
NameServer
Indexserver
NameServer
Indexserver
NameServer
Indexserver
DataVolumes
LogVolume
DataVolumes
LogVolume
Synchronous mirroredredo log writing
Ship incremental databackup
© 2013 SAP AG. All rights reserved. 46
Log Shipping Timeout
PrimaryStops log shipping when waiting longer than logshipping_timeout (default 30seconds)
SecondaryTries to reconnect in intervals defined by reconnect_time_interval (default 30seconds)
Primary sends incremental data backup after reconnectRedo log history can get lost in secondary !(Future releases will ship missing redo log if possible)
Walldorf
Primary
NameServer
Indexserver
NameServer
Indexserver
NameServer
Indexserver
DataVolumes
LogVolume
DataVolumes
LogVolume
Rot
Secondary
NameServer
Indexserver
NameServer
Indexserver
NameServer
Indexserver
DataVolumes
LogVolume
DataVolumes
LogVolume
Synchronous mirroredredo log writing
© 2013 SAP AG. All rights reserved. 47
Takeover
Send Takeover to secondaryhdbnsutil -sr_takeover
Secondary goes online, main columns as used in the primary are loadedRuntime of takeover mainly depends on the size of the row store
Walldorf
Primary
NameServer
Indexserver
NameServer
Indexserver
NameServer
Indexserver
DataVolumes
LogVolume
DataVolumes
LogVolume
Rot
Primary
NameServer
Indexserver
NameServer
Indexserver
NameServer
Indexserver
DataVolumes
LogVolume
DataVolumes
LogVolume
_
ClientsSwitch virtual hostnames,
etc.
© 2013 SAP AG. All rights reserved. 48
Takeover II
Secondary Takeover stepsOpen data persistence based on last savepointLoad Row StoreReplay Redo LogRebuild Row Store Indexes
Load of Column Store Table when Secondary is OnlineRead delta log from diskReplay delta log
Verify System Stateld8454:HDB:ha1adm> python $DIR_INSTANCE/exe/python_support/landscapeHostConfiguration.py| Host | Host | Host | Failover| Remove| Storage | Failover | Failover | NameServer | NameServer | IndexServer | IndexServer |
| | Active | Status| Status | Status| Partition | Config Group| Actual Group| Config Role| Actual Role | Config Role | Actual Role |
| ------ | ------ | ------| --------| ------| --------- | ------------| ------------| -----------| ----------- | ----------- | ----------- |
| ld8454 | yes | ok | | | 1 | default | default | master 1 | master | worker | master |
| ld8453 | yes | ok | | | 2 | default | default | master 2 | slave | worker | slave |
overall host status: ok
© 2013 SAP AG. All rights reserved. 49
Failback
Activate Previous Primary as secondary when DC is backRegister Walldorf as secondaryWalldorf: hdbnsutil -sr_register --remoteHost=<rot_host> --remoteInstance=50
--mode=syncmem –name=WALLDORFPrimary sends a complete data backup
Redo log history can get lost in secondary !(Future releases will ship missing redo log or an incremental backup if bothsystems were not online in parallel)
Walldorf
Secondary
NameServer
Indexserver
NameServer
Indexserver
NameServer
Indexserver
DataVolumes
LogVolume
DataVolumes
LogVolume
Rot
Primary
NameServer
Indexserver
NameServer
Indexserver
NameServer
Indexserver
DataVolumes
LogVolume
DataVolumes
LogVolume
Synchronous mirroredredo log writing
Ship complete databackup
© 2013 SAP AG. All rights reserved. 50
OperationsAlerts
Log Shipping Timeouts Generate Alerts
© 2013 SAP AG. All rights reserved. 51
OperationsMail Notification
Use “Check for internal event” for mail notification
© 2013 SAP AG. All rights reserved. 52
Backup & Recovery
BackupData backups and redo log archives are still neededPrimary and secondary should access to the same (shared) or replicated backuplocation adjust your backup file description or backup parameters
Walldorf
Primary
NameServer
Indexserver
NameServer
Indexserver
NameServer
Indexserver
DataVolumes
LogVolume
DataVolumes
LogVolume
Rot
Secondary
NameServer
Indexserver
NameServer
Indexserver
NameServer
Indexserver
DataVolumes
LogVolume
DataVolumes
LogVolume
Synchronous mirroredredo log writing
Ship incremental data
© 2013 SAP AG. All rights reserved. 53
OperationsLicense
License ValidityPrimary replicates relevant license information to secondaryNo additional license need to be installed if primary and secondary have thesame SID
Walldorf
Primary
NameServer
Indexserver
NameServer
Indexserver
NameServer
Indexserver
DataVolumes
LogVolume
DataVolumes
LogVolume
Rot
Secondary
NameServer
Indexserver
NameServer
Indexserver
NameServer
Indexserver
DataVolumes
LogVolume
DataVolumes
LogVolume
Synchronous mirroredredo log writing
Ship incremental data
© 2013 SAP AG. All rights reserved. 54
UpgradeThe secondary system can run with a higher version than the primary
Upgrade ProcedureThe secondary system can run with a higher version than the primary
Upgrade secondary system withhdbupd --import_content=off
As a result the secondary runs in system replication mode.Upgrade primary system as usual
Near Zero Downtime Upgrade with upgrading the secondary first, performing a takeover andupgrading the previous primary as secondary is planned for future releases.
Walldorf
Primary
NameServer
Indexserver
NameServer
Indexserver
NameServer
Indexserver
DataVolumes
LogVolume
DataVolumes
LogVolume
Rot
Secondary
NameServer
Indexserver
NameServer
Indexserver
NameServer
Indexserver
DataVolumes
LogVolume
DataVolumes
LogVolume
© 2013 SAP AG. All rights reserved. 55
SAP HANA on SLES:Agenda
Introduction & Overview (SAP and LINUX)
SAP HANA on SLES (Platform & Appliance methodology )
Deployment
High Availability (SAP and HA certification and outlook)
Backup & Recovery (System Copy)
Monitoring & Administration
© 2013 SAP AG. All rights reserved. 56
HANA
SAP HANA Persistence:In-Memory Data Is Regularly Saved to Disk
Data:SQL data and undo log informationAdditional HANA information,such as modeling dataKept in-memory to ensure maximumperformanceWrite process is asynchronously
Log:Information about data changes (redo log)Directly saved to persistent storage whentransaction is committed (synchronous)Cyclical overwrite (only after backup)
Savepoint:Changed data and undo log is written frommemory to persistent storageAutomaticAt least every 5 minutes (customizable)
Memory
Data
Persistent Storage
Regular automaticsavepoints
Information aboutdata changes
LogVolume
DataVolumes
© 2013 SAP AG. All rights reserved. 57
In-Memory
SAP HANA Database Landscape
Persistence Layer
LOGDISK
DATADISK
LOGDISK
DATADISK
LOGDISK
DATADISK
Distributed HANAdatabase even on asingle host with sharednothing concept
© 2013 SAP AG. All rights reserved. 58
In-memory computing is secureThe SAP in-memory database holds the bulk of its data in memory for maximumperformance, but still uses persistent storage to provide a fallback in case of failure. Thelog is capturing all changes by database transactions (redo logs)Data and undo log information (part of data) are automatically saved to disk at regularsavepointsThe log is also saved to disk continuously and synchronously after each COMMIT of adatabase transaction (waiting for end of disk write operation)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 redo log since the last savepoint)
SAP HANA Persistence:Regular Saving of In-Memory Data to Disk, Restart
Savepoint:Data & undo log is written
to disk (data area)
1Continously and after each COMMIT,redo log is written to disk (log area)
2Power failure
3
Time
© 2013 SAP AG. All rights reserved. 59
SAP HANA database Data backupsContain the current payload of the datavolumesAny pages that are changed during the databackup written to different locations in thedata volumes (shadow page concept)Manual (SAP HANA studio, SQLcommands), or scheduled (DBA Cockpit)
Log backupsContain the content of closed log segmentsAutomatic (asynchronous) whenever a logsegment is full or the timeout for log backuphas elapsed
Log Area(disk)
Data Area(disk)
Memory
Savepoint COMMIT
Data Backups Log Backups
SAP HANA Backup and RecoveryMemory Disk Backup
© 2013 SAP AG. All rights reserved. 60
Backup and RecoveryData backups
Data backups save the content of the data area to a different location in the filesystem. Depending on the usage scenario, this includes the replicated businessdata from ERP and all the modeling data.Data backups are carried out manually:
SAP HANA studioDBA CockpitSQL commands (command line)
Scheduling:Using scripts (via the SQL interface)Planning calendar in DBA Cockpit
Backup frequencyRegular data backups required, but no general guidelines available(depends on the usage scenario)
Space requirementsOnly occupied space is backed up
© 2013 SAP AG. All rights reserved. 61
Backup and RecoveryAdvantages for Backups with HANA Kernel involvement
Structural knowledge of data in database kernelMini-verify of every page with relevant information during simple data and log backupHeader and Trailer verification of checksums ensures valid data in pagesHardware problems get soon recognized and can be treated early enough w/o furtherimplications to general data consistencyOS-related or external tools don’t offer this structural knowledge into HANA data types
PerformanceOnly occupied space is backed upThroughput of up to 0.5 or 1 TB per hour and per host (scale-out case) reported in anoptimal situation(There are a lot of ways like bad network throughput, slow NFS storage perf., no hardwareseparation etc. to ruin such a good B&R performance)
Check BackupGeneral possibility to check also backups with data knowledge in kernelFurther functionality planned
© 2013 SAP AG. All rights reserved. 62
SAP HANA Server
SAP HANA Backup/RecoveryData backup: Only payload is backed up
Shared BackupDirectory
(staging area)
Name Server
Data
Index Server
Statistics Server
DATA_BACKUP_0001
DATA_BACKUP_0002
DATA_BACKUP_0003
Data
BackupSavepoint
Data
BackupSavepoint
Data
BackupSavepoint
DATA_BACKUP_0000
© 2013 SAP AG. All rights reserved. 63
Backup and RecoveryBackups during normal operation of the database: Summary
Data backups(external backup
destination)
1Log backups
(external backupdestination)
2Crash
4Most recentlog entries
from log area
3
Time
© 2013 SAP AG. All rights reserved. 64
BackupBackup in SAP HANA Studio
© 2013 SAP AG. All rights reserved. 65
RecoveryRecovery in SAP HANA Studio
© 2013 SAP AG. All rights reserved. 66
Shared Backup Directory
SAP HANA Backup/RecoveryData backup: Single-node and scale-out systems
SAP HANA automatically handles thesynchronization of backups for all nodes
no special user interaction requiredWhat happens internally:
All services with a persistence need to bebacked up (e.g. index servers, mastername server)A global, synchronized backup savepointis written for all these serviceso All transactions are stopped for a brief
momento Kept until the backup is finished for all
servicesData marked in the savepoint is writtenfrom the data volume to a backup fileo One backup file per serviceo Written in parallel -> read from different
disks (depends on appliance configuration)
Backup File
NameServer
IndexServer
Savepoint
NameServer
IndexServer
Savepoint
MasterNameServer
IndexServer
Savepoint
Data written in parallelfrom different nodes
Savepoint
© 2013 SAP AG. All rights reserved. 67
Backup and RecoverySupport for external backup tools
Available today via Backup Staging AreaStaging area management will be optimized by backup tool vendorSAP note 1651055 offers a PDF attachment and scripts about handling the backup staging area
Further integration available with HANA SPS5 and first pilot certification achieved.
Use of operating system pipes to connect directly to external backup tools
New interface standard defined: Backint for HANABackint (in general) is an established standard by SAP and has been continuous extended over timeExtended for pipes for some years (e.g. Backint for MaxDB/liveCache)Further minor extends for the use with SAP HANADescription and simulator already available to start adoption process on external tools now
Contacts to major vendors of external backup tools established, first pilot certification available.
For more information please check SAP note 1730932.
© 2013 SAP AG. All rights reserved. 68
SAP HANA Backup/RecoveryBackup Cockpit in SAP HANA Studio: Configuration
Backint Settings:– If a Backint agent is configured, it is displayed. Vendor-specific parameter files for Backint (optional).Data and Log Backup Settings:– Default settings for data backups (file-based only) and log backups
© 2013 SAP AG. All rights reserved. 69
SAP HANA supportsBackups to the file systemBackups to 3rd party backup tools (via pipes)
Backups to the file system:Use a location that is not on the same disk as the data or log area of the database, e.g. anNFS share
SAP HANA Backup and RecoveryOptions for backups
SAP HANADatabase
BackupStorage
(e.g. NFS)
Backup/recovery
controlled byHANA
© 2013 SAP AG. All rights reserved. 70
SAP HANA Backup/Recovery3rd party backup tool support (I)
Backups to 3rd party backup tools:“Backint for SAP HANA” is an API that can be implemented by a 3rd party backup agentFor both data and log backupsProvides functions for backup, recovery, query, and delete3rd party backup agent runs on HANA server, communicates with 3rd party backup serverBackups are transferred via pipeFull integration with SAP HANA studio (configuration and execution of backups to Backint)
SAP HANADatabase
Backup Server(3rd Party)
Backup/recovery
controlled byHANA
BackupAgent
(3rd Party)
© 2013 SAP AG. All rights reserved. 71
Backup and RecoveryStorage-based offline database copy
1. While the source database is offline, create a filer snapshot of the database and transferthe content of the snapshot to a different location.This leads to two databases with the same name.
2. Restart the source database.3. Change database name and topology (hostname) using the hdbrename utility
(located in /usr/sap/<SID>/SYS/global/hdb/install/bin/)4. The target database is automatically started.
Copy
Storage System
Source Database
offline
Offline filersnapshot
Storage System
Target Database
offline
© 2013 SAP AG. All rights reserved. 72
Storage System
Backup and RecoveryBackup-based online database copy
Available since SAP HANA SPS4SID and hostnames are adapted during the recovery processTarget database is started at the end of the recoveryNo impact on in-memory processing on source; executed on persistence level
Storage System
Source Database
online
Database backup filesOnlineDatabase Backup Database Recovery
Target Database
(copy)
© 2013 SAP AG. All rights reserved. 73
Backup and RecoveryInternal Snapshots in SAP HANA
SAP note: 1703435
Limitation: One internal Snapshot only right nowConflicts with Backup Snapshot which is needed during backup execution time.If an internal snapshot already exists when backup is started, the backup will not beexecuted and an error presented.
Roadmap: multiple named internal Snapshots are planned
© 2013 SAP AG. All rights reserved. 74
Backup and RecoveryNew features for database copies
SAP HANA database copy from PROD to QA or DEV allows now to change thetopology in case of a Scale-out setup on PROD side:
Backups which are produced on scale-out landscapes with n hosts can be recovered toone QA or DEV system.Purpose is to offer a possibility for a light system copy without the full performance scopelike PRODAbility to work on that copy limited by performance and restricted by tables/partition sizes
N 1N M
PROD
QA, DEVor Sandbox
Node 1Index Server n
Index Server 2
Index Server 1
Node nIndex ServerNode 2
Index ServerNode 1Index Server
Database inside changes
© 2013 SAP AG. All rights reserved. 75
SAP HANA Backup & RecoveryNews with SAP HANA SPS6 and Beyond
Backup LiveCycle Management &Security extensions
Option to split large data backupsBackup Catalog in StudioExtended log backup Availability CheckNew system privilege BACKUPOPERATORSecureStoreFileSystem (SSFS)
Recovery Options (n m)Flexible recovery despite different numberof hosts – this feature offers new optionsalso to system copies (Prod QA)
Direct backup content streaming to3rd party backup tools
First official releases; furtherannouncements about possible releasedates for several tool partners
Planned with SAP HANA SPS7 (Endof 2013)
Integration of external Storage Systemsnapshots with Redo Log roll forward ofHANAKeep Backup History with TopologyChangesMore 3rd party backup tools
Planned beyond (2014)Incremental or differential BackupNamed internal Snapshots
© 2013 SAP AG. All rights reserved. 76
SAP HANA on SLES:Agenda
Introduction & Overview (SAP and LINUX)
SAP HANA on SLES (Platform & Appliance methodology )
Deployment
High Availability (SAP and HA certification and outlook)
Backup & Recovery (System Copy)
Monitoring & Administration
© 2013 SAP AG. All rights reserved. 77
SAP Solution Manager can beused for basic administration andholistic monitoring of HANAsystems within existing SAPlandscapes.
It is used by SAP support forearly problem analysis andas backbone for CTS+transport integration.
SAP HANA also integrateswith SAP Landscape andVirtualization Manager (LVM)for basic operation oflarger/more complex SAPlandscapes (start/stop &dependencies, etc.)
LVMSAP
HANAStudio
SAP HANA Administration and MonitoringIntroduction
HANA Studio is oneadministration & monitoringtool for managing SAP HANA
It enables customers to makesure their HANA system runsas expected and providespossibilities to analyzeproblems
It also houses the SAPHANA modeler and the usermanagement for the SAPHANA database
© 2013 SAP AG. All rights reserved. 78
SAP HANA StudioNative Administration & Monitoring Console
NavigatorView
PropertiesView
AdministrationView
© 2013 SAP AG. All rights reserved. 79
SAP HANA as Part of the Customer SolutionProvide a holistic operations concept
Browser GUI Mobile
SAP Solution Manager integrates SAP HANA and SAP HANA Studio
HANAStudio
SAPHANA
BW onHANA
SAPECC
SAPCRM Warehouse
© 2013 SAP AG. All rights reserved. 80
SAP HANA Administration and MonitoringScreenshots
SAP HANA Studio DBA Cockpit in SAP Solution Manager
© 2013 SAP AG. All rights reserved. 81
The Monitoring and Alerting InfrastructureSupports SAP HANA
Thresholdvalue
exceeded!
1. Utilize established SAPSolution Managerfunctions
2. Knowledge Articlesexplain how to handleexceptions
3. Notifications lead toGuided Procedures thatdocument the individualsteps
Daily/weekly/monthly HANADatabase Administration tasksHandling of HANA DatabaseAlerts
4. … and provide access torequired activities
1
3
42
Training on the Job while operating SAP HANA
© 2013 SAP AG. All rights reserved. 82
E2E Root Cause Analysiswith SAP Solution Manager 7.1
End-To-End Workload AnalysisAnalyze workload across components
End-To-End Change AnalysisEnsure compliance with standard configuration
End-To-End Exception AnalysisGet central access to all log information
End-To-End Trace AnalysisInvestigate performance across the full stack
System, Host & Database AnalysisAnalyze capacity needs and trends per technical component
Accelerate time for problem analysis and resolution
© 2013 SAP AG. All rights reserved. 83
SAP HANA Administration and MonitoringFeature comparison between Studio <> LVM
Administration– Starting/Stopping the SAP HANA database– Backup and recovery– User and role management– Configuration changesMonitoring– Integration of all SAP HANA databases in the
landscape possible– Detailed views for specific areas (like services,
volumes, performance relevant information)Alerting– Alerts for critical situations are generated by the
database automatically– Adjustment of alert thresholds to customer needs– Configuration of Email notificationsTracing– Changing trace levels– Display of individual trace files– View to display merged trace files of the different
database services and from all database hosts
Administration– Auto-detection of SAP HANA systems within
SAP landscapes by LVM and requiredconfiguration parameters (incl. host- andinstance-information)
– Managing hierarchies in starting/stopping theSAP HANA database in context of larger SAPlandscapes, respecting their dependencies
Monitoring– Monitoring of SAP HANA system status and
process activity
SAP HANA Studio SAP NetWeaver LandscapeVirtualization Management
© 2013 SAP AG. All rights reserved. 84
SAP HANA Monitoring, Alerting, SchedulingExternal monitoring tools
Use SAP Solution Manager as relay station for monitoring information for externalmonitoring tools.
A lot of these tools offer Solution Manager as a counterpart in these communications.
Alternatively possible by direct SQL connect to SAP HANAMonitoring via direct connection to HANA Statistics ServerScheduling via SQL administration commands send directly to SAP HANA by tool
Alerting framework in external tool
Availability in preparationFirst contacts to external tool vendor establishedAvailability depends on tool partners and the validation process and subsequent partnersolution offerings
© 2013 SAP AG. All rights reserved. 85
SAP HANA Monitoring, Alerting, SchedulingNews with SAP HANA SPS6 and Beyond
Improved Monitoring
Improved SQL Plan Cache
Table and partition redistributioneditor with automation option
Important for Scale-Out setups and howthe data is located in an optimal way ondifferent hosts for BW and SoH scenariosPrepared schemas of data distribution inplace to offer this automation
More support for 3rd partymanagement tools
Planned with SAP HANA SPS7(End of 2013)
More 3rd party management tools
Planned beyond (2014)Monitoring API
© 2013 SAP AG. All rights reserved. 86
SAP HANA documentationSAP Help Portal: http://help.sap.com/hana_appliance
SAP HANA Administration Guide, several chapters e.g. “High Availability forSAP HANA” covering also Disaster Recovery topicSAP HANA Technical Operations Manual (TOM)List of interesting links about the topicData Center Operation:http://www.saphana.com/docs/DOC-2935
SAP Notes1848976:SAP HANA Platform SPS 06Release Note1755396: Released DT solutions forSAP HANA with disk1876398: Network configuration forSAP HANA System Replication1834153: HANA high availability disastertolerance config
More Information
© 2013 SAP AG. All rights reserved. 87
Thank You!
Contact information:
Uwe HeinzProduct Management SAP [email protected]
http://www.saphana.com/
© 2013 SAP AG. All rights reserved. 88
No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may bechanged without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietarysoftware components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of MicrosoftCorporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer,z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER,OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP,RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registeredtrademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks orregistered trademarks of Adobe Systems Incorporated in the United States and/or othercountries.Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin aretrademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, WorldWide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license fortechnology invented and implemented by Netscape.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,StreamWork, and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and othercountries.
© 2013 SAP AG. All rights reserved
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, CrystalDecisions, Web Intelligence, Xcelsius, and other Business Objects products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarksof Business Objects Software Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybaseproducts and services mentioned herein as well as their respective logos are trademarks orregistered trademarks of Sybase, Inc. Sybase is an SAP company.
All other product and service names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informational purposes only. Nationalproduct specifications may vary.The information in this document is proprietary to SAP. No part of this document may bereproduced, copied, or transmitted in any form or for any purpose without the express priorwritten permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or anyother agreement with SAP. This document contains only intended strategies, developments,and functionalities of the SAP® product and is not intended to be binding upon SAP to anyparticular course of business, product strategy, and/or development. Please note that thisdocument is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does notwarrant the accuracy or completeness of the information, text, graphics, links, or other itemscontained within this material. This document is provided without a warranty of any kind,either express or implied, including but not limited to the implied warranties ofmerchantability, fitness for a particular purpose, or non-infringement.SAP shall have no liability for damages of any kind including without limitation direct,special, indirect, or consequential damages that may result from the use of these materials.This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has nocontrol over the information that you may access through the use of hot links contained inthese materials and does not endorse your use of third-party Web pages nor provide anywarranty whatsoever relating to third-party Web pages.
© 2013 SAP AG. All rights reserved. 89
SAP HANA PersistenceNews with SAP HANA SPS6 and Beyond
Hybrid LOBsKeep LOBs mostly on disk to optimizememory efficiency
Paged AttributeRead tables/columns in smaller chunksespecially with single record access
IO Optimizations for ROW storeDo IOs on ROW store in chunks up to 64MBIncreases speed of start-up and Backup &Recovery
Support for large Data Volumes onEXT3 file system
Support bigger Data Volumes possiblewith Scale-up of SoH which will not be
able to be handled by EXT3 (2 TB file sizelimit of EXT3)
Smart Data AccessLet external database content look likeinternal SAP HANA local tables to createcontent on top with all known featuresSAP HANA can offer to developers
Planned with SAP HANA SPS7 (Endof 2013)
Persistence development is deeplyinvolved in several projects, like IQtechnology integration into SAP HANA
Planned beyond (2014)More flexible Data Volume management