没有合适的资源?快使用搜索试试~ 我知道了~
首页SAP HANA 最佳实践
资源详情
资源评论
资源推荐

SAP HANA
BEST PRACTICES GUIDE
DRAFT VERSION - CONFIDENTIAL USE ONLY
Dr. Tristan Daude, Product Manager
INTRODUCTION
SAP HANA is a new and innovative in-memory database platform and SAP’s answer to the question on how to
analyse Big Data in near real time. HANA takes full advantage of all-new hardware technologies by combining
columnar data storage, massively parallel processing of modern CPUs and in-memory computing. This puts
HANA in a position to be able to support numerous use cases in the real-time analytics space. Above that, SAP
HANA can also be deployed as the underlying database of SAP Business Suite applications.
A HANA database is identified by an unique SID. Four so-called servers form a HANA database: Name Server,
Stats Server, XS Engine and Index Server. Each of these servers has its own data and log volume. In case of
increasing workloads, a HANA database can be scaled up by adding more memory and CPUs to the local node
it’s running on.
Figure 1: SAP HANA Single Node Configuration
There is also a scale-out option which works through adding additional nodes leading a single database being
spread across multiple nodes.

Figure 2: SAP HANA Multi Node Configuration
In order to protect against power failures and system crashes, HANA has the concept of persisting all changed
data of the four HANA servers along with their logfiles to disk as so-called savepoints. Those savepoints are
scheduled to happen periodically (typically every 5 minutes). Savepoints are consistent images of the database.
After a crash the in-memory database gets loaded from the last savepoint and is rolled forward to the latest
transaction using the externalized logfiles.
BACKING UP SAP HANA
There are basically three main backup options for SAP HANA:
File-level backup, where the data gets written to a local storage location
Local snapshots using storage-level snapshot technologies
Backint for HANA, which is a SAP-defined backup interface for connecting centralized 3
rd
party
backup solutions to backup HANA
As of now, Backint for HANA is the backup approach preferred by many HANA users as it is the only way for
connecting a SAP HANA landscape to the existing centralized backup solution in a SAP-certified way.
Commvault Simpana as a market leading solution for enterprise backup implements Backint for HANA as part
of the Simpana iDataAgent for SAP HANA. According to the standard, the agent is named “backint” and is
accessed via a logical link in a defined directory.
Data transfer in Backint for HANA works through named pipes. Communication between HANA and the backup
tool is done facilitated using the so-called input and output files. For instance, for a backint backup call, HANA
allocates named pipes and passes their full path via the input file. Once the backup has completed, Simpana
returns backup status information (like the backup IDs) and return codes via the output file back to HANA.

PREPARATION
Before the installation can start, we need to find out the SID of the SAP HANA database. Above that, we also
need to make sure that two directories exist which are required during and after installation:
SAPHANAEXE directory, which will hold the symbolic link to Simpana SAP HANA agent later-on
o /usr/sap/<SID>/SYS/global/hdb/opt
Backint for HANA agent configuration file directory
o /usr/sap/<SID>/SYS/global/hdb/opt/hdbconfig
If either one of these directories is missing, it needs to be created manually as user <SID>adm. This activity
needs to be repeated on all SAP HANA nodes in a multi-node environment.
INSTALLATION
Simpana SAP on HANA agent can be installed from command line or using push install. Remember, this needs
to be done on all SAP HANA nodes.
COMMAND LINE INSTALLATION
When running cvpkgadd, the agent is available for selection:
During installation specify:
/usr/sap/<SID>/SYS/global/hdb/opt as SAPHANAEXE directory
sapsys as OS group (alternatively, you can create and specify on own group, but need to assign it to
<SID>adm as secondary group)
After installation, the link to Simpana backint executable should be available:
PUSH INSTALL
After selecting the SAP HANA agent, make sure you enter the correct OS group (see above) before pushing out
the agent
剩余14页未读,继续阅读













安全验证
文档复制为VIP权益,开通VIP直接复制

评论1