SAP Innovation Summer Camp Come with a Curiosity – …fm.sap.com/data/UPLOAD/files/03Infrastructure Track... · SAP Innovation Summer Camp Come with a Curiosity ... SAP HANA System

SAP Innovation Summer Camp

Come with a Curiosity – Leave with a Plan

July 12 - 13, 2012 | SAP Americas HQ

www.sap.com/sapsummercamp

© 2012 SAP AG. All rights reserved. 2

Disclaimer

This presentation outlines our general product direction and should not be relied on

in making a purchase decision. This presentation is not subject to your license

agreement or any other agreement with SAP. SAP has no obligation to pursue any

course of business outlined in this presentation or to develop or release any

functionality mentioned in this presentation. This presentation and SAP's strategy

and possible future developments are subject to change and may be changed by

SAP at any time for any reason without notice. This document is provided without a

warranty of any kind, either express or implied, including but not limited to, the

implied warranties of merchantability, fitness for a particular purpose, or non-

infringement. SAP assumes no responsibility for errors or omissions in this

document, except if such damages were caused by SAP intentionally or grossly

negligent.

Infrastructure Track Administration and Monitoring of HANA in the Data Center


Agenda

• Introduction to HANA System Administration and Monitoring from

HANA Studio and DBACockpit

• HANA Backup / Recovery: Power Failure Recovery for an In-Memory

Database

• SAP HANA User Management: User and Role concept

• SAP HANA Update and Patching: OS Patching, SP Stack Update,

Patching Revisions

• Available Remote Service Connections to HANA


Tools for Administration and Monitoring the HANA DB

SAP HANA Studio

DBACockpit for HANA

HDBSQL – command line

SAP Solution Manager


SAP HANA Studio First Start

The SAP HANA Studio is

an Eclipse based tool

delivered with SAP HANA

and provides an

environment for

administration , modeling

and data provisioning.


SAP HANA Studio Administration & Monitoring Console

Navigator

View

Properties

View

Administration

View


DBACockpit Overview Screen

• DBACockpit is SAP‘s ABAP based standard tool for DB monitoring

• It is available for the SAP HANA DB as of SAP_BASIS 7.02 SP 09 & Solution

Manager ST 710 SP 04


SAP HANA HDBSQL

• SAP HANA HDBSQL is a command line tool for entering and executing SQL statements,

executing database procedures, and querying information about SAP HANA databases. You

can use HDBSQL interactively or import commands from a file and execute them in the

background. You can access databases on your local computer and on remote computers.

Enter the following command:

hdbsql [<options>] -n <database_host> -i <instance_id> -u <database_user> -p

<database_user_password> “<command>“

or use the hdbuserstore to avoid specifying user and password in the command line:

hdbsql [<options>] -n <database_host> -i <instance_id> -U <user_store_key> “<command>“


SAP HANA System Monitoring in Solution Manager

Availability

Alerts (by Hostagent)

Configuration Alerts

(by DBACockpit)

Special HANA Alerts

like

- General Exceptions

- Table Exceptions

(by DBACockpit)

Availability metrics as of SolMan 7.1 SP03, all HANA alerts as of SP04

HANA Performance

- Memory Usage

- CPU Usage

(by DBACockpit)


HANA DB Processes

vml3341:/usr/sap/HA2/HDB02> ps -ef | grep ha2adm

ha2adm 8530 1 0 Dec07 ? 00:00:43 /usr/sap/HA2/HDB02/exe/sapstartsrv

pf=/usr/sap/HA2/SYS/profile/HA2_HDB02_vml3341 -D

ha2adm 10093 10092 0 17:41 pts/0 00:00:00 -sh

ha2adm 10168 10093 0 17:42 pts/0 00:00:00 ps -ef

ha2adm 10169 10093 0 17:42 pts/0 00:00:00 grep ha2adm

ha2adm 30205 1 0 Dec10 ? 00:00:00 sapstart pf=/usr/sap/HA2/SYS/profile/HA2_HDB02_vml3341

ha2adm 30281 30205 0 Dec10 ? 00:00:03 /usr/sap/HA2/HDB02/vml3341/trace/hdb.sapHA2_HDB02 -d -nw -f

/usr/sap/HA2/HDB02/vml3341/daemon.ini pf=/usr/sap/HA2/SYS/profile/HA2_HDB02_vml3341

ha2adm 31395 30281 0 Dec10 ? 00:01:16 hdbnameserver

ha2adm 31618 30281 0 Dec10 ? 00:00:16 hdbpreprocessor

ha2adm 31635 30281 0 Dec10 ? 00:08:19 hdbindexserver

ha2adm 31643 30281 0 Dec10 ? 00:07:49 hdbstatisticsserver


Configuration: Parameterfiles

SAP delivered configuration files created during the installation procedure:

•/usr/sap/<SID>/exe/linuxx86_64/<ver build>/config/<ININAME>

Customer configuration files:

• /usr/sap/<SID>/global/hdb/custom/config/<ININAME>


Agenda

• Introduction to HANA System Administration and Monitoring from HANA

Studio and DBACockpit

• HANA Backup / Recovery: Power Failure Recovery for an In-

Memory Database



Patching Revisions



SAP In-Memory Computing Engine

SAP HANA DB

In-Memory Data Is Regularly Saved to Disk

Data:

Replicated business data

Additional information,

such as modeling data

Kept in-memory to ensure maximum

performance

Log:

Information about data changes

Directly saved to persistent storage when

transaction is committed

Cyclical overwrite

Savepoint:

Changed data and log is written from

memory to persistent storage

Automatic and before each backup

At least every 5 minutes (customizable)

Memory

Data

Persistent Storage

Regular

automatic

savepoints

Information

about

data changes

Log

Volume Data

Volumes


Services with their own Persistency

Data and Log Volumes


SAP HANA Server

SAP HANA Backup/Recovery Online backup into files using a consistent snapshot

Shared Backup

Directory

(staging area)

Name Server

Data

Index Server

Statistics Server

DATA_BACKUP_0001

DATA_BACKUP_0002

DATA_BACKUP_0003

Data

Backup

Savepoint

Data

Backup

Savepoint

Data

Backup

Savepoint

DATA_BACKUP_0000

Each HANA Service has its own persistency – consistent snapshot backed up to Shared Directory


Backup and Recovery Backups during normal operation of the database: Summary

Data backups

(external backup

destination)

1

Log backups

(external backup

destination)

2

Crash

4

Most recent

log entries

from log area

3

Time

During normal operations, the ACID concept is maintained:

•Log entries written to persistent layer synchronously with each commit

•Savepoints flushing all changes to persistent layer


After a power failure, the database can be restarted and returned to its last consistent state*:

Scenario: Power Failure In-memory data and persistent storage

Savepoint:

Data is written

to disk (data area)

1 After each COMMIT,

log is written

to disk (log area)

2

Power failure

3

Time

• Last Savepoint is reloaded

• Uncommitted transactions are rolled back using the undo information contained in the Savepoint

• Committed transactions are rolled forward using the log

• Data is loaded back into memory

*Used for Recovery / Prerequisites: Last data Savepoint

Log between the last data Savepoint and the time of failure


Savepoint:

Data is written

to disk (data area)

2 After each COMMIT,

log is written

to disk (log area)

3

Disk crash with data volume damage

4

Scenario: Disk Crash with Data Volume Damage In-memory data and persistent storage

Time

Data Backup to

external Backup

destination

1

Restore after a disk crash*:

• Restore required backups from external destination

• Uncommitted transactions are rolled back using the undo information contained in the backup

• Committed transactions are rolled forward using the log

• Data is loaded back into memory

*Used for recovery / Prerequisites: Data backup

Log information since the data backup


Backup and Recovery Support for external backup tools

Further integration planned for HANA SPS5 (expected end 2012 – see SAP

Note 1642148):

Use of operation system pipes to connect directly to external backup tools

New interface standard to be defined: Backint for HANA

• Backint (in general) is an established standard by SAP and extended over time

• Extended for pipes for some years (e.g. Backint for MaxDB)

• Further minor extends for the use with SAP HANA

• Description and simulator already available to start adoption process on external tools now

First contacts:

Symantec (Netbackup)

IBM (Tivoli)

HP (Data Protector)

etc.


Backup and Recovery Data backups

Data backups save the content of the data area to a different location in the file

system. Depending on the usage scenario, this includes the replicated business

data from ERP and all the modeling data.

Data backups can be triggered manually via:

SAP HANA Studio

DBA Cockpit

SQL commands (command line)

Scheduling:

Using scripts (via the SQL interface)

Planning calendar in DBA Cockpit

Backup frequency

Regular data backups required, but no general guidelines available

(depends on the usage scenario)

Space requirements

Only occupied space is backed up


Backup and Recovery Advantages for Backups with HANA Kernel involvement

Structural knowledge of data in database kernel

Mini-verify of every page with relevant information during simple data and log backup

Header and Trailer verification of checksums ensures valid data in pages

Hardware problems soon recognized and can be treated early enough w/o further

implications to general data consistency

OS-related or external tools don’t offer this structural knowledge

Performance

Only occupied space is backed up

Throughput of up to 2 TB per hour reported

Check Backup

General possibility to check also backups with data knowledge in kernel

Still to be implemented


Backup Backup in SAP HANA Studio

HANA Database Backups can be executed via SAP HANA Studio:


Recovery Recovery in SAP HANA Studio

HANA Database Recovery can be executed from the SAP HANA Studio:


Log Modes

Normal:

• Recommended setting for HANA SPS3.

• Prerequisite for automated log backup.

Overwrite:

• Log can be overwritten after a savepoint was taken.

• Not recommended for production usage.


Agenda




Database



Patching Revisions



SAP HANA User Management

SAP HANA User and Role concept

The SAP HANA database allows for a fine granularity of access control, based on the user’s

tasks:

– Business end users, Modelers, DB Administrators, Replication Users, Support (read-only)

Roles are assigned to users, and roles can also be assigned to roles (creating a role

hierarchy)

Define and Create Roles

Assign Privileges to

Roles

Create Users

Assign Users to

Roles

SAP HANA provides the following options for authentication: Direct logon to SAP HANA database with user name and password

The SAP HANA database does authenticate users

Authentication using third-party authentication providers like Kerberos / Active Directory

An external services does authenticate users (e.g. Active Directory Server)

Can be used to integrated SAP HANA into single-sign-on landscape


User and Access Management User and role concept

Tool support:

Manual user, role and privilege management using SAP HANA studio

All user management functions in the SAP HANA DB are available via the SQL interface: • Scripting

• Connection of third-party user management/provisioning tools that support SQL


User and Access Management Data mart scenario

SAP ERP Database

SAP ERP

Data

Replication

Client

(Excel)

U1

SAP HANA Database

Client

(BOBJ Client)

U2

BOE Server

No user

replication!

Only data, but no user information is replicated

Individual users access data in the

SAP HANA database (using client tools)

Individual users need to be known in the SAP

HANA database


User and Access Management Authentication with SAP Business Objects

SAP HANA Database

User

Management

Client

(BOBJ Client)

U2

BOE Server

BOE User

Management

Manual

synchronization

Users must exist both in BOE server and in the SAP HANA database

(1) manual synchronization of users (2) with SAP Identity Management (IDM)

SAP HANA Database

User

Management

Client

(BOBJ Client)

U2

BOE Server

BOE User

Management

Active

Directory

or LDAP

SAP IDM

User information

held centrally

Provision

users

Import

users


Agenda




Database



Patching Revisions



SAP HANA Update & Patching

OS patching

•Pre-validated HW/OS stack configurations reduce risk of operating system SP update while leaving flexibility to implement important security patches released by Novell as soon as they are released.

SP Stack Update

•Implementation of SAP HANA SP Stack can be done automated using the SAP Software Update Manager for SAP HANA (SUM for SAP HANA), available with SL Toolset 1.0 SP02

Patching Revisions / SPs

•The implementation of intermediate patches / revisions / SPs, for example of the SAP HANA database component can be done individually following the corresponding documentation available at https://help.sap.com


SAP HANA SP Stack Update

SAP Software Update

Manager (SUM) for SAP

HANA integrates into the

look and feel of SAP HANA

monitoring and

administration by being

managed from inside SAP

HANA studio

SUM for SAP HANA

support update of all kind of

different components

included in a SAP HANA

support package stack,

while e.g. not relying on

other on-site ABAP

infrastructure.

The SAP HANA appliance from a maintenance point of view:

Provide automated SP Stack update procedure from within SAP HANA studio.


SAP HANA SP Stack Update – Process Description

SAP HANA appliance software

SAP HANA database & client

SAP HANA studio repository

SAP HANA load controller

SAP Host

Agent

SUM for SAP

HANA

SAP HANA studio

(Eclipse) LM

perspective

Maintenance Optimizer

Service Marketplace

All remote connections are done via secure web services.

1. Perform Software Update Manager for SAP HANA self-update

2. Detect components in the SAP HANA landscape

3. Get latest SP stack information from SMP

4. Download required component updates

5. Update components on the SAP HANA system

Internet


Agenda




Database



Patching Revisions



Remote Support Tools to HANA Database (see SAP Note

1635304)

HANA Host

Inte

rnet

SAP Customer

SolMan Host

SolMan 7.1 HANA Database

DBA Cockpit

HANA DB Studio

SAP GUI / Browser

Http Connect

R/3 Support

SAP Router

SSH / telnet / Netviewer

OS Console


Remote Access to Solution Manager

• HANA can be connected to Solution Manager 7.1 >= SP02

• Standard SAPGUI and HTTP connection to Solution Manager has to

be established (see SAP Note 962516)


Remote Connection via saprouter to HANA DB Studio

What is needed to connect from

SAP Network to customer network:

– Connection via sapstartsrv

on the HANA Server

to the Master Index Server

SAP HANA

Server

SAP Router

SAP

Network

Customer

Network



• Saprouter installation required at customer side

see also http://service.sap.com/serviceconnection

• Connection to customer HANA DB possible from SAP local HANA DB Studio

• New connection type „SAP HANA database“ in customer system data and STFK

• See note 1592925 (SAP HANA database service connections)

Port of sapstartsrv for HANA

(by default: 5<instno>13)

Port of HANA master indexserver

(by default: 3<instno>15)

http://service.sap.com/serviceconnection



• Specify a certain user which has no administrative roles:

•MONITORING

•Possible to look at historical data

(Schema _SYS_STATISTICS)

•PUBLIC

•Possible to look at Monitoring Views

(Schema SYS)


Remote Access to OS level

In difficulty support cases it might be necessary to have OS level access.

• For the HANA Linux systems a SSH or Telnet remote connection should be set up

(SAP Notes 1275351 + 1327257)

• For unattended access a Windows Terminal Server connection can be setup

(SAP Note 605795)

• For Windows based systems (potentially used for Business Objects components)

a Netviewer connection can be used (SAP Note 1036616). Netviewer requires

the customer to actively accept a connection request.


Remote Access to Further Components in HANA

Scenarios

• Business Objects Enterprise / BI Platform 4.0 can be connected to

Solution Manager 7.1 (SAP Note 962516)

R/3 support (SAP Note 812732)

HTTP Connect (SAP Note 592085)

• Business Objects Central Management Console (CMC)

HTTP Connect – URL access

• SAP Backend system and SLT system can be connected to

Solution Manager 7.1

R/3 support

HTTP Connect

Further Reading Public Documentation, Wikis, Communities, …


help.sap.com/hana


Public Links Around SAP HANA

www.sap.com/hana - official SAP HANA page with customer testimonials

www.experiencesaphana.com - SAP HANA collaboration space for customers

help.sap.com/hana_appliance - Official documentation

service.sap.com/HANA - Installation and Implementation knowledge

www.sdn.sap.com/irj/sdn/in-memory - SAP Developer Network for HANA

scn.sap.com/community/developer-center/hana - SAP HANA Developer Center

http://www.sap.com/hana

http://www.experiencesaphana.com/

http://help.sap.com/hana_appliance

http://help.sap.com/hana_appliance

http://service.sap.com/HANA

http://www.sdn.sap.com/irj/sdn/in-memory



http://scn.sap.com/community/developer-center/hana




Thank you

Contact information:

Frank Lukens

AGSA - CoE

DB Team Lead

610-661-7147

Documents

SAP Innovation Summer Camp Come with a Curiosity – …fm.sap.com/data/UPLOAD/files/03Infrastructure Track... · SAP Innovation Summer Camp Come with a Curiosity ... SAP HANA System