Data Protection for SAP HANA Installing, configuring, and protecting

IBM Tivoli Storage Manager for
Enterprise Resource Planning
Data Protection for SAP HANA®
Installing, configuring, and protecting
data
Version 6.4.1
Description
Use this document to help you to install, configure, and protect SAP HANA data with IBM Tivoli Storage
Manager for Enterprise Resource Planning: Data Protection for SAP HANA. This version of Data Protection for
SAP HANA can be used in your existing Tivoli Storage Manager backup environment once all prerequisites have
been met.
Installation
Prerequisites
Before installing and configuring Data Protection for SAP HANA, verify that the following prerequisites are met:
•
SAP HANA SPS 05 revision 45 or later is available.
•
Tivoli Storage Manager API Version 5.5 or later is installed and configured on all SAP HANA nodes where
you are going to install and configure Data Protection for SAP HANA.
•
The SAP HANA database configuration is complete on the system where you are going to install and
configure Data Protection for SAP HANA.
•
SAP HANA HDB client is installed.
•
Installation is run using the root user ID for the appliance host operating system. During the installation
and configuration of Data Protection for SAP HANA, root access to the appliance host operating system is
required.
Data Protection for SAP HANA® V6.4.1 - Installing, configuring, and protecting data
Limitations
Data Protection for SAP HANA is not integrated with the Tivoli Storage Manager for Enterprise Resource
Planning Administration Assistant. The Administration Assistant cannot be used to configure and monitor Data
Protection for SAP HANA.
Installation
The Data Protection for SAP HANA installation package is delivered as a self-contained installer program. This
file uses the following name format:
6.4.1.0­TIV­TSMERP­HANA­Linux.bin
To install the software, complete the following steps:
1. Using the root user ID, log on to the SAP HANA host where you want to install Data Protection for SAP
HANA. Choose one of the following methods for installing:
I. Mount the DVD containing Data Protection for SAP HANA.
II. From the command line, change to the DVD directory where the installer is located. Enter the following
command to start the installer:
./6.4.1.0­TIV­TSMERP­HANA­Linux.bin
III. If you are logged on to the SAP HANA host with an X Windows System or X terminal the installation will
be started in graphical mode and will guide you through the installation process. Follow the screen
instructions to complete the installation. If you are using a non-graphical terminal during installation, a
console mode installation will be started.
IV. If you are installing from an file share directory, enter the following command to ensure that the installer
file has execute permissions:
chmod +x 6.4.1.0­TIV­TSMERP­HANA­Linux.bin
Illustration 1: Data Protection for SAP HANA Installation Welcome screen
Data Protection for SAP HANA® V6.4.1 - Installing, configuring, and protecting data
2.
Accept the license agreement and click Next. The Data Protection for SAP HANA will check if the
prerequisites are met before proceeding.
Illustration 2: Software License Agreement screen
Illustration 3: Pre-Installation Summary screen
Data Protection for SAP HANA® V6.4.1 - Installing, configuring, and protecting data
Illustration 4: Installation Completed screen
Installation results
During the installation, the following changes are automatically completed on the system where the software is
installed:
1. An entry is created in /etc/inittab that automatically starts the ProLE daemon on the system.
2. An entry is created in /etc/services for internal communication using port tdphana (57321).
3. Data Protection for SAP HANA is installed in the directory: /opt/tivoli/tsm/tdp_hana
Installation in silent mode using a response file
To automate the installation of Data Protection for SAP HANA in silent mode using a response file follow the
steps below. Installing the program in silent mode means you so not need to monitor the process or input any
details. The steps needed to create a response file to start the installation in silent mode are listed.
1. Create a response file for the installation in silent mode using the option “-i console” and “-r responsefile”, for
example:
./6.4.1.0­TIV­TSMERPHANA­CD­Linux.bin ­i console ­r responsefile
2. Silent mode installation using the previously recorded responsefile can be started using the option “-i silent”
followed by the option “-f” providing the name of your response file. For example:
./6.4.1.0­TIV­TSMERPHANA­CD­Linux.bin ­i silent ­f responsefile
Data Protection for SAP HANA® V6.4.1 - Installing, configuring, and protecting data
Uninstallation
To uninstall Data Protection for SAP HANA and remove all files that are associated with it, follow these steps:
1. Change directory to the uninstall subdirectory in the installation folder.
2. Enter the following command:
/opt/tivoli/tsm/tdp_hana/uninstall/uninstaller.bin
Results:
The uninstaller will remove Data Protection for SAP HANA from your system. Services that are installed and
used by Data Protection for SAP HANA will be stopped and removed.
Note: If RPM is used to uninstall Data Protection for SAP HANA the uninstallation program would remain on disk.
The Tivoli Storage Manager for ERP RPM packages that were installed as part of the setup procedure on other
SAP HANA nodes will remain on these nodes. To remove these packages, run the following command on the
SAP HANA nodes:
rpm ­e TIV­TSMERP­HANA
Setting up Data Protection for SAP HANA
Before Data Protection for SAP HANA can be used, it must be configured using the setup.sh script in the
installation directory. To run the setup.sh script, follow these steps:
1. Change to the Data Protection for SAP HANA installation directory:
cd /opt/tivoli/tsm/tdp_hana
2. Enter the following command to run the Data Protection for SAP HANA configuration script setup.sh with the
root user ID:
./setup.sh
The Data Protection for SAP HANA configuration files are installed in the configuration directory
/usr/sap/<SID>/SYS/global/hdb/opt/hdbconfig:
▪init<SID>.utl
▪init<SID>.bki
▪agent.lic (copy of the licence file stored in the Data Protection for SAP HANA
installation directory).
3. (Optional) From the command line, input the Tivoli Storage Manager node password for Data Protection for
SAP HANA :
i.Log on as the Data Protection for SAP HANA user <SID>adm. For example, for the SID
I53 this will be user i53adm.
ii.From a terminal, enter the following command:
/opt/tivoli/tsm/tdp_hana/hdbbackint ­p <full path to profile>/init<SID>.utl ­f password
iii.If the password for the Tivoli Storage Manager node has not been set with the
setup.sh script, you will be prompted to enter the password.
Data Protection for SAP HANA® V6.4.1 - Installing, configuring, and protecting data
Configuring Data Protection for SAP HANA
Data Protection for SAP HANA requires the Tivoli Storage Manager API configuration files dsm.sys and
dsm.opt to be configured. The server stanza in the dsm.sys file that is used for Data Protection for SAP HANA
should be created before proceeding to the configuration of Data Protection for SAP HANA.
The following information is requested when executing the Data Protection for SAP HANA configuration script
setup.sh.
1. Please enter the SAP HANA system ID [SID]:
The setup.sh script provides a proposal for the SAP HANA system ID. To accept the proposed value, press
enter.
2. Please enter instance number [00]:
For a typical configuration, the SAP HANA instance number is 00. You can accept the default value by pressing
enter, or override it with your input.
3. Enter the Please enter password for SYSTEM user:
The system user is the SAP HANA database administration user. The password of the system user is used
internally only in the setup.sh script. The password is not stored by Data Protection for SAP HANA.
4. You will be asked if you want to setup the Tivoli Storage Manager configuration. If you know how the Tivoli
Storage Manager server is configured, and how the Tivoli Storage Manager node is configured, answer yes. You
will be asked for Tivoli Storage Manager configuration parameters. Based on the information that is provided, the
configuration in the Data Protection for SAP HANA UTL-file is updated.
5.If you answer no, you must manually edit the Data Protection for SAP HANA UTL-file initSID.utl after the
setup.sh script finishes. You need to change the following Tivoli Storage Manager parameters in the server
section of this UTL-file:
SERVER server # Servername, as defined in dsm.sys
ADSMNODE NODE # Tivoli Storage Manager Nodename
BRBACKUPMGTCLASS MDB # Mgmt­Classes for database backup
BRARCHIVEMGTCLASS MLOG # Mgmt­Classes for redo log backup 6. If you answered yes, you will be asked if you want to use automatic password handling. If you choose
automatic password handing the Tivoli Storage Manager node password is stored by the Tivoli Storage Manager
API. When the Tivoli Storage Manager node password expires on the server, the Tivoli Storage Manager client
and server automatically negotiate a new password. The API in turn updates the password on the client. For this
feature the Tivoli Storage Manager node name must be specified in the server stanza in the dsm.sys file.
The other configuration option is to manually handle passwords. With this option the Tivoli Storage Manager
node password is stored in the Tivoli Storage Manager for the ERP configuration file. Once the password expires
it needs to be updated manually with the 'hdbbackint -f password' command.
7. Please enter the TSM server name as defined in dsm.sys:
The Data Protection for SAP HANA UTL-file initSID.utl parameter SERVER is updated with the Tivoli Storage
Manager server name. Data Protection for SAP HANA uses the Tivoli Storage Manager server name to backup
and restore data.
8. Please enter the TSM node name:
The Data Protection for SAP HANA UTL-file initSID.utl parameter ADSMNODE is updated with the Tivoli Storage
Manager node name. Data Protection for SAP HANA uses the Tivoli Storage Manager node name on the Tivoli
Storage Manager server to backup and restore data.
9. Please enter the TSM management class for database backups:
The Data Protection for SAP HANA UTL-file initSID.utl parameter BRBACKUPMGTCLASS is updated with this
Tivoli Storage Manager management class name. Data Protection for SAP HANA uses the Tivoli Storage
Manager management class on the Tivoli Storage Manager server to backup and restore the SAP HANA
Data Protection for SAP HANA® V6.4.1 - Installing, configuring, and protecting data
database.
10. Please enter the TSM management class for log file backups:
The Data Protection for SAP HANA UTL-file initSID.utl parameter BRARCHIVEMGTCLASS is updated with the
Tivoli Storage Manager management class name. Data Protection for SAP HANA uses the Tivoli Storage
Manager management class on the Tivoli Storage Manager server to backup and restore database redo log files.
11.You are prompted to set the password for the Tivoli Storage Manager node. After you enter the password, the
password is verified. For a scale-out system with automatic password handling this step is repeated for each
SAP HANA node that belongs to the scale-out system.
Additional configuration considerations
Tivoli Storage Manager client profile
Data Protection for SAP HANA requires the Tivoli Storage Manager server and the local Tivoli Storage Manager
client to be configured. For more information about these configuration tasks, see the configuration section of the
Tivoli Storage Manager for Enterprise Resource Planning Version 6.3 Installation and User's Guide. This
document is available online at:
http://pic.dhe.ibm.com/infocenter/tsminfo/v6r3/topic/com.ibm.itsm.erp.d oc/t_dperp_configuring_tsm.html
Data Protection for SAP HANA profile
The Data Protection for SAP HANA profile has the default name initSID.utl, where SID is the identifier of the SAP
HANA database instance. During the setup process this file is created in the directory
/usr/sap/SID/SYS/global/hdb/opt/hdbconfig, and the SAP HANA configuration is adjusted to use this
profile for backup and recovery operations.
Additional customizations are available according to the instructions in the Tivoli Storage Manager for Enterprise
Resource Planning Version 6.3 Installation and User's Guide available at:
http://pic.dhe.ibm.com/infocenter/tsminfo/v6r3/topic/com.ibm.itsm.erp.doc/c_dperp_c _opt_dpsapprofile.html
Special considerations for scale-out solutions
When Data Protection for SAP HANA is used to protect a scale-out solution, backup and restore operations run
simultaneously on all SAP HANA nodes. SAP requires that each SAP HANA node has access to all backups that
have been run by any SAP HANA node within the cluster. This results in the requirement that all data has to be
stored on a single Tivoli Storage Manager server.
For manual password handling all SAP HANA nodes must have an identical Tivoli Storage Manager
configuration. Ensure that the stanzas in dsm.sys that are referenced by the Tivoli Storage Manager for ERP
profile are identical. An example is shown below. Note that the parameter nodename in dsm.sys is commented
out.
Data Protection for SAP HANA® V6.4.1 - Installing, configuring, and protecting data
SAP HANA instance PRD
SAP HANA node 01
initPRD.utl
# TSM ERP profile
...
server TSM_SRV
...
adsmnode SAP­PRD
dsm.sys
servername TSM_SRV
...
* NODENAME node
SAP HANA node 04
initPRD.utl
# TSM ERP profile
...
server TSM_SRV
...
adsmnode SAP­PRD
dsm.sys
servername TSM_SRV
...
* NODENAME node
SAP HANA node 07
initPRD.utl
# TSM ERP profile
...
server TSM_SRV
...
adsmnode SAP­PRD
dsm.sys
servername TSM_SRV
...
* NODENAME node
Drawing 1: Example scenario - Data Protection for SAP HANA on scale-out solution with manual
password handling
If automatic password handling is used the stanzas in dsm.sys, that are referenced by the Tivoli Storage
Manager for the ERP profile must have unique Tivoli Storage Manager node names for each SAP HANA node.
Otherwise the stanzas must be identical. These Tivoli Storage Manager nodes are used for authentication
purposes. By using the Tivoli Storage Manager proxy node feature, the nodes gain access to a single Tivoli
Storage Manager node that holds the data for the entire SAP HANA instance. In the following sample the Tivoli
Storage Manager node SAP­PRD is used to store the backup of the entire SAP HANA database. The Tivoli
Storage Manager nodes SAP­PRD­01, SAP­PRD­04, and SAP­PRD­07 are used by SAP HANA nodes 01, 04,
and 07 to authenticate with the Tivoli Storage Manager server. These Tivoli Storage Manager nodes must have
proxy authority to the Tivoli Storage Manager node SAP­PRD. Similar configuration must be applied to all other
nodes within the SAP HANA scale-out system.
SAP HANA instance PRD
SAP HANA node 01
initPRD.utl
# TSM ERP profile
...
server TSM_SRV
...
asnode SAP­PRD
dsm.sys
servername TSM_SRV
...
NODENAME SAP­PRD­01
passwordaccess generate
SAP HANA node 04
initPRD.utl
# TSM ERP profile
...
server TSM_SRV
...
asnode SAP­PRD
dsm.sys
servername TSM_SRV
...
NODENAME SAP­PRD­04
passwordaccess generate
SAP HANA node 07
initPRD.utl
# TSM ERP profile
...
server TSM_SRV
...
asnode SAP­PRD
dsm.sys
servername TSM_SRV
...
NODENAME SAP­PRD­07
passwordaccess generate
Drawing 2: Example scenario - Data Protection for SAP HANA on scale-out solution with automatic
password handling
Data Protection for SAP HANA® V6.4.1 - Installing, configuring, and protecting data
Performance considerations
When SAP HANA runs a backup it sends the data for all SAP HANA services, such as nameserver and
indexserver in parallel from all nodes. If data is intended to go directly to tape, the number of allowed mount
points for the Tivoli Storage Manager node needs to be adjusted accordingly.
If data is stored in a disk storage pool first, and afterwards migrated to tape it should be considered that SAP
HANA expects data to be restored in the order determined by HANA. It is not possible for Tivoli Storage Manager
for ERP to optimize the restore order to reduce the number of tape seeks and mounts. If the data to be restored
for all nodes is located on a single tape drive this can lead to increased restore times or even deadlocks. Use
either disk storage pools or tapes with a sufficient number of mount points to avoid deadlock.
Expiration of obsolete backups
In contrast to V6.4.0 the profile keyword MAX_VERSIONS can not be used to delete obsolete backup
generations automatically. For Data Protection for SAP HANA 6.4.1 the expiration of backups can be controlled
with the attribute RETVER of the archive copy group that is used to store the backup data on the TSM server. To
keep 30 daily backups the RETVER attribute must be set to 30. Keep in mind that backups do expire even in
case there is no backup performed at some days.
Backing up log and data files
During the setup procedure the SAP HANA configuration is adjusted to use the 'BACKINT for SAP HANA'
interface to backup the redo logs. Once this change has been completed, SAP HANA regularly backs up the
redo logs to the Tivoli Storage Manager. The frequency of these backups can be adjusted with the SAP HANA
configuration parameter log_backup_timeout_s located in the persistence section of the global.ini configuration file. Refer to the SAP HANA documentation for further details about how to adjust this parameter.
A backup of the database can be started in two ways:
1. In the SAP HANA Studio, select the database instance. Right click the mouse to show the context menu and
select Back Up.
2. In the Backup Settings window, select the Backint option for Destination Type.
Illustration 5: Backup Settings panel
Data Protection for SAP HANA® V6.4.1 - Installing, configuring, and protecting data
3. On the command line use the SAP HANA SQL client 'hdbsql'. For example the command:
hdbsql ­i 53 ­n vhana06 ­u system ­p manager "backup data using backint ('DAILY')"
connects to the instance with number 53 on host vhana06, as user system with password manager and runs a
complete database backup.
Restoring and recovering Data Protection for SAP HANA
The entire restore and recovery process is driven from within the SAP HANA Studio. Refer to the SAP HANA
documentation for further details about how to restore and recover data. Complete the following steps:
1.In the SAP HANA Studio Navigator tab, right click to select the instance. Click Recovery.
Illustration 6: Recovery with
SAP HANA Studio
Note: If the database instance is still running, a message might be displayed. The message states that the
system has to be shut down. When you confirm the message, SAP HANA Studio automatically shuts down
the instance.
2. In the Specify Recovery Type window, choose the type of recovery that you want to run: most recent, pointin-time or restore of a backup with recovery of redo logs.
Illustration 7: Choosing Recovery Type with
SAP HANA Studio
Data Protection for SAP HANA® V6.4.1 - Installing, configuring, and protecting data
3. In the Locate Log Backups panel no input is required. The default location can be used.
4. Choose the backup to restore in the Select Data Backups panel. The list of backups is generated from the
SAP HANA recovery catalog. This catalog contains every backup that has been created. By selecting a specific
backup and pressing Check Availability it can be verified that the backup exists on the Tivoli Storage Manager
server.
Illustration 8: Select the backup to restore with SAP HANA Studio
5.Advance through the panels, and selecting appropriate options. Refer to the SAP HANA documentation for
further details.
Data Protection for SAP HANA® V6.4.1 - Installing, configuring, and protecting data
©Copyright IBM Corporation 2012, 2013 . U.S. Government Users Restricted Rights - Use, duplica tion or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM, the IBM logo, ibm.com, Tivoli, and System Storage are trademarks of International Business
Machines Corp., registered in many jurisdictions worldwide. Other product and service names
might be trademarks of IBM or other companies. A current list of IBM trademarks is available on
the web at “Copyright and trademark information”at ibm.com/legal/copytrade.shtml
Adobe is a trademark of Adobe Systems Incorporated in the United States, and/or other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.
SAP and SAP HANA are the trademarks or registered trademarks of SAP AG in Germany and in several other countries.
This document is current as of the initial date of publication and may be changed by IBM at any
time. Not all offerings are available in every country in which IBM operates. It is the user’s responsibility to evaluate and verify the operation of any other products or programs with IBM products
and programs.
THE INFORMATION IN THIS DOCUMENT IS PROVIDED “AS IS”WITHOUT ANY WARRANTY, EXPRESS
OR IMPLIED, INCLUDING WITHOUT ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTY OR CONDITION OF NON-INFRINGEMENT.
IBM products are warranted according to the terms and conditions of the agreements under which
they are provided. The client is responsible for ensuring compliance with laws and regulations applicable to it. IBM does not provide legal advice or represent or warrant that its services or products will ensure that the client is in compliance with any law or regulation.
Data Protection for SAP HANA® V6.4.1 - Installing, configuring, and protecting data
Download PDF
Similar pages