SAP_HANA_Technical_Operations_Manual_en[1].pdf

8/14/2019 SAP_HANA_Technical_Operations_Manual_en[1].pdf

http://slidepdf.com/reader/full/saphanatechnicaloperationsmanualen1pdf 1/53

PUBLIC

SAP HANA Platform SPS 06Document Version: 1.1 - 17-07-2013

SAP HANA Technical Operations Manual



Table of Contents

1 Getting Started with SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.1 About Technical Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.2 What is SAP HANA?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

1.3 SAP HANA Guides. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.4 Related Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.5 Important SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

1.6 Software Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.6.1 Download Patches and Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.7 So ftware Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 Administering and Operating SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.1 Roles and Responsibilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.2 Service and Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

2.3 Installation of the SAP HANA Appliance Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.4 Change Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.5 Software Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.5.1 Updating and Patching the Operating System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

2.5.2 Updating and Patching SAP HANA Appliance Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.5.3 Updating and Patching File System Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.5.4 Updating and Patching Storage Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.5.5 Updating and Patching Firmware of Underlying Hardware Components . . . . . . . . . . . . . . . . . 17

2.6 Monitoring the SAP HANA Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.6.1 Integrating SAP HANA into a Central Operations Concept. . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.7 Administering the SAP HANA Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

2.7.1 Initial Administrative Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.7.2 Regular Administrative Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.7.3 On Demand Administrative Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.8 Backup and Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2.9 Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.9.1 Security Features and Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2.9.2 Data Center Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2.9.3 Compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2.10 Hi gh Availability for SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3 Administering and Operating SAP HANA Data Provisioning Technologies. . . . . . . . . . . . . . . . . . . 31

3.1 SAP HANA Data Provisioning Technologies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.1.1 SAP Sybase Event Stream Processor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

3.1.2 SAP HANA Smart Data Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.1.3 SAP HANA Replication Technologies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

2P U B L I C© 2013 SAP AG or an SAP affiliate company. All rights reserved.

SAP HANA Technical Operations ManualTable of Contents



3.2 Monitoring the SAP HANA System Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.2.1 Monitoring Components for Trigger-Based Replication (SAP LT Replication Server). . . . . . . . 44

3.2.2 Monitoring components for SAP HANA Direct Extractor Connection (DXC). . . . . . . . . . . . . . 45

3.2.3 Monitoring Components for ETL-Based Replication (SAP Data Services). . . . . . . . . . . . . . . . 45

3.3 SAP HANA Administration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

3.3.1 Administrating Components for Trigger-Based Replication (SAP LT Replication Server). . . . . 45

3.3.2 Administrating Components for SAP HANA Direct Extractor Connection (DXC). . . . . . . . . . . 46

3.3.3 Administrating Components for ETL-Based Replication (SAP Data Services). . . . . . . . . . . . . 46

3.4 Starting the Software Update Manager (SUM) for SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

3.5 Backup and Recovery of SAP HANA Replication Technologies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

3.5.1 Backup and Recovery for the Trigger-Based Replication components (SAP LT Replication Server). . . . . 47

3.5.2 Backup and Recovery for the SAP HANA Direct Extractor Connection (DXC). . . . . . . . . . . . . 47

3.5.3 Backup and Recovery for the ETL-Based Replication components (SAP Data Services). . . . . . 48

3.6 Security for the SAP HANA System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

4 SAP HANA Data Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

4.1 Configuring Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

4.2 Modeling Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

4.3 Modeling and Data Provisioning for ETL-Based Replication (SAP Data Services). . . . . . . . . . . . . . . . . . 49

5 SAP liveCache on SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

SAP HANA Technical Operations ManualTable of Contents

P U B L I C© 2013 SAP AG or an SAP affiliate company. All rights reserved. 3



1 Getting Started with SAP HANA

1.1 About Technical Operations

This Technical Operations Manual provides an end-to-end picture of the administration tools available with SAPHANA and the key tasks that a system administrator needs to perform. Links to the rele vant administrationdocumentation of each of the components included in the SAP HANA solution are provided for details and stepprocedures.

Caution

This guide does not replace the daily operations handbook that we recommend customers to create for their

specific production operations.

1.2 What is SAP HANA?

SAP HANA is a modern in-memory platform that is deployable as an on-premise appliance, or in the cloud. As anappliance, SAP HANA combines software components from SAP optimized on proven hardware provided bySAP’s hardware partners. In the cloud SAP HANA is offered as a comprehensive infrastructure combined with

managed services. SAP HANA can also be deployed through the following cloud offerings: SAP HANA One, SAPHANA Cloud and SAP HANA Enterprise Cloud.

The SAP HANA platform is a flexible data source agnostic in-memory data platform that allows customers toanalyze large volumes of data in real-time. It is also a development platform, providing an infrastructure and toolsfor building high-performance applications based on SAP HANA Extended Application Services (SAP HANA XS). Itis the foundation of various SAP HANA editions, like the SAP HANA Platform Edition, providing core databasetechnology, and the SAP HANA Enterprise Edition, bundling additional components for data provisioning. The SAPHANA Platform Edition integrates a number of SAP components, including the SAP HANA database, SAP HANAstudio, and SAP HANA clients.

1.3 SAP HANA Guides

For more information about SAP HANA landscape, security, installation, and administration, see the resourceslisted below:

Topic Location Quick Link

SAP HANA landscape, deployment,and installation

SAP HANA Knowledge Centeron the SAP Help Portal

http://help.sap.com/hana_platform :

● SAP HANA Master Guide● SAP HANA Server Installation Guide


SAP HANA Technical Operations ManualGetting Started with SAP HANA

http://help.sap.com/hana/SAP_HANA_Server_Installation_Guide_en.pdf

http://help.sap.com/hana/SAP_HANA_Master_Guide_en.pdf

http://help.sap.com/hana/SAP_HANA_Server_Installation_Guide_en.pdf


http://help.sap.com/hana_platform



Topic Location Quick Link

● SAP HANA Master Update Guide

● SAP HANA Update andConfiguration Guide

SAP HANA administration andsecurity

SAP HANA Knowledge Centeron the SAP Help Portal

http://help.sap.com/hana_platform :

● SAP HANA Technical OperationsManual

● SAP HANA Administration Guide● SAP HANA Security Guide

SAP HANA documentation forprevious Support Package Stacks

SAP HANA Knowledge Centeron SAP Service Marketplace

https://service.sap.com/hana :

● SAP HANA SPS 05 Documentation(ZIP)



1.4 Related InformationFor more information about planning your deployment, see the following:

Content Location

Latest documentation for SAP HANA https://service.sap.com/hana *


Sybase product documentation http://sybooks.sybase.com/nav/base.do

Sizing, calculation of hardware requirements, such as CPU,disk, and memory resources

https://service.sap.com/sizing

SAP BusinessObjects installation and deployment guides https://service.sap.com/bosap-instguides

SAP BusinessObjects support https://service.sap.com/bosap-support

Sizing, calculation of hardware requirements - such as CPU,disk and memory resources - with the QuickSizer tool

https://service.sap.com/quicksizer

Released platforms and technology-related topics such asmaintenance strategies and language support – Platform

Availability Matrix (PAM)

https://service.sap.com/pam




https://service.sap.com/quicksizer

https://service.sap.com/bosap-support

https://service.sap.com/bosap-instguides

https://service.sap.com/sizing

http://sybooks.sybase.com/nav/base.do


https://service.sap.com/hana

https://service.sap.com/~sapidb/011000358700001430632012







http://help.sap.com/hana/SAP_HANA_Security_Guide_en.pdf

http://help.sap.com/hana/SAP_HANA_Administration_Guide_en.pdf

http://help.sap.com/hana/SAP_HANA_Technical_Operations_Manual_en.pdf

http://help.sap.com/hana/SAP_HANA_Technical_Operations_Manual_en.pdf


http://help.sap.com/hana/SAP_HANA_Update_and_Configuration_Guide_en.pdf

http://help.sap.com/hana/SAP_HANA_Update_and_Configuration_Guide_en.pdf

http://help.sap.com/hana/SAP_HANA_Master_Update_Guide_en.pdf



Content Location

Network security https://service.sap.com/securityguide

High availability http://scn.sap.com/docs/DOC-7848

Security https://service.sap.com/security

Unicode SAP systems and their availability https://service.sap.com/unicode

Information about Support Package Stacks, latest softwareversions and patch level requirements

https://service.sap.com/sp-stacks

(*) You need an authorized user ID to access this information. Do you need to register for an SAP ServiceMarketplac e login ? Did you f orget your password ?

The following table lists further useful links on SAP Service Marketplace:

Content Location on SAP Service Marketplace

SAP message wizard https://service.sap.com/message

SAP Notes search https://service.sap.com/notes

SAP Software Distribution Center – software download andordering of software

https://service.sap.com/swdc

SAP Online Knowledge Products (OKPs) – role-specificlearning maps

https://service.sap.com/rkt

1.5 Important SAP Notes

Read the following SAP Notes before you start the installation. These SAP Notes contain the latest inform ationabout the installation, as well as corrections to the installation documentation.

Make sure that you have the most up-to-date version of each SAP Note, which you can find on SAP ServiceMarketplace at https://service.sap.com/notes .

SAP Note Number Title

SAP Note 1514967 SAP HANA: Central Note

SAP Note 1848976 SAP HANA Appliance Software SPS 06 Release Note

SAP Note 1523337 SAP HANA Database: Central Note

SAP Note 1681092 Support for multiple SAP HANA databases on a single SAP

HANA appliance



https://service.sap.com/sap/support/notes/1514967


https://service.sap.com/notes






https://service.sap.com/rkt

https://service.sap.com/swdc


https://service.sap.com/message

http://service.sap.com/~sapidb/002006825000101060662000E/



https://service.sap.com/sp-stacks

https://service.sap.com/unicode

https://service.sap.com/security

http://scn.sap.com/docs/DOC-7848

https://service.sap.com/securityguide




SAP Note 1661202Support for multiple applications on SAP HANA

SAP Note 1828400 SAPUI5 tools disappeared after updating HANA Studio

SAP Note 1577128 Supported clients for SAP HANA

SAP Note 1514966 SAP HANA: Sizing SAP HANA Database

SAP Note 1637145 SAP BW on HANA: Sizing SAP HANA Database

SAP Note 1793345 Sizing for Suite on HANA

SAP Note 1824819 Optimal settings for SLES 11 SP2 and SLES 11 for SAP SP2

SAP Note 1597355 Swap space recommendation for Linux

For the SAP HANA system there are no special requirements

regarding swap space.

Check the current SAP Notes for the various parts of SAP HANA by searching for any of the following applicationareas:

SAP HANA Platform

● BC-DB-HDB SAP HANA Database● BC-DB-HDB-AFL SAP HANA Application Function Library● BC-DB-HDB-AFL-DQ SAP HANA Data Quality Library● BC-DB-HDB-AFL-PAL SAP HANA Predictive Analysis Library● BC-DB-HDB-AFL-SOP SAP HANA Sales and & Operations Planning● BC-DB-HDB-BAC SAP HANA Backup & Recovery● BC-DB-HDB-CCM CCMS for SAP HANA● BC-DB-HDB-CLI SAP HANA Clients (JDBC, ODBC)● BC-DB-HDB-DBA SAP HANA database administration (DBA cockpit)● BC-DB-HDB-DXC SAP HANA direct extractor connector● BC-DB-HDB-ENG SAP HANA database engine● BC-DB-HDB-MDX MDX Engine / MS Excel client● BC-DB-HDB-HLM SAP HANA Lifecycle Manager● BC-DB-HDB-PER SAP HANA database persistence● BC-DB-HDB-PLE Planning Engine● BC-DB-HDB-POR DB Porting for SAP HANA● BC-DB-HDB-R SAP HANA Integrat ion with R● BC-DB-HDB-SCR SAP HANA SQL Script● BC-DB-HDB-SCR -CLT SAP HANA SQL Script Editor/Debugger Client● BC-DB-HDB-SEC SAP HANA Security & User Management● BC-DB-HDB-SYS SAP HANA database interface/DBMS● BC-DB-HDB-TXT SAP HANA Text & Search Features

● BC-DB-HDB-XS SAP HANA Application Services

















● BC-DB-HDB-XS-WB Workbench / Team Provider SAP HANA DB● BC-DB-LCA SAP HANA liveCache Applications● BC-HAN-MOD SAP HANA studio / information modeler● BC-HAN-3DM SAP HANA information composer● BC-HAN-SRC SAP HANA UI Toolkit● BC-CCM-HAG SAP Host Agent● SV-SMG-DIA SAP Solution Manager Diagnostics Agent

SAP HANA Lifecycle Management

● BC-HAN-SL-STP SAP HANA unified installer● BC-DB-HDB-INS SAP HANA database installation (hdbinst)● BC-HAN-UPD Software Update Manager for SAP HANA● BC-DB-HDB-UPG SAP HANA database upgrade (hdbupd)

SAP HANA Enterprise● BC-HAN-LOA SAP HANA load controller (log-based replication)● BC-HAN-REP Sybase rep. server (log-based replication)● BC-HAN-LTR SAP Landscape Transformation (trigger-based replication)● BC-HAN-DXC SAP HANA Direct Extractor Connection● EIM-DS Data Services (ETL-based replication)

End User Clients

● BI-BIP, BI-BIP-CMC Business intelligence platform (formerly known as BOE)● BI-RA-EXP SAP BusinessObjects Explorer● BI-RA-CR, BI-BIP-CRS SAP Crystal Reports● BI-RA-XL Dashboard Designer● BI-BIP-IDT Information design tool● BI-RA-WBI Web Intelligence● BI-RA-AO-XLA MS Excel Add-In

The search also supports using the wildcard asterisk (*), so you can, for example, also search for BC-DB-HDB* orsimilar and you will get results for all sub-components.

Customer Messages

If you encounter any problems with the software, create a customer message on the SAP Service Marketplace athttp://service.sap.com/message .

In addition, the Customer Interaction Center (CIC) is available 24 x 7 in every region to help you resolve any issuesyou may run into ( https://service.sap.com/supportcenters ).

The CIC requires a valid S-user number. To create an S-user ID, follow the steps in this guide ( https:// service.sap.com/~sapidp/011000358700000905192010E.pdf ).

When creating a customer message, you can choose from the above list of components for the relevant software

part.



https://service.sap.com/~sapidp/011000358700000905192010E.pdf


https://service.sap.com/supportcenters

http://service.sap.com/message



https://service.sap.com/supportcenters

http://service.sap.com/message



1.6 Software Download

The components of SAP HANA can only be installed by certified hardware partners on validated hardware runninga specific operating system. Any other system or content developed with such systems is not supported by SAP.For more information, see the information page of the product version. Support Package Stacks (SPS) can bedownloaded and applied to appliances according to agreements with the respective hardware partner.

1.6.1 Download Patches and Updates

Note

For more information on applying patches and updates see the section on Change Management.

Related Links

Change Management [page 14]

1.7 Software Components

The SAP HANA Platform Edition is the foundation of various other SAP HANA editions, like the SAP HANAEnterprise Edition. These editions bundle additional components that customers might require, for example, fordata replication. The SAP HANA Platform Edition is composed of the following components:

● SAP HANA database● SAP HANA client● SAP HANA client for Microsoft Excel● SAP HANA studio● SAPUI5 Tools IDE PLUGIN● SAP Host Agent● Diagnostics Agent● SAP HANA information composer● SAP HANA AFL● SAP HANA LCApps● SAP HANA lifecycle manager● SAP HANA RDL● SAP HANA smart data access● SAP HANA INA Toolkit HTML● SAP HANA unified installer● LM structure inst SAP HANA● SAP HANA Direct Extractor Connection (DXC)

The SAP HANA Platform Edition is bundled together with other products into editions as license bundles forspecial purposes. This is a subset of the available editions:





● SAP HANA Enterprise Edition (containing SAP Data Services and SAP LT Replication Server)● SAP Sybase Replication Server, SAP HANA edition● Real-time-data edition for SAP HANA (includes SAP Sybase Replication Server, SAP HANA edition)● SAP HANA Database edition for BW● SAP HANA Limited edition for Apps / Accelerators● SAP HANA EDGE edition

Note

SAP HANA information composer is a Web-based environment that allows business users to upload data to theSAP HANA database and to manipulate that data by creating information views. The SAP HANA informationcomposer is installed separately from the SAP HANA system. For more information, see the SAP HANAInformation Composer – Installation and Configuration Guide .



http://help.sap.com/hana/SAP_HANA_Information_Composer_Installation_Guide_en.pdf

http://help.sap.com/hana/SAP_HANA_Information_Composer_Installation_Guide_en.pdf



2 Administering and Operating SAP HANA

2.1 Roles and Responsibilities

This section describes the tasks, concepts, responsibilities, and procedures necessary for the ongoing operationof the SAP HANA appliance software. It answers the following questions:

● Tasks and ResponsibilitiesThe following table gives an overview of tasks and who is responsible for the task. What is SAP responsible forand what does SAP support? What do the SAP hardware partners do? What is the customer asked to do? Thisis explained in more detail in the following sections.

Phase Task Responsible

Provisioning/Setup

Installation of Hardware Hardware Partner

Installation of Operating System Hardware Partner

Installation of SAP HANA Platform Hardware Partner

Adding additional SAP HANA databaseinstances (MCOS)

Customer

Data Source Connectivity Customer

Maintenance

Patching of Firmware Customer (*)

Patching of Operating System Customer (*)

Patching of SAP HANA platformcomponents

Customer

Patching of peripheral components Customer

Upgrade of Operating System Customer (*)

Update of SAP HANA platformcomponents

Customer

Operations

General administration of SAP HANAdatabase

Customer

Backup and Recovery Customer

SAP HANA System Monitoring Customer

SAP HANA Database Monitoring Customer

Installation of third party softwarecomponents

Customer

Support

Issue Handling Process SAP, Customer (*), (**)

SAP HANA Technical Operations ManualAdministering and Operating SAP HANA




(*) The customer is generally responsible for maintenance of the SAP HANA system. If the customer has aspecial support agreement with the hardware partner, maintenance may be the responsibility of the hardwarepartner.

(**) SAP is the main point of contact and distributes all issues within the support organization by default, as isthe case for other SAP applications. If the customer has defined special support agreements with thehardware partner, the customer should contact the hardware partner directly in the case of obvious hardwareor operating system issues. If no agreements have been made neither SAP nor the hardware partner areresponsible for the installation, maintenance and possible adjustment of external software installed on theSAP HANA system.

● Schedule - When and how often should each task be performed? What tasks are to be performed duringongoing operation, such as regular checks and periodic tasks? What tasks must be performed on demand andin special situations?

● Procedures - How can each task be performed? Several tools and transactions can be used for administeringand monitoring SAP HANA.

SAP HANA is following the appliance delivery model. Hence it can only be obtained from one of the followingcertified SAP hardware partners:

● Hewlett Packard ( http://www.hp.com/go/sap/hana )● IBM (http://www.ibm.com/solutions/sap/hana )● Fujitsu Computers ( http://ts.fujitsu.com/hana )● CISCO systems ( http://www.cisco.com )● DELL (http://www.dell.com )● Hitachi ( http://www.hds.com/solutions/applications/sap-application/sap-hana.html )● NEC ( http://www.nec.com )● Lenovo ( http://www.lenovo.com )● Huawei ( http://enterprise.huawei.com/en/ )● VCE (http://www.vce.com/products/specialized/sap-hana )

For more informatio n on supported software and hardware platforms refe r to the SAP Product Availability Matrix(search for "HANA"), th e SAP HANA Master Guide on SAP Service Marketplace https://service.sap.com/hana orrespective components administration guides a t https://help.sap.com/hana .

2.2 Service and Support

If errors occur in an y software component of SAP HANA, SAP i s the main point of contact. SAP distributes allissues within the support organi zation by default, as is the case for other SAP applications.

If the customer has defined special support agreements with the hardware partner (such as a special ServiceLevel Agreement (ESA)), the customer should contact the hardware partner directly in the case of obvioushardware or operating system issues.

To investigate SAP HANA-related problems, SAP support requires a support connection to all servers in the SAPHANA landscape. For more information about establishing a service connection for SAP HANA, see SAP ServiceMarketplace. See SAP Note 1635304 .

Note

You need a valid SAP Service Marketplace user to access SMP and related SAP Notes.




http://www.vce.com/products/specialized/sap-hana

http://enterprise.huawei.com/en/

http://www.lenovo.com/

http://www.cisco.com/

http://www.ibm.com/solutions/sap/hana

http://www.hp.com/go/sap/hana


https://help.sap.com/hana


http://www.vce.com/products/specialized/sap-hana

http://enterprise.huawei.com/en/

http://www.lenovo.com/

http://www.nec.com/

http://www.hds.com/solutions/applications/sap-application/sap-hana.html

http://www.dell.com/

http://www.cisco.com/

http://ts.fujitsu.com/hana

http://www.ibm.com/solutions/sap/hana

http://www.hp.com/go/sap/hana



2.3 Installation of the SAP HANA Appliance Software

The installation of the SAP HANA appliance software is performed by the SAP hardware partner. Therefore, theSAP hardware partners deliver the SAP HANA appliance software together with corresponding, validatedhardware as a prepackaged solution with the most recent support package stack (at the time of shipment of theSAP HANA appliance ) to the c ustomer site. The SAP hardware partner may add specific best-practices and SAPHANA software configuration. The installation is finalized by an onsite setup of the SAP HANA components. Thisincludes deploying the SAP HANA system in the customer data center, connectivity to the network, SAP systemrename, and SAP Solution Manager connectivity, if applicable.

Once the network connection to the SAP HANA system has been established successfully and the SAP HANAsystem with the most recent support packages is reachable under its desired host name, IP address and SAPsystem ID from within the customer network, the establishment of data replication/connectivity to data source

systems (including the deployment of additional replication components) and the installation of potential BIclients (such as SAP BusinessObjects Explorer on top of BOE) is again the responsibility of the customer or theconsulting organization carrying out the SAP HANA project onsite for the customer.

Note

The installation of the SAP HANA server components, in particular the installation of the SAP HANA databaseshall only be performed by certified hardware partners, on validated hardware, running a specific operatingsystem, as published in the SAP HANA Product Availability Matrix on SAP Service Marketplace ( http:// service.sap.com/pam ). Any other system or content developed with such systems is not supported by SAP foruse in production. SAP HANA studio and clients need to be installed outside of the SAP HANA appliance andcan therefore be downloaded and installed by SAP customers directly.

Further note, there is a product “SAP HANA (platform|enterprise edition)”, where the “SAP HANA database” isone component of the product. The product is also comprised of other components. In consequence, do not touse the individual installation tools of the various components to setup a SAP HANA system. The SAP HANAunified installer is the only official tool for installing the SAP HANA product and should always be used toensure proper system setup. Otherwise Lifecycle Management processes like the Software Update Manager(SUM) for SAP HANA, a tool for updating and patching of the SAP HANA product might fail if the product wasnot installed comple tely as a whole.

Installation of additional software

To ensure the smooth operation of an SAP HANA system and to fulfill IT compliances and IT policies, you need touse external software in the SAP HANA appliance. External software is software that was not delivered by SAP orby your HANA appliance hardware partner.

SAP permits the installation and operation of external software that is required to fulfill the IT compliance and ITpolicy that are determined in operation, provided the prerequisites in the following SAP Notes are met.


1730929 Using external tools in an SAP HANA appliance




http://service.sap.com/pam







1730932 Using backup tools with Backint

1730930 Using antivirus software in an SAP HANA appliance

Each of these SAP Notes refers to additional documentation about software and software versions that, in theexperience of SAP Support, have caused problems in the customer environment or in the laboratories of SAP orthe hardware suppliers and are therefore not recommended for use in the HANA appliance.

Neither SAP nor the hardware supplier of your HANA appliance are responsible for the installation, maintenanceand possible adjustment of the external software if no agreements have been made for this purpose.

2.4 Change Management

The following sections provide information on permitted configuration changes to the SAP HANA software,operating system, and so on. You will also find information about the changes that are not supported by SAP orSAP hardware partners.

SAP allows changes in configuration parameters in the SAP HANA database, when this is recommended in SAPdocumentation, SAP Notes or by an SAP employee (e.g. Consulting, Development, or Support).

To guarantee optimal performance and the highest stability SAP HANA appliance Hardware partners can deliversystems with properties that differ from the standard.

Changes t o operating system parameters and ports are only allowed with the agreement of the hardware partnerthat provided your SAP HANA appliance.

SAP Note 1731000 describes configuration changes that resulted in problems in customer environments and inSAP or hardware partner lab environments.

2.5 Software Maintenance

2.5.1 Updating and Patching the Operating System

The initially delivered configuration of the operating system should persist. If configuration settings aresubsequently changed, significant performance problems may occur. The customer can request a validation ofconfiguration changes for the operating system and for the installation of additional operating systemcomponents by the hardware partner depending on the service contract between the hardware partner and thecustomer. The hardware partner then supports these changes and additional components in accordance with theexisting service contract with the customer. No modified Linux version can be used.

The customer is generally responsible for implementing operating system patches. If the customer has a specialagreement with the hardware partner, support for operating system patching may be the responsibility of thehardware partner.









OS security patches may be installed immediately after they are available; however, the original packages of thedistributors must be used, that a customer is entitled to within the framework of a valid support contract with thedistributor or an authorized OEM.

For all other operating system patches, the customer should wait until they are officially released for SAP HANAvia a corresponding SAP Note before the operating system is updated with the patches in question. In particular,any updates related to kernel or runtime libraries (glibc) need to be validated and approved by SAP beforehand.Support Package Stacks (SPSs) can be downloaded and applied to the SAP HANA system only according toagreements with the respective hardware partner.

On rare occasions, SAP HANA might require a certain operating system patch. In this case, you must ensure thatthe configuration settings of the operating system persist. Do not change configuration settings when you patchthe operating system unless explicitly stated in the corresponding SAP release note. SAP will state anydependencies in the relevant SAP Note published when a revision is released which requires such modifications.

NoteIn some cases, customers may have outsourced the administration of their landscapes. In such a case, theoutsourced service provider should only change any settings after consultation with the hardware supportprovider. The customer is responsible for any complete upgrade of the operating system and the use of toolsfor distributing operating system patches in a distributed system landscape.

SUSE offers enhanced support for SUSE Linux in collaboration with SAP Linux Lab ('SUSE Priority Support forSAP'). This support offer facilitates communication and ensures high quality. OS security patches may beimported immediately after they are available; however, the original packages of the distributors must be used,that a customer is entitled to within the framework of a valid support contract with the distributor or an authorizedOEM.

For more information, see SAP Note 1056161 - SUSE Priority Support for SAP applications and SAP Note 171356 –SAP software on Linux: Essential information (SAP Service Marketplace user required).

2.5.2 Updating and Patching SAP HANA Appliance Software

The SAP hardware partners ship SAP HANA pre-configured and with the most recent support package stack atthe time when the SAP HANA appliance is shipped. The customer is responsible for the subsequent

implementation of SAP HANA patches, revisions, or support packages and support package stacks.In general the following points apply:

● Any system connected to the SAP HANA system, as a source or as a client, may require a minimum SAPHANA support package stack to be implemented. Unless explicitly stated, we recommend applying the latestSAP HANA support package stack after applying an update to the connected system.

● The SAP HANA support packages are cumulative. You can update directly from any older SAP HANA supportpackage to any newer SAP HANA support package.

● New SAP HANA support package mainly cover software improvements. SAP recommends that you downloadand install these new SAP HANA support packages if SAP support has to resolve issues with SAP HANAversions previously installed in the customer landscape. However, customers do not necessarily need toupdate their SAP HANA landscape with the newest SAP HANA support packages if their SAP HANAlandscape works correctly.







● New SAP HANA support packages and patches will be produced and shipped at SAP’s sole discretion. Thereis no periodic cycle for releasing and patching the SAP HANA software. The new SAP HANA support packagestacks will be communicated to customers and hardware partners by means of SAP Notes.

An automated update of your SAP HANA system is performed using SAP HANA lifecycle manager, which is thesuccessor to the SAP Software Update Manager (SUM) for SAP HANA. SAP HANA lifecycle manager covers allscenarios previously covered by the SUM (SAP HANA system update, single SAP HANA component updates anddeployment of SAP HANA application content), the SAP HANA On-Site configuration tool (renaming SAP HANAsystems, adding additional SAP HANA systems, registration in a System Landscape Directory) and can be used toconfigure SAP Landscape Transformation (LT). SAP HANA lifecycle manager is automatically installed with SAPHANA Unified Installer, as part of the SAP HANA appliance installation. You can access the tool in SAP HANAstudio. An additional command line interface is also be available.

The following scenarios are supported:

● SAP HANA standalone maintenance (online): In the SAP HANA studio, start the lifecycle management

perspective to set up a connection to the SAP Service Marketplace, automatically download the requestedSAP HANA SP-Stack to your SAP HANA system and apply the update.

● SAP HANA standalone maintenance (offline): Download the requested SP-Stack in advance from SAP ServiceMarketplace and make it available to your SAP HANA system. In the SAP HANA studio, enter the location ofthe downloaded SP-Stack and proceed directly with implementing the update.

● SAP Solution Manager based maintenance: Use Maintenance optimizer in your local SAP Solution Manager tocalcul ate a nd download SP-Stack in advance and make it available to your SAP HANA system. In the SAPHANA studio, enter the location of the downloaded SPS and proceed with applying the update.

● For more information, see the SAP HANA Master Update Guide . Additionally see Backing Up and Recoveringthe SAP HANA Database in the SAP HANA Administration Guide .

Note

It is strongly recommended after the initial setup and before every system update, that you perform a full dataand file system backup (including a configuration backup).

For the most current information on SAP HANA support packages and patches, see SAP Note 1514967 – SAPHANA 1.0: Cen tral Note (SAP Service Marketplace user required). Up to now t here are no known dependenciesbetween SAP HANA support package stacks and the SAP HANA hardware an d installed firmwa re. The process forimplementing SAP HANA support packages is described on SAP Service Marketplace at https://service.sap.com/ hana (SAP Service Marketplace user required).

Note

Special support agreements may exist with the hardware partner which include services such as patching.

2.5.3 Updating and Patching File System Components

The customer is responsible for implementing patches for the shared file system. If the customer has a specialagreement with the hardware partner, the hardware partner is responsible for providing support for file system

patching.















● SAP Solution Manager documentation● SAP Solution Manager homepage on SMP● Knowledge transfer by Online Knowledge Products● SAP Solution Manager SCN community

Note

You need an authorized user ID to access this information. Do you need to register for an SAP ServiceMarketplace login ? Did you forget your password ?

2.6.1.1 Connecting SAP Solution Manager to SAP HANA

If you want to use capabilities of SAP Solution Manager, you have to make sure that the two systems know eachother. Prerequisite for this is the registration of the SAP HANA system in the System Landscape Directory. Fromthere, SAP Solution Manager gets the information that the SAP HANA system exists. The communicationbetween the systems is based on a central agent infrastructure. The pre-configured agents are delivered by SAPand deployed on the SAP HANA appliance by the hardware partner.

The configuration of the connection itself is done as part of the basic configuration of SAP Solution Manager. Inthe guided procedure for Managed Systems Configuration you just need to set up the correct connection, assignthe right agents, enter some parameters, create required users, and do a few more configurations. After this, youcan start the collaboration of SAP HANA and SAP Solution Manager.

Some of t he processes in SAP Solution Manager require additio nal configuration to specify how they shouldhandle the SAP HANA database. For example, you have to specify in system monitoring which metrics you wantto control. Or you have to define your transport landscape (development system -> quality assurance system ->productive system) for change control.

Related Links

SAP Note 1747682: Managed System Setup for HANA

2.6.1.2 Central Monitoring and Administration

The monitoring and alerting infrastructure of SAP Solution Manager is based on a central agent infrastructure.SAP delivers pre-configured agents for SAP HANA. If these agents have been deployed on SAP HANA and havebeen connected to SAP Solution Manager, SAP Solution Manager receives all alerts of the HANA DB Studio. Thesealerts will be displayed in the unified alert inbox.

SAP Solution Manager also provides an automated regular status check of your SAP solutions: SAP EarlyWatchAlert (EWA). This tool monitors the essential administrative areas of SAP components and keeps you up to dateon their performance and stability. If you have any ABAP-based system besides or on SAP HANA, you can includethe SAP HANA database information into the EWA report of this system: Availability of services; size and growth;performance; important alerts; and correct setting of configuration parameters.

Besides bas ic administration tasks, SAP provides s pecific ta sk lists for SAP HANA, SAP NetWeaver BusinessWarehouse (BW) on HANA, and SAP LT (Landscape Transformation) Replication Server. These lists describeadditional activities for administering these components and provide best practices for individual tasks.




https://service.sap.com/request-user

https://service.sap.com/request-pw



https://service.sap.com/request-pw



http://scn.sap.com/community/it-management/alm/solution-manager

https://service.sap.com/rkt-solman

https://service.sap.com/solutionmanager

https://help.sap.com/solutionmanager



2.6.1.3 Analyzing the Root Cause of Problems

Often, SAP HANA systems are integrated with business applications that either call application accelerators in theSAP HANA database or are deployed on the database. If a problem occurs in this setup, you have to take asystematic approach to identify the precise cause of the fault. This standardized process must first broadlyidentify the components concerned and then analyze them more closely to arrive at the cause of the fault byprocess of elimination (top-down approach).

End-to-end root cause analysis in SAP Solution Manager provides your support organization with tools andmethods that reliably identify the affected component while minimizing the time needed to solve the problem.Besides your business applications, it supports also your SAP HANA database. This is the foundation for resolvingproblems in a holistic approach. The DBA Cockpit is used in SAP Solution Manager to get a detailed insight intothe status of the database. Basically, this is about the same data that you can see in the SAP HANA Studio foryour in-memory database. But the DBA Cockpit supports other databases as well. If you have heterogeneousdatabases in your environment because your business applications still run on traditional databases, the DBACockpit enables you to use the same tool for the different databases.

Trace analysis records performance-related and functional faults in a specific user activity from the user’sbrowser to the data stored in memory or on a storage sub-system. The measurement is triggered in the userinterface and automatically activates recording of the relevant traces on every component processed by the userquery.

After the root cause of a problem has been located, you can use detailed analysis to find a resolution. Workloadanalysis comprises server-related workload statistics for the connected systems. Exception analysis allows you tocentrally analyze all exceptions from connected systems, such as serious error messages in logs or dumps. Fromhere, you can start component-specific tools. And change analysis creates transparency for all changes (technical

configuration, code, content) that have been made in the connected system landscape. This is particularly usefulin the event of faults that occur once changes have been made to the production landscape.

2.6.1.4 Controlling Change

In integrated system landscapes, it is important to manage all changes in a central system. This is the only way tosynchronously execute changes that affect more than one production system. For example, if you use SAP HANAapplication-specific accelerators (for example, CO-PA) in combination with your SAP ERP back-end, you might

need to synchronize changes of the data models on SAP HANA with changes for accessing the changed modelsfrom the transactions on SAP ERP. SAP Solution Manager provides central transport functions for the entiresystem landscape as well as additional support for quality management.

The process for transporting changes from a SAP HANA development system to a quality assurance and furtheron to the productive system starts in SAP HANA Studio. There you retrieve content from the HANA sourcesystem and export it to enhanced Change and Transport System (CTS+) in SAP Solution Manager. The exporteddelivery units are attached automatically to a transport request of CTS+. After you have released this transportrequest, CTS+ triggers the automatic activation of the change in the SAP HANA repository on the target system(quality assurance or production).

Besides supporting the transport and activation of new or changed data models, views, stored procedures, oranalytic privileges, SAP Solution Manager offers additional possibilities to improve the quality of changes. You canuse change analysis and reporting for getting information about the current status and history of changes.





Configuration validation checks whether the systems of your system landscape (for example, development,quality assurance, and production) are configured consistently and according to the requirements. Quality GateManagement provides an additional quality inspection for projects and ensures changes are transported correctly

and synchronously to the production systems. And Change Request Management within SAP Solution Managercontrols the entire change execution with detailed process and workflow control. Out of these options, you canselect those for controlling changes on SAP HANA that fit best to the quality strategy of your organization.

Related Links

CTS+ How To Guide on SCN

2.7 Administering the SAP HANA Database

You administer the SAP HANA database using the administration console perspective of the SAP HANA studio.The administration console perspective of the SAP HANA studio allows technical users to manage the SAP HANAdatabase as well as to create and manage user authorizations.

For more details, see the SAP HANA Administration Guide

For further reference information, see:

● SAP HANA SQL Reference● SAP HANA Database – System Views Reference

Related Links

SAP HANA Administration Guide

SAP HANA SQL Reference

SAP HANA Database – System Views Reference

2.7.1 Initial Administrative Tasks

It is strongly recommended after the initial setup and after the initial load, that you perform a full data andfilesystem backup (including a configuration backup). For more information, see the section Backing Up andRecovering the SAP HANA Database in the SAP HANA Administration Guide.

Related Links


2.7.2 Regular Administrative Tasks

● Regularly check the system status on the Overview tab page of the administration editor in SAP HANA studio.This displays the most important system information:

○ Overall system state○ General system information (software versions and so on).



http://help.sap.com/hana/html/SAP_HANA_System_Views_Reference_en.html

https://scn.sap.com/docs/DOC-35874


http://help.sap.com/hana/html/SAP_HANA_System_Views_Reference_en.html

http://help.sap.com/hana/html/SAP_HANA_SQL_Reference_en.html


https://scn.sap.com/docs/DOC-35874



○ The Alerts section shows the latest warnings and messages generated by the statistics server, which is amonitoring tool for the database. It collects statistical and performance information using SQLstatements.

○ The bar views provide an overview of important system resources: the amount of available memory,CPUs and storage space is displayed as well as the used amount of these resources. In a distributedlandscape, the amount of available resources is aggregated over all servers. Additionally, the resourceinformation of the server with the highest resource consumption is displayed.

● The Services tab page (under the Landscape tab) of the administration screen in SAP HANA studio, lets youcheck that all services belonging to your system are running: preprocessor, name server and index server foreach host and one statistics server. A statistics server exists on each host of a distributed landscape;however, the service actually runs on the master host only. Running services are indicated by a green icon.Information about resource usage and possible bottlenecks is also displayed.

● Regularly perform data backups including configuration backups. There are no general guidelines for backupfrequency (this depends on the usage scenario). For more information, see the section Backing Up and

Recovering the SAP HANA Database in the SAP HANA Administration Guide.Related Links


2.7.3 On Demand Administrative Tasks

● In case of problems with the SAP HANA database, you can check log and trace files for errors. These log filesare available in the SAP HANA studio on the Diagnosis Files tab page of the administration screen.

●

You can turn on and configure several traces from the Trace Configuration tab. For more details seeConfiguring Traces in the SAP HANA Administration Guide.● In certain situations, you have to restart the system (for example, after a power failure). This can be done

using the SAP HANA Systems view of the SAP HANA studio. After confirming the restart, you need to enterthe operating system user and password before the system is actually restarted. For more details see the SAPHANA Administration Guide.

● Avoiding LOG FULL (file system full) situationsWhen the log is backed up, the backed up log segments remain on disk until they have been releasedautomatically after a savepoint. After the log has released, the oldest unused log segment can be overwrittenwith new log entries. If there are no unused log segments, new log segments are created. If the disk becomesfull and no more log segments can be created, a log full situation arises. When the log is full, no more loggingis possible until the log backup has completed. Automatic log backup prevents log full situations from arising.For more information, see the section Backing Up and Recovering the SAP HANA Database in the SAP HANAAdministration G uide.

● Avoid log backup area becoming full.Regularly archive old log backups to a different location (using operating system commands).

● Monitor disk space that is used for diagnosis files (these files record errors and changes in system behavior)and can be viewed on the Diagnosis Files tab in SAP HANA studio. We recommend using SAP HANA studio todelete diagnosis files that are no longer needed.

Caution

Do not delete log segments on the operating system level, as the log area will become unusable and the

database may stop working.







● Before the SAP HANA database or SAP HANA software is upgraded to a new version, perform a data backupincluding a configuration backup. This allows for the recovery of the system in case the software upgradefails.

● After the initial load has finished successfully, a data backup is strongly recommended.● For more information, see the section Backing Up and Recovering the SAP HANA Database in the SAP HANA

Administration Guide.

Note

For replication scenarios during the initial data load - from ERP into the SAP HANA database – log writingshould not be switched off.

Note

There is no system table or log file that records the information that log writing has been switched off. For thisreason, SAP does not recommend switching off the log during initial load. It is not possible to check when logwriting has been switched OFF/ON on customer systems.

Related Links


2.8 Backup and Recovery

The backup and recovery functionality in SAP HANA is quite straightforward. The payload of all data volumes of allservices (name server, index server, statistics server) that belong to a database is written to service-specificbackups. Backups can be written to the file system or using a third-party backup tool. An administrator can backup the database with only a few clicks and the system does the rest automatically: all the relevant service-specificdata is backed up, regardless of whether your system has a single node or multiple nodes.

In-Memory Data and Persistent Storage

The SAP HANA database holds the bulk of its data in memory for maximum performance, but still uses persistentstorage to provide a fallback in case of failure.

During normal database operation, data is automatically saved from memory to disk at regular savepoints.

Additionally, all data changes are captured in the redo log. With each committed database transaction, the redolog is saved from memory to disk and also log backups for SAP HANA are available.

If a failure occurs, for example a power outage, the database can be restarted in the same way as any disk-baseddatabase, and it is returned to its last consistent state by replaying the redo log since the last savepoint.






Recovery

Using data and log backups (and if available log entries from the log volumes), the SAP HANA database can berecovered. A recovery may be necessary in one of the following situations:

● Data area is unusable● Log area is unusable● Logical error

Note

The recovery process of the SAP HANA database causes the database to be shut down. During recovery, thesystem is therefore not accessible for end-users or applications.

For more information, see the section Backing Up and Recovering the SAP HANA Database in the SAP HANAAdministration Guide.

Related Links

SAP HANA Administr ation Guide

2.9 Security

How you implement SAP HANA determines what you need to consider from a security perspective.

SAP HANA can be implemented in the following main ways:

● As a data mart for reporting and analytics● As the primary database in a traditional 3-tier architecture, for example, in SAP NetWeaver Business

Warehouse (SAP NetWeaver BW) or SAP Business Suite installations● As a platform for providing database and application services to native SAP HANA-based applications

For more information about the security-relevant information that applies to SAP HANA in your scenario, see theSAP HANA Security Guide .

Related Links

SAP HANA Security Guide

2.9.1 Security Features and Functions

SAP HANA provides security-related features that enable you to implement different security policies and meetcompliance requirements. Depending on the scenario in which SAP HANA is used, only some of these featuresmight actually be needed, others might be provided in other architecture layers.

SAP HANA supports standard interfaces to enable integration with customer security network and data centerinfrastructures.









Depending on the scenario, the user accessing the SAP HANA database may either be a technical user or anindividual end user. Independent of the SAP HANA scenario, there will always be direct access to SAP HANA bydatabase administrators. For user and role management, you can use either the SAP HANA studio or SQL

commands.

Authorization

All access to data and execution of actions in the database requires authorization. The user must have both theprivilege(s) to perform the operation and the privilege(s) to access the object (for example, a table) to which theoperation applies.

Privileges can be granted to database users either directly, or indirectly through roles. A role is a set of privileges.Roles are the standard mechanism of granting privileges as they allow you to implement both fine-grained andcoarse-grained reusable hierarchies of user access that can be modeled on business roles. Several standard rolesare also delivered with the SAP HANA database (for example, MODELING, MONITORING). You can use these astemplates for creating your own roles. It is also possible to create roles as design-time objects in the repository ofthe SAP HANA database.

There is a privilege concept for both design time (developer use case) and runtime.

The following privilege types exist:

● System privileges: Authorize execution of administrative actions for the entire SAP HANA database● SQL privileges: Authorize access to data and operations on database objects

● Analytic privileges: Authorize read access to analytic views at runtime and provide row-level access controlbased on the dimensions of the relevant view

● Package privileges: Authorize access in the repository (modeling environment) at design time● Application privileges: Authorize access to SAP HANA XS application functions

Secure Communication

Network traffic can be encrypted using SSL (v.3), both between the SAP HANA database and clients, as well asbetween hosts in a distributed SAP HANA system.

Encryption

The SAP HANA database can encrypt data at rest (data volumes). Encryption works at the page level and uses theAES256 encryption algorithm.





Operating System

SAP HANA is based on SUSE Linux Enterprise 11 for SAP and includes security pre-configurations (for example,minimal network services). The SAP HANA database runs with a restricted operating system user. Operatingsystem access using SSH, for example, is not required for the day-to-day operations of SAP HANA.

Security Patches

SAP HANA security patches are published as part of the general SAP security patch strategy (SAP SecurityNotes). SAP HANA security patches are delivered as SAP HANA revisions and can be applied via SUM for SAPHANA. Operating system security patches are provided and published by SUSE and can be applied by customersas soon as they become available.





Network Integration

Network communication (purpose, ports) used by SAP HANA are documented in the SAP HANA Security Guideand in the SAP HANA Master Guide . This guide includes recommendations for the use of firewalls and how toseparate internal and external communication. SSL is supported for network communication channels.

Related Links

SAP HANA Security Guide

SAP HANA Master Guide

2.9.3 Compliance

SAP HANA takes an end-to-end approach to enable application compliance. This is based on the built-in databasesecurity features and the secure pre-configuration of the whole software stack (for example, operating system).This is extended by integration with existing security infrastructures via standard/documented interfaces and theoption to use third-party tools that are required for data center operations. This is complemented by an end-to-end documentation covering the whole software life cycle, including an exhaustive security guide andrecommendations for a secure setup.







Deletion

As part of the technical infrastructure for applications, SAP HANA provides delete functions for records in alltypes of tables. These functions can be leveraged by applications to implement their specific deletionrequirements.

2.10 High Availability for SAP HANA

SAP HANA is fully designed for high availability. It supports recovery measures ranging from faults and softwareerrors, to disasters that decommission an entire data center. High availability is the name given to a set of

techniques, engineering practices and design principles that support the goal of business continuity. This isachieved by eliminating single points of failure (fault tolerance), and providing the ability to rapidly resumeoperations after a system outage with minimal business loss (fault resilience). Fault recovery is the process ofrecovering and resuming operations after an outage due to a fault. Disaster recovery is the process of recoveringoperations after an outage due to a prolonged data center or site failure. Preparing for disasters may requirebacking up data across longer distances, and may thus be more complex.

The key to achieving high availability is redundancy, including hardware redundancy, network redundancy anddata center redundancy. SAP HANA provides several levels of defense against failure-related outages:

1 Hardware Redundancy – SAP HANA appliance vendors offer multiple layers of redundant hardware, softwareand network components, such as redundant power supplies and fans, enterprise grade error-correctingmemories, fully redundant network switches and routers, and uninterrupted power supply (UPS). Diskstorage systems use batteries to guarantee writing even in the presence of power failure, and use striping andmirroring to provide redundancy for automatic recovery from disk failures. Generally speaking, all theseredundancy solutions are transparent to SAP HANA's operation, but they form part of the defense againstsystem outage due to single component failures.

2 Software – SAP HANA is based on SUSE Linux Enterprise 11 for SAP and includes security pre-configurations(for example, minimal network services). Additionally, the SAP HANA system software also includes awatchdog function, which automatically restarts configured services (index server, name server, and so on),in case of detected stoppage (killed or crashed).

3 Persistence – SAP HANA persists transaction logs, savepoints and snapshots to support system restart andrecovery from host failures, with minimal delay and without loss of data.

4 Standby and Failover – Separate, dedicated standby hosts are used for failover, in case of failure of theprimary, active hosts. This improves the availability by significantly reducing the recovery time from anoutage.

SAP HANA High Availability Support

As an in-memory database, SAP HANA is not only concerned with maintaining the reliability of its data in the eventof failures, but also with resuming operations with most of that data loaded back in memory as quickly as possible.

SAP HANA supports the following recovery measures from failures:

● Disaster recovery support:





○ Backups: Periodic saving of database copies in safe place.○ Storage replication: Continuous replication (mirroring) between primary storage and backup storage over

a network (may be synchronous).○ System replication: Continuous update of secondary system by primary system, including in-memory

table loading.● Fault recovery support:

○ Service auto-restart: Automatic restart of stopped services on host (watchdog).○ Host auto-failover: Automatic failover from crashed host to standby host in the same system.

Using Secondary Servers for Non-Productive systems

With SAP HANA system replication you can use the servers on the secondary system for non-productive SAPHANA systems under the following conditions:

● Table pre-load is turned off in the secondary system.● The secondary system uses its own disk infrastructure. In the case of single node systems this means, the

local disk infrastructure needs to be doubled.● The non-productive systems are stopped with the takeover to the productive secondary.

Related Links







3.1.3 SAP HANA Replication Technologies

3.1.3.1 IntroductionIn-memory reporting and analyzing of business data requires the replication of the data from a source system tothe SAP HANA database. This section provides an overview of the possible replication methods that are availablefor the SAP HANA appliance. It also describes the application fields and lists the main components required foreach method.

The figure above focuses on the task of loading business data from a source system to the SAP HANA database.

The methods for performing data replication are shown in the figure below. The main components involved in allreplication scenarios are:

● SAP HANA appliance, consisting of the SAP HANA database and SAP HANA studio, which is used toadminister the appliance. User interfaces, such as SAP BusinessObjects Dashboards or Web Intelligence, arenot part of the appliance software.

● Source system● Software components supporting the data replication

The software components that support different methods of data replication are described in the followingreplication scenarios.


SAP HANA Technical Operations ManualAdministering and Operating SAP HANA Data Provisioning Technologies



SAP Sybase Replication Server (SRS) is a sophisticated transactional data movement product that movesand synchronizes data across the enterprise without the limitation of geographical distance, to meetdemanding requirements in the enterprise such as guaranteed data delivery, real-time business intelligence

and zero operational downtime. SRS facilitates this by non-intrusively handling data at the source and target,while ensuring high performance and transactional integrity.

Related Links

Product Availability Matrix (PAM) (search for SAP HANA)

3.1.3.2 Trigger-Based Replication (SAP LandscapeTransformation (LT) Replication Server)

The Trigger-Based Replication method uses the SAP Landscape Transformation (LT) Replication Servercomponent to pass data from the source system to the SAP HANA database target system.

Initial Load and Simultaneous Delta Replication

The initial load of business data is initiated using the SAP HANA studio. The initial load message is sent from theSAP HANA system to the SLT system, which in turn passes the initialization message to the ERP system.Furthermore, the SLT system initiates the set-up of replication log tables in the database of the ERP system foreach table to be replicated. After the transaction tables are completed, the SLT system begins a multi-threadedreplication of data to the target system, which enables high speed d ata transfer.







The initial load of data can be executed while the source system is active. The system load that this processcauses can be controlled by adjusting the number of worker threads performing the initial replication.

In parallel to the initial load, by means of database-specific triggers, the SLT system begins detecting any datachanges that occur while the initial load process is running. These changes are already recorded in logging tablesduring the initial load phase and are propagated during the replication phase to the target SAP HANA system afterthe initial load has been completed. The multi-version concurrency control (MVCC) of the SAP HANA databaseprevents issues that might be caused by the overlapping of the initial load process and new database transactions

Continuous Delta Replication After Initial Load

After the initial load process has completed, the SLT system continues to monitor the transaction tables in theERP system, and replicates data changes in the source system to the SAP HANA system in near real time.

Required Software Components

This replication method requires the following component:

● SAP Landscape Transformation: this controls the entire replication process by triggering the initial load andcoordinating the delta replication.

Installation considerations

The SLT system can be installed in the ways shown below. You can select between these options depending onyour current system landscape and the software versions in your landscape:

● Installation on your ERP system● Installation on a standalone SAP system (recommended setup)

Related Links

SAP HANA Installation Guide – Trigger-Based Replication (SLT)

3.1.3.3 SAP HANA Direct Extractor Connection (DXC)

The SAP HANA Direct Extractor Connection (DXC) is a means for providing out-of-the-box foundational datamodels to SAP HANA, which are based on SAP Business Suite entities. DXC is also a data acquisition method forSAP HANA. The rationale for DXC is essentially simple, low TCO data acquisition for SAP HANA leveragingexisting delivered data models.

Customer projects may face significant complexity in modeling entities in SAP Business Suite systems. In manycases, data from different areas in SAP Business Suite systems requires application logic to appropriatelyrepresent the state of business documents. SAP Business Content DataSource Extractors have been available formany years as a basis for data modeling and data acquisition for SAP Business Warehouse; now with DXC, theseSAP Business Content DataSource Extractors are available to deliver data directly to SAP HANA.

DXC is a batch-driven data acquisition technique; it should be considered as a form of extraction, transformationand load although its transformation capabilities are limited to user exit for extraction.

A key point about DXC is that in many use cases, batch-driven data acquisition at certain intervals is sufficient (forexample, every 15 minutes).



http://help.sap.com/hana/SAP_HANA_Installation_Guide_Trigger_Based_Replication_SLT_en.pdf



Overview of the DXC Rationale

●

Leverage pre-existing foundational data models of SAP Business Suite entities for use in SAP HANA data martscenarios:

○ Significantly reduces complexity of data modeling tasks in SAP HANA○ Speeds up timelines for SAP HANA implementation projects

● Provide semantically rich data from SAP Business Suite to SAP HANA:

○ Ensures that data appropriately represents the state of business documents from ERP○ Application logic to give the data the appropriate contextual meaning is already built into many extractors

● Simplicity/Low TCO:

○ Re-uses existing proprietary extraction, transformation, and load mechanism built into SAP BusinessSuite systems over a simple http(s) connection to SAP HANA

○ No additional server or application needed in system landscape● Change data capture (delta handling):

○ Efficient data acquisition – only bring new or changed data into SAP HANA○ DXC provides a mechanism to properly handle data from all delta processing types

Default DXC Configuration for SAP Business Suite

DXC is available in different configurations based on the SAP Business Suite system:

● The default configuration is available for SAP Business Suite systems based on SAP NetWeaver 7.0 or higher– such as ECC 6.0.

● The alternative configuration is available for SAP Business Suite systems based on releases lower than SAPNetWeaver 7.0 – such as SAP ERP 4.6, for example.

An SAP Business Suite system is based on SAP NetWeaver. As of SAP NetWeaver version 7.0, SAP BusinessWarehouse (BW) is part of SAP NetWeaver itself, which means a BW system exists inside SAP Business Suitesystems such as ERP (ECC 6.0 or higher). This BW system is referred to as an “embedded BW system”. Typically,this embedded BW system inside SAP Business Suite systems is actually not utilized, since most customers whorun BW have it installed on a separate server, and they rely on that one. With the default DXC configuration, weutilize the scheduling and monitoring features of this embedded BW system, but do not utilize its other aspectssuch as storing data, data warehousing, or reporting / BI. DXC extraction processing essentially bypasses thenormal dataflow, and instead sends data to SAP HANA. The following illustration depicts the default configurationof DXC.





An In-Memory DataStore Object (IMDSO) is generated in SAP HANA, which directly corresponds to the structureof the DataSource you are working with. This IMDSO consists of several tables and an activation mechanism. Theactive data table of the IMDSO can be utilized as a basis for building data models in SAP HANA (attribute views,analytical views, and calculation views).

Data is transferred from the source SAP Business Suite system using an HTTP connection. Generally, theextraction and load process is virtually the same as when extracting and loading SAP Business Warehouse – yourely on InfoPackage scheduling, the data load monitor, process chains, etc. – which are all well-known fromoperating SAP Business Warehouse.

Note

DXC does not require BW on SAP HANA. Also with DXC, data is not loaded into the embedded BW system.Instead, data is redirected into SAP HANA.

Related Links

SAP HANA Direct Extractor Connection Implementation Guide

Editing DataSources and Application Component Hierarchies



http://help.sap.com/saphelp_nw04/helpdata/en/49/ae67401d4988448036b180dc9ec1e6/frameset.htm

http://help.sap.com/hana/SAP_HANA_Direct_Extractor_Connection_Implementation_Guide_en.pdf



Enhancing DataSources

3.1.3.4 ETL-Based Replication (SAP Data Services)

Extraction-Transformation-Load (ETL) based data replication uses SAP Data Services (referred to as DataServices from now on) to load the relevant business data from the source system, SAP ERP, and replicate it to thetarget, SAP HANA database. This method enables you to read the required business data on the level of theapplication layer. You deploy this method by defining data flows in Data Services and scheduling the replicationjobs.

Since this method uses batch processing, it also permits data checks, transformations, synchronizing withadditional data providers, and the merging of data streams.

The figure above gives an overview of the ETL-based replication method. Here, data replication is operated byData Services. Its main components are the Data Services Designer, where you model the data flow, and the DataServices Job Server for the execution of the replication jobs. An additional repository is used to store themetadata and the job definitions.

Data Flow

As for any replication scenario you have to define a series of parameters for the two systems involved. UtilizingData Services you have to set up datastores to define such parameters. You use the Designer to set updatastores.

Datastore Setup



http://help.sap.com/saphelp_nw70/helpdata/en/6e/fe6e420f00d242e10000000a1550b0/content.htm



Setting up a datastore for the source system SAP ERP, choose SAP Applications for the type of datastore, andspecify the address of the system, the user name and password allowing Data Services to access the system.Additional settings depend on the type of SAP ERP objects to be read.

For the target system of the replication, the SAP HANA database, you have to set up a separate datastore as donefor the source system.

Data Flow Modeling

Once datastores are set up, Data Services can connect to the source system by RFC. Based on the metadataimported from the ABAP Data Dictionary to Data Services, you can determine the business data to be replicated.Data Services offers replication functions for a variety of data source types. However, for the replication of SAPERP data to SAP HANA database, we recommend you to use extractors.

Note

● You must apply SAP Note 1522554 to fully benefit from the extractor support.● In the source system, the extractors must be released for the replication access by Data Services. In

addition, you have to indicate the primary key, such as the GUID, to enable the correct replication.● The extractors must support delta handling.

Choose the extractors that are relevant for the replication job.

Model the data flow for each extractor you have selected: indicate the source for the data flow, which is theextractor. For the target of the replication, choose a template table, which is then used in the SAP HANA databaseto store the replaced data.

Data Flow for Initial Load and Update

Both the initial load of business data from the source system into SAP HANA database as well as updating thereplicated data (delta handling) is done using SAP Data Services. The initial load can be set up modeling a simpledata flow from source to target. For the update, in most cases, the data flow is enhanced by a delta handlingelement, such as Map_CDC_Operation or Table_Comparison Transform . It depends on the environment andthe requested setup of the target tables which data flow design best serves your requirements.

Although we recommend you to use delta supporting extractors, you can also use SAP ABAP tables.

Replication Job Schedule

Since you can schedule the replication jobs when using Data Services, this method is suitable where the sourcesystem must be protected from additional load during the main business hours. In this way, you can shift the

replication workload, for example, to the night. As a result, the data that is available for reporting alwaysrepresents the state reached by the time when the latest replication job was started.

Use the Management Console, which comes with Data Services, to schedule replication jobs. You can choosefrom different tools and methods for the scheduling. You can also use the Management Console to monitor thereplication process.

Required Software Components

This replication method requires the following main components:

● SAP HANA database● SAP Data Services (contains Information Platform Services)

Related Links






Product Availability Matrix (PAM) (search for SAP HANA)

Enterprise Information Management on SAP Help Portal

3.1.3.5 Log-Based Replication (SAP Sybase ReplicationServer)

SAP Sybase Replication Server (SRS) is a sophisticated transactional data movement product that moves andsynchronizes data across the enterprise without the limitation of geographical distance, to meet demandingrequirements in the enterprise such as guaranteed data delivery, real-time business intelligence and zerooperational downtime. SRS facilitates this by non-intrusively handling data at the source and target, whileensuring high performance and transactional integrity.

SRS enables you to replicate data into an SAP HANA database from these primary databases:

● Adaptive Server● Oracle● Microsoft SQL Server● DB2 UDB

It also supports the initial load of data as well as continuous real-time transactional replication from thesedatabases to the SAP HANA database. SRS supports replication of data from non-SAP applications.

These are the components required to implement a PrimaryDB-to-SAP-HANA database replication system:



http://help.sap.com/boeim/




● A primary data server (SAP Sybase Adaptive Server, Oracle, DB2 UDB, MSSQL Server)● A replicate SAP HANA database data server● A Replication Server ® (with ExpressConnect for SAP HANA database)● The Replication Server Options component (this component is not required for ASE Primary DB to SAP

HANA): Replication Agent for MSSQL or DB2 or Oracle

Note

License Requirements:

You can use these licenses for replication into the SAP HANA database:

● Separately purchase SAP Sybase Replication Server, SAP HANA edition, for replicating from multiple datasources. This license includes all components required to provision data from UDB DB2, Oracle, or MSSQLinto the SAP HANA database.

●

Alternatively, when you buy the Real-time-data edition for SAP HANA, you automatically receive a licensefor SAP Sybase Replication Server, SAP HANA edition.

Individual components can also be licensed separately for replication from UDB DB2, Oracle, or MSSQL intothe SAP HANA database through the SAP Sybase Replication Server, option for SAP HANA. A prerequisite forthis is that you must have SAP Sybase Replication Server, enterprise edition.

Related Links

Sybase Product Documentation

3.1.3.6 Comparison of Replication Methods

This table compares the key features of each replication method.

Capability Trigger-BasedReplication

SLT Replication)

ETL-Based Replication

Data Services 4.0 –SP2)

Extractor-based DataAcquisition

DXC)

Release coverage SAP R/3 4.6C - SAP ERP6.0 (EHP06)

All other ABAP-based SAPApplications (Basis 4.6C-NW7.02)

ERP 4.6c - SAP ERP 6.0 SAP Business Suitesystems based onNetWeaver ABAP 4.6C orhigher

Unicode/Non-Unicode Yes Yes Yes

MDMP Partial (If table containsonly ASCII characters orlanguage key is included)

Partial (1) Yes – via How to Guide

Transparent Tables Yes Yes Yes- via generic Data

Source



http://sybooks.sybase.com/sybooks/sybooks.xhtml;jsessionid=pwschrsahesz?c=categories




SLT Replication)


Data Services 4.0 –

SP2)


DXC)

Cluster & Pool Tables Yes Yes Yes- via generic DataSource

Non-SAP Sources Yes (for SAP supportedDBs only)

Yes No

Compressed Values DBTable

Yes Yes Yes- via generic DataSource

Row Compression DB

Table

Yes Yes Yes- via generic Data

Source

DB Support (Source side) All SAP supported DBs,incl. ASE

All SAP supported DBs,incl. ASE, and others: seePAM for full list

(no MaxDB support)

All SAP supported DBs

OS Support (Source side) All SAP supported OS All OS supported underERP (NO impact of sourceOS on Data Services)

All OS supported underSAP Business Suitesystems

Transactional Integrity No No Yes

Multi-System Support Multiple source systemsto multiple SAP HANAinstances

Multiple source systems Multiple source systems

Workload balancing(parallelization ofreplication)

Yes Yes Yes

Real-time and/orscheduled replication

Real-time and scheduled(on table level)

Scheduled Scheduled or Event driven

Initial Load & Deltareplication

Initial load, initial load +delta replication forrelevant tables

Initial load + deltareplication (for tablebased needs deltainformation throughtimestamp column orthrough delta enabledextractors)

Not recommended for usewith DataSourceextractors with delta

processing types AIM, AIE,

Initial load + deltareplication, for all deltaprocessing types includingAIM, AIE, AIED, AIMD,ADD, ADDD, CUBE etc.






SLT Replication)


Data Services 4.0 –

SP2)


DXC)

AIED, AIMD, ADD, ADDD,and CUBE

Transformationcapabilities

Capabilities for filteringand transforming data, aswell as data scrambling.Data filtering can be doneeither via selectivetriggers or via replicationconfiguration settings

Complete ETL engine fromsimple functions to verycomplex transformations

Limited for extraction, viauser exits

Access to performancestatistics

Support dashboard Via Data Services ownManagement Console orthrough the integrationwith SAP SolutionManager

Via Monitoring details Tr:RSMO and via Table View:“M_Extractors” in SAPHANA studio

Access to trouble shootingfeature

Yes Via Data Services ownManagement Console orthrough the integrationwith SAP SolutionManager

Yes, Via Monitoring detailsTr: RSMO, via Table View:“M_Extractors” in SAPHANA studio, and alertswhich can be set instatistics serverconfiguration

(1) SAP Data Services will need a fixed code page for each run. In order to process MDMP, the same job will needto get executed multiple times, each time with a different code page and with a WHERE clause on the languagekey. This would only be manageable for a limited number of code pages.

This table gives an overview of the capabilities of SAP Sybase Replication Server (SRS):

Feature/Capability SAP Sybase Replication Server

SRS)

Applications (SAP/non-SAP) Application-independent, DB-specific. However, SAPBusiness Suite is not supported.

Table/Database Level Replication Yes

Extractors/Data Access @Interface -

Technology Log-based

Connectivity Optimized to SAP HANA ODBC

SAP/Non-SAP Data Sources Both

Transformations/Mapping Yes





3.2.2 Monitoring components for SAP HANA Direct ExtractorConnection (DXC)

For more information about monitoring the SAP HANA Direct Extractor Connection, see SAP HANA DirectExtractor Connection Implementation Guide .

Related Links


3.2.3 Monitoring Components for ETL-Based Replication(SAP Data Services)

For information about monitoring SAP Data Services, see:

● SAP Data Services Management Console GuideInformation about how to use SAP Data Services Administrator and SAP Data Services Metadata Reports.

● SAP Data Services Administrator's GuideInformation about administrative tasks such as monitoring, life cycle management, security, and so on.

● SAP Data Services Performance Optimization GuideInformation about how to improve the performance of SAP Data Services.

3.3 SAP HANA Administration Overview

You administer the SAP HANA system landscape by administering the SAP HANA components:

● Administering comp onents for Trigger-Based Replication: SA P LT (Landscape Transformation) ReplicationServer

● Administering comp onents for ETL-Based Replication: SAP Data Se rvices● Administering components for SAP HANA Direct Extractor Connection (DXC)

3.3.1 Administrating Components for Trigger-BasedReplication (SAP LT Replication Server)

For information abou t administering the SAP LT (Landscape Transformation) Repl ication Server, see the SAPLandscape Transformation for SAP HANA - Technical Operations Manual .



http://help.sap.com/businessobject/product_guides/sbods42/en/ds_42_admin_en.pdf

http://help.sap.com/businessobject/product_guides/sbods42/en/ds_42_mgmt_cons_en.pdf


http://help.sap.com/hana/SAP_Landscape_Transformation_for_SAP_HANA_Operations_Guide_en.pdf

http://help.sap.com/hana/SAP_Landscape_Transformation_for_SAP_HANA_Operations_Guide_en.pdf

http://help.sap.com/businessobject/product_guides/sbods42/en/ds_42_perf_opt_en.pdf

http://help.sap.com/businessobject/product_guides/sbods42/en/ds_42_admin_en.pdf

http://help.sap.com/businessobject/product_guides/sbods42/en/ds_42_mgmt_cons_en.pdf




3.3.2 Administrating Components for SAP HANA DirectExtractor Connection (DXC)

For information about administering the SAP HANA Direct Extractor Connection (DXC), see, SAP HANA DirectExtractor Connection Implementation Guide

3.3.3 Administrating Components for ETL-Based Replication(SAP Data Services)

For information about administrating SAP Data Services components, see the following guides:

● Management Console Guide SAP Data Services XI 4.0 (14.0.0)● SAP Data Services Administration Guide● Information platform services Administration Guide● SAP Data Services Upgrade Guide

3.4 Starting the Software Update Manager (SUM) for S APHANA

For information about starting the Software Update Manager (SUM) for SAP HANA see the SAP HANA AutomatedUpdate Guide -> Automated Update -> Performing an Automated Update

3.5 Ba ckup and Recovery of SAP H ANA ReplicationTechnol ogies

You backup and recover the SAP HANA system landscape by extending the backup and recovery strategy toinclude the SAP HANA components as well as the SAP HANA database:

● Backup and Recovery for the Trigger-Based Replication components: SAP LT (Landscape Transformation)Replicator

● Backup and Recovery for SAP HANA Direct Extractor Connection (DXC)● Backup and Recovery for ETL-Based Replication components: Data Services



https://service.sap.com/~sapidb/011000358700000604952011D

http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_ips_admin_en.pdf

http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_ds_admin_en.pdf



https://service.sap.com/~sapidb/011000358700001323242010E

http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_ips_admin_en.pdf


http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_ds_mgmt_cons_en.pdf





3.5.1 Backup and Recovery for the Trigger-Based Replicationcomponents (SAP LT Replication Server)

For information about backup and recovery for the SAP LT (Landscape Transformation) Replication Server,observe the following:

● The SAP LT (Lan dscape Transformation) Replication Server creates a schema in the SAP HANA databasecalled SYS_REPL where the replication control tables are stored (RS_* tables, to store replication status forexample).

● These tables are part of the normal database backup/recovery.● Recovery scenarios:

○ If the database is recovered to the latest consistent state, no further action is necessary, the replicationautomatically resumes (as the jobs are not running on the SAP HANA hardware).

○ If the database is recovered to an earlier point in time (recovery of data backup with clear log option),initial load and replication have to be started again.

3.5.2 Backup and Recovery for the SAP HANA DirectExtractor Connection (DXC)

The architecture of DXC involves components implemented in the SAP Business Suite system and also in SAPHANA. Thus, a significant amount of configuration data, metadata, and the state of the mechanisms for deltahandling (change data capture) are stored in the SAP Business Suite system. Of course, your SAP Business Suitesystem must be backed up regularly.

● A schema is created for each SAP Business Suite system connected to SAP HANA via DXC, and for eachDataSource a corresponding In-Memory DataStore Object is created in SAP HANA.

● These In-Memory DataStore Objects are be part of any normal SAP HANA database recovery.● Recovery scenarios:

○ In any recovery scenario, data consistency must be maintained between the SAP Business Suite systemand SAP HANA.

○ If the SAP Business Suite system is recovered to a point-in-time, in order to ensure that data in the In-Memory DataStore Objects in SAP HANA are consistent with the SAP Business Suite system, the data inthe In-Memory DataStore Objects in SAP HANA should be deleted and a delta initialization should be

performed for all DataSources in use in SAP HANA from that SAP Business Suite system.○ Similarly, if the SAP HANA database is recovered to a point-in-time, in order to ensure that data in the In-

Memory DataStore Objects in SAP HANA are consistent with the SAP Business Suite system, the data inthe In-Memory DataStore Objects in SAP HANA should be deleted and a delta initialization should beperformed for all DataSources in use in SAP HANA from that SAP Business Suite system.

Note

Delta initialization typically involves loading historical data, and can be significantly time-consuming.This should be factored into business continuity planning

Related Links




http://help.sap.com/hana/SAP_HANA_DXC_Implementation_Guide_en.pdf

http://help.sap.com/hana/SAP_HANA_DXC_Implementation_Guide_en.pdf



Information on Delta Initialization

3.5.3 Backup and Recovery for the ETL-Based Replicationcomponents (SAP Data Services)

For information about backup and recovery for SAP Data Services, observe the following:

● SAP Data Services stores its own metadata in a relational database (currently not the SAP HANA database).This metadata is the definition of the source and target connections, the mappings and transformations, theworkflows with load order and so on. Backup this database regularly.

● If the SAP HANA database needs to be recovered, replication can resume without any further user interaction.Data Services provides batch loading for SAP HANA database, so no further user interaction would be

needed. The next time a batch load is started, it will be loaded into the database again.

3.6 Security for the SAP HANA System Landscape

You ensure security for your SAP HANA system landscape by ensuring security of the SAP HANA components:

For more information, see:

● SAP HANA Se curity Guide

● SAP HANA Security Guide - Trigger-Based Replication (SLT)● SAP HANA Se curity Guides - ETL-Based Replication (D ata Services)

○ SAP Data Services Administrator’s Guide-> Sec urity

○ SAP D ata Services Administrato r’s Guide-> User Rights and management





http://help.sap.com/hana/SAP_HANA_SLT_Security_Guide_en.pdf




http://help.sap.com/hana/SAP_HANA_SLT_Security_Guide_en.pdf


http://help.sap.com/saphelp_erp60_sp/helpdata/en/80/1a65dce07211d2acb80000e829fbfe/frameset.htm



4 SAP HANA Data Management

You use the SAP HANA modeler, which is accessible as a perspective of the SAP HANA studio, for modeling andmanaging SAP HANA data. It allows technical users to create new or modify existing models of data. In addition,the initial configuration of the data replication is done in the SAP HANA modeler.

4.1 Configuring Data Replication

Configure data replication to provide the necessary metadata and data to the SAP HANA system. You need toperform the following steps:

● Load table metadata from the data provider systems (source systems) into the SAP HANA database (targetsystem) for all tables of the source system or for a subset of tables

● Load data (initial load) from the data provider s ystems (source systems) in to the SAP HANA database (targetsystem) for a selection of tables

● Start continuous replication of data changes from the data provider systems (source systems) into the SAPHANA database (target system) for a selected subset of tables

Once the metadata and data are loaded to the SAP HANA system, you can create views and reports based onthese metadata and data, as described in Modeling Data .

For more information, see the SAP HANA Developer Guide , chapters:

●

Importing Metadata○ Mass Import of Metadata○ Selective Import of Metadata

● Provisioning Data

4.2 Modeling Data

You use the SAP HANA modeler for modeling and managing SAP HANA data.

For more information, see the SAP HANA Developer Guide .

4.3 Modeling and Data Provisioning for ETL-BasedReplication (SAP Data Services)

When using the ETL-Based Replication technology by SAP Data Services, you can also model ERP data by meansof Data Services modeling tools. The following documents describe the modeling and data provisioning steps youhave to do in SAP Data services:

SAP HANA Technical Operations ManualSAP HANA Data Management


http://help.sap.com/hana/SAP_HANA_Developer_Guide_en.pdf





● SAP Data Services Administrator’s Guide -> Server Management -> To configure SAP HANA ODBC● SAP Data Services Reference Guide -> SAP HANA target table options● SAP Data Services Reference Guide -> Database datastores -> SAP HANA● Designer Guide SAP Data Services

Describes how to set up a job in the Designer to connect to any database● Reference Guide SAP Data Services

Describes the options for setting up connections to the SAP HANA database● Supplement for SAP Data Services

Describes all interactions with other SAP applications

Related Links

Enterprise Information Management on SAP Help Portal


SAP HANA Technical Operations ManualSAP HANA Data Management

http://help.sap.com/bods/



5 SAP liveCache on SAP HANA

You can run SAP liveCache on SAP HANA, lowering total cost of ownership and taking advantage of SAP HANAfeatures.

SAP liveCache is an in-memory object store technology that is used to speed up material planning scenarios inSAP Supply Chain Management (SCM). It is now offered as an add-on for SAP HANA.

There are a number of advantages to running SAP liveCache as part of SAP HANA:

● Only one database needs to be administered, which reduces setup and maintenance● Backup and recovery is simplified:

○ There is no longer a need for separate backups○ Inconsistencies that could arise from separate backups can be avoided

●

SAP liveCache can take advantage of existing SAP HANA capabilities like performance and high availability.

Supported Scenarios

The following scenarios are supported:

● Single host scenario: The SAP HANA database runs on a single host including SAP liveCache● Scale out scenario: SAP liveCache runs on a dedicated, separate slave host in a distributed SAP HANA

system.

In a scale-out system, a standby host must be equipped so that it can take over the operation of any of thefailed hosts in the failover group. In the case of a failed host, which was a dedicated liveCache host, with areduced set of memory or CPU features, it may not be reliably used as a standby host for any hosts in thefailover group.

Note

There is no standalone SAP liveCache based on SAP HANA technology. This means that you cannot replaceyour standalone SAP liveCache based on MaxDB technology with a standalone SAP liveCache based on SAPHANA technology.

Monitoring SAP liveCache in SAP HANA Studio

You can use both the DBACockpit for SAP HANA and the SAP HANA studio to monitor SAP liveCache. Thefollowing system views allow you to monitor run time information in the SAP HANA studio:

● M_LIVECACHE_OMS_VERSIONS● M_LIVECACHE_PROCEDURE_STATISTICS● M_LIVECACHE_CONTAINER_STATISTICS● M_LIVECACHE_SCHEMA_STATISTICS● M_LIVECACHE_LOCKS

SAP HANA Technical Operations ManualSAP liveCache on SAP HANA




www.sap.com/contactsap

© 2013 SAP AG or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in anyform or for any purpose without the express permission of SAP AG.The information contained herein may be changed without priornotice.Some software products marketed by SAP AG and its distributorscontain proprietary software components of other softwarevendors. National product specifications may vary.These materials are provided by SAP AG and its affiliatedcompanies ("SAP Group") for informational purposes only, without

http://www.sap.com/contactsap

SAP_HANA_Technical_Operations_Manual_en[1].pdf

Documents

Transcript of SAP_HANA_Technical_Operations_Manual_en[1].pdf