tsm erp dp hana 641 users guide

8/21/2019 Tsm Erp Dp Hana 641 Users Guide

1/12

IBM Tivoli Storage Manager forEnterprise Resource Planning

Data Protection for SAP HANA®

Installing, configuring, and protectingdataVersion 6.4.1

DescriptionUse this document to help you to install, configure, and protect SAP HANA data with IB !i"oli Storageanager for #nterprise $esource Planning% Data Protection for SAP HANA& !his "ersion of Data Protection forSAP HANA can 'e used in your e(isting !i"oli Storage anager 'ac)up en"ironment once all prere*uisites ha"e'een met&

Installation

Prerequisites

Before installing and configuring Data Protection for SAP HANA, "erify that the following prere*uisites are met%

• SAP HANA SPS + re"ision - or later is a"aila'le&

• !i"oli Storage anager API .ersion & or later is installed and configured on all SAP HANA nodes whereyou are going to install and configure Data Protection for SAP HANA&

• !he SAP HANA data'ase 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 installationand configuration of Data Protection for SAP HANA, root access to the appliance host operating system isre*uired&

Data Protection for SAP HANA® ./&-&0 1 Installing, configuring, and protecting data


2/12

Limitations

Data Protection for SAP HANA is not integrated with the !i"oli Storage anager for #nterprise $esourcePlanning Administration Assistant& !he Administration Assistant cannot 'e used to configure and monitor DataProtection for SAP HANA&

Installation

!he Data Protection for SAP HANA installation pac)age is deli"ered as a self1contained installer program& !hisfile uses the following name format%

6.4.1.0-TIV-TSMERP-HANA-Linux.bin

!o install the software, complete the following steps%

0& Using the root user ID, log on to the SAP HANA host where you want to install Data Protection for SAPHANA& 2hoose one of the following methods for installing%

I& ount the D.D containing Data Protection for SAP HANA&II. 3rom the command line, change to the D.D directory where the installer is located& #nter 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 4 5indows System or 4 terminal the installation will'e started in graphical mode and will guide you through the installation process& 3ollow the screeninstructions to complete the installation& If you are using a non1graphical terminal during installation, aconsole mode installation will 'e started&

I.& If you are installing from an file share directory, enter the following command to ensure that the installerfile has e(ecute permissions%

chmod +x 6.4.1.0-TIV-TSMERP-HANA-Linux.bin


Illustration 1: Data Protection for SAP HANA Installation Welcome screen


3/12

2. Accept the license agreement and clic) Next& !he Data Protection for SAP HANA will chec) if theprere*uisites are met 'efore proceeding&


Illustration 3: Pre-Installation Summary screen

Illustration 2: Software License Agreement screen


4/12

Installation resultsDuring the installation, the following changes are automatically completed on the system where the software isinstalled%

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

!o automate the installation of Data Protection for SAP HANA in silent mode using a response file follow thesteps 'elow& Installing the program in silent mode means you so not need to monitor the process or input anydetails& !he steps needed to create a response file to start the installation in silent mode are listed&

0& 2reate a response file for the installation in silent mode using the option 61i console7 and 61r responsefile7, fore(ample% ./6.4.1.0-TIV-TSMERPHANA-CD-Linux.bin -i console -r responsefile

8& Silent mode installation using the pre"iously recorded responsefile can 'e started using the option 61i silent7followed 'y the option 61f7 pro"iding the name of your response file& 3or e(ample%

./6.4.1.0-TIV-TSMERPHANA-CD-Linux.bin -i silent -f responsefile


Illustration : Installation !om"lete# screen


5/12

ninstallation

!o uninstall Data Protection for SAP HANA and remo"e all files that are associated with it, follow these steps%

1. 2hange directory to the uninsta su'directory in the installation folder&8& #nter the following command%/opt/tivoli/tsm/tdp_hana/uninstall/uninstaller.bin

$esults%

!he uninstaller will remo"e Data Protection for SAP HANA from your system& Ser"ices that are installed andused 'y Data Protection for SAP HANA will 'e stopped and remo"ed&

Note% If $P is used to uninstall Data Protection for SAP HANA the uninstallation program would remain on dis)&

!he !i"oli Storage anager for #$P $P pac)ages that were installed as part of the setup procedure on otherSAP HANA nodes will remain on these nodes& !o remo"e these pac)ages, run the following command on theSAP HANA nodes%

rpm -e TIV-TSMERP-HANA

Setting up Data Protection for S!P "!N!Before Data Protection for SAP HANA can 'e used, it must 'e configured using the setup.sh script in the

installation directory& !o run the setup.sh script, follow these steps%

0& 2hange to the Data Protection for SAP HANA installation directory%cd /opt/tivoli/tsm/tdp_hana

8& #nter the following command to run the Data Protection for SAP HANA configuration script setup.sh with theroot user ID%

./setup.sh

!he Data Protection for SAP HANA configuration files are installed in the configuration directory

/usr/sap//SYS/global/hdb/opt/hdbconfig:▪init.utl

▪init.bki

▪agent.lic 9copy of the licence file stored in the Data Protection for SAP HANA

installation directory:&

;& 9


6/12

#onfiguring Data Protection for S!P "!N!

Data Protection for SAP HANA re*uires the !i"oli Storage anager API configuration files dsm.sys anddsm.opt to 'e configured& !he ser"er stan?a in the dsm.sys file that is used for Data Protection for SAP HANAshould 'e created 'efore proceeding to the configuration of Data Protection for SAP HANA&

!he following information is re*uested when e(ecuting the Data Protection for SAP HANA configuration scriptsetup.sh.

0& Please enter the SAP HANA system ID [SID]:!he setup&sh script pro"ides a proposal for the SAP HANA system ID& !o accept the proposed "alue, pressenter&

8& Please enter instance number [00]:3or a typical configuration, the SAP HANA instance num'er is ++& @ou can accept the default "alue 'y pressingenter, or o"erride it with your input&

;& Enter the Please enter password for SYSTEM user:!he system user is the SAP HANA data'ase administration user& !he password of the system user is usedinternally only in the setup.sh script& !he password is not stored 'y Data Protection for SAP HANA&

-& @ou will 'e as)ed if you want to setup the !i"oli Storage anager configuration& If you )now how the !i"oliStorage anager ser"er is configured, and how the !i"oli Storage anager node is configured, answer yes& @ou

will 'e as)ed for !i"oli Storage anager configuration parameters& Based on the information that is pro"ided, theconfiguration in the Data Protection for SAP HANA U!=1file is updated&&If you answer no, you must manually edit the Data Protection for SAP HANA U!=1file initSID.utl after the

setup.sh script finishes& @ou need to change the following !i"oli Storage anager parameters in the ser"er

section of this U!=1file%

SERVER server # Servername, as defined in dsm.sysADSMNODE NODE # Tivoli Storage Manager NodenameBRBACKUPMGTCLASS MDB # Mgmt-Classes for database backupBRARCHIVEMGTCLASS MLOG # Mgmt-Classes for redo log backup

/& If you answered yes, you will 'e as)ed if you want to use automatic password handling& If you chooseautomatic password handing the !i"oli Storage anager node password is stored 'y the !i"oli Storage anagerAPI& 5hen the !i"oli Storage anager node password e(pires on the ser"er, the !i"oli Storage anager clientand ser"er automatically negotiate a new password& !he API in turn updates the password on the client& 3or thisfeature the !i"oli Storage anager node name must 'e specified in the ser"er stan?a in the dsm.sys file&

!he other configuration option is to manually handle passwords& 5ith this option the !i"oli Storage anagernode password is stored in the !i"oli Storage anager for the #$P configuration file&


7/12

data'ase&

0+& Please enter the TSM management class for log file backups:!he Data Protection for SAP HANA U!=1file init!"#&utl parameter B$A$2HI.#F!2=ASS is updated with the!i"oli Storage anager management class name& Data Protection for SAP HANA uses the !i"oli Storageanager management class on the !i"oli Storage anager ser"er to 'ac)up and restore data'ase redo log files&

00&@ou are prompted to set the password for the !i"oli Storage anager node& After you enter the password, thepassword is "erified& 3or a scale1out system with automatic password handling this step is repeated for each

SAP HANA node that 'elongs to the scale1out system&

!dditional configuration considerations

Tivoli Storage Manager client profile

Data Protection for SAP HANA re*uires the !i"oli Storage anager ser"er and the local !i"oli Storage anagerclient to 'e configured& 3or more information a'out these configuration tas)s, see the configuration section of the$ivoi !tora%e &ana%er 'or Enterprise esource Pannin% Version 6.3 "nstaation and ser*s +uide& !hisdocument is a"aila'le online at%http%GGpic&dhe&i'm&comGinfocenterGtsminfoG"/r;GtopicGcom&i'm&itsm&erp&d ocGtdperpconfiguringtsm&html

Data Protection for S!P "!N! profile

!he Data Protection for SAP HANA profile has the default name init!"#&utl, where !"# is the identifier of the SAPHANA data'ase 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 adusted to use this

profile for 'ac)up and reco"ery operations&Additional customi?ations are a"aila'le according to the instructions in the $ivoi !tora%e &ana%er 'or Enterpriseesource Pannin% Version 6.3 "nstaation and ser*s +uide a"aila'le at%http%GGpic&dhe&i'm&comGinfocenterGtsminfoG"/r;GtopicGcom&i'm&itsm&erp&docGcdperpc optdpsapprofile&html

Special considerations for scale$out solutions

5hen Data Protection for SAP HANA is used to protect a scale1out solution, 'ac)up and restore operations runsimultaneously on all SAP HANA nodes& SAP re*uires that each SAP HANA node has access to all 'ac)ups thatha"e 'een run 'y any SAP HANA node within the cluster& !his results in the re*uirement that all data has to 'estored on a single !i"oli Storage anager ser"er&

3or manual password handling all SAP HANA nodes must ha"e an identical !i"oli Storage anagerconfiguration& #nsure that the stan?as in dsm.sys that are referenced 'y the !i"oli Storage anager for #$P

profile are identical& An e(ample is shown 'elow& Note that the parameter nodename in dsm.sys is commented

out&


http://pic.dhe.ibm.com/infocenter/tsminfo/v6r3/topic/com.ibm.itsm.erp.doc/t_dperp_configuring_tsm.htmlhttp://pic.dhe.ibm.com/infocenter/tsminfo/v6r3/topic/com.ibm.itsm.erp.doc/t_dperp_configuring_tsm.htmlhttp://pic.dhe.ibm.com/infocenter/tsminfo/v6r3/topic/com.ibm.itsm.erp.doc/c_dperp_c_opt_dpsapprofile.htmlhttp://pic.dhe.ibm.com/infocenter/tsminfo/v6r3/topic/com.ibm.itsm.erp.doc/c_dperp_c_opt_dpsapprofile.htmlhttp://pic.dhe.ibm.com/infocenter/tsminfo/v6r3/topic/com.ibm.itsm.erp.doc/t_dperp_configuring_tsm.htmlhttp://pic.dhe.ibm.com/infocenter/tsminfo/v6r3/topic/com.ibm.itsm.erp.doc/c_dperp_c_opt_dpsapprofile.htmlhttp://pic.dhe.ibm.com/infocenter/tsminfo/v6r3/topic/com.ibm.itsm.erp.doc/c_dperp_c_opt_dpsapprofile.htmlhttp://pic.dhe.ibm.com/infocenter/tsminfo/v6r3/topic/com.ibm.itsm.erp.doc/t_dperp_configuring_tsm.html


8/12

If automatic password handling is used the stan?as in dsm.sys, that are referenced 'y the !i"oli Storage

anager for the #$P profile must ha"e uni*ue !i"oli Storage anager node names for each SAP HANA node&


9/12

Performance considerations

5hen SAP HANA runs a 'ac)up it sends the data for all SAP HANA ser"ices, such as nameser"er andinde(ser"er in parallel from all nodes& If data is intended to go directly to tape, the num'er of allowed mountpoints for the !i"oli Storage anager node needs to 'e adusted accordingly&If data is stored in a dis) storage pool first, and afterwards migrated to tape it should 'e considered that SAPHANA e(pects data to 'e restored in the order determined 'y HANA& It is not possi'le for !i"oli Storage anagerfor #$P to optimi?e the restore order to reduce the num'er of tape see)s and mounts& If the data to 'e restoredfor all nodes is located on a single tape dri"e this can lead to increased restore times or e"en deadloc)s& Use

either dis) storage pools or tapes with a sufficient num'er of mount points to a"oid deadloc)&

Expiration of o%solete %ac&ups

In contrast to ./&-&+ the profile )eyword A4.#$SI


10/12

;&


11/12

;& In the Locate Log Bac&ups panel no input is re*uired& !he default location can 'e used&

-& 2hoose the 'ac)up to restore in the Select Data Bac&ups panel& !he list of 'ac)ups is generated from theSAP HANA reco"ery catalog& !his catalog contains e"ery 'ac)up that has 'een created& By selecting a specific'ac)up and pressing hec vaiabiit it can 'e "erified that the 'ac)up e(ists on the !i"oli Storage anagerser"er&

&Ad"ance through the panels, and selecting appropriate options& $efer to the SAP HANA documentation forfurther details&


Illustration /: Select t&e 0ac)u" to restore wit& SAP HANA Stu#io


12/12

©Copyright IBM Corporation 2012, 2013 . U.S. Government Users Restricte Rights ! Use, "p#ica!tion or isc#os"re restricte $y GS% %&' Sche"#e Contract (ith IBM Corp.

IBM, the IBM #ogo, i$m.com, )ivo#i, an System Storage are traemar*s o+ Internationa# B"sinessMachines Corp., registere in many "risictions (or#(ie. -ther pro"ct an service namesmight $e traemar*s o+ IBM or other companies. % c"rrent #ist o+ IBM traemar*s is avai#a$#e onthe (e$ at Copyright an traemar* in+ormation/at i$m.com#ega#copytrae.shtm#

%o$e is a traemar* o+ %o$e Systems Incorporate in the Unite States, anor other co"ntries.

in" is a registere traemar* o+ in"s )orva#s in the Unite States, other co"ntries, or $oth.

Microso+t an ino(s are traemar*s o+ Microso+t Corporation in the Unite States, other co"n!tries, or $oth.

S%' an S%' 4%5% are the traemar*s or registere traemar*s o+ S%' %G in Germany an in sev!era# other co"ntries.

)his oc"ment is c"rrent as o+ the initia# ate o+ p"$#ication an may $e change $y IBM at anytime. 5ot a## o++erings are avai#a$#e in every co"ntry in (hich IBM operates. It is the "ser6s respon!si$i#ity to eva#"ate an veri+y the operation o+ any other pro"cts or programs (ith IBM pro"ctsan programs.

)47 I58-RM%)I-5 I5 )4IS &-CUM75) IS 'R-9I&7& %S IS/I)4-U) %5: %RR%5):, 7;'R7SS-R IM'I7&, I5CU&I5G I)4-U) %5: %RR%5)I7S -8 M7RC4%5)%BII):, 8I)57SS 8-R % '%R!

)ICU%R 'UR'-S7 %5& %5: %RR%5): -R C-5&I)I-5 -8 5-5!I58RI5G7M75).

IBM pro"cts are (arrante accoring to the terms an conitions o+ the agreements "ner (hichthey are provie. )he c#ient is responsi$#e +or ens"ring comp#iance (ith #a(s an reg"#ations ap!p#ica$#e to it. IBM oes not provie #ega# avice or represent or (arrant that its services or pro!"cts (i## ens"re that the c#ient is in comp#iance (ith any #a( or reg"#ation.


tsm erp dp hana 641 users guide

Documents