IBM Storage Protect for Enterprise Resource Planning 8.2 Documentation Updates

Content

The IBM Storage Protect Data Protection for Enterprise Resource Planning was named IBM Tivoli® Storage Manager Data Protection for Enterprise Resource Planning in releases earlier than Version 7.1.3. To learn more about the rebranding transition, see this technote.

Data Protection for Enterprise Resource Planning V8.2.0
The IBM Knowledge Center messages collection for Brazilian Portuguese is shown in English. The PDF available in IBM Knowledge Center is in Portuguese. Click here to read the messages in Brazilian Portuguese, Data Protection for Enterprise Resource Planning Messages V8.1.0 

The IBM Knowledge Center messages collection for Japanese shows message sub-headings in English. The PDF available in IBM Knowledge Center shows all headings in Japanese. Click here to read the Japanese messages, Data Protection for Enterprise Resource Planning Messages V8.1.0 

Managing SAP HANA data with the Data Protection for SAP File Manager
The Data Protection for SAP File Manager is a tool that simplifies the inquire, restore, and delete operations of the SAP HANA backups that are saved to IBM Storage Protect server.
The interface consists of a split window that is character based. In the left hand window, certain backup IDs found on all IBM Storage Protect servers are displayed. These backup IDs are the ones that match the backup ID prefix that is configured in the Data Protection for SAP profile.

In the right-hand window, all the files that belong to the selected backup ID are displayed. Individual backup IDs or multiple files can be selected.

Procedure
 

1. Start the file manager with the path and the name of the Data Protection for SAP profile. The user must be a member of the dba group:

backfm -p /usr/sap/SID/SYS/global/hdb/opt/hdbconfig/initSID.utl [-o log file directory]

If the -o parameter is specified at startup, the default directory for log files is changed.

2. The file manager calls the backint executable file to connect to the IBM Storage Protect server configured in the Data Protection for SAP profile. If this call fails, the file manager shows an error message but does not analyze the cause of the error. Use the backint inquire function to analyze the error.

3. An automatic inquire operation for all backup IDs is done by the file manager. In the resultant list of backup IDs, if you mark the ID you are interested in and then press the Tab key to move the cursor to the right panel, all file names belonging to the marked backup ID are displayed.

The following function keys are defined for restore and delete operations:

Up, Down, Left, Right - Move cursor
Move the highlighted cursor in the direction indicated on the key.

Tab - Switch window side
Move the cursor between the left and right sides of the window.

F2 - Restore
Restore all marked files. Before the restore begins, you can specify a common destination path and you are prompted to confirm the restore process. If you specify a destination path, all marked files are restored to that directory. Otherwise, the files are restored to the directory from which they were backed up.
For restore operations, the wanted files first must be marked. This action can be done either with the F3 function key to mark all the files that were found or with the ENTER key to mark only one wanted file. Marked files can be identified by the symbol "*" in front of the file name. Only the marked files are restored. 
For every restore operation, a log file is created in the following location, 
 

• ${SAP_RETRIEVAL_PATH}/trace/backfm_<timestamp>.log

F3 - Mark all
All files that belong to the current backup ID is marked.

F4 - Unmark all
Unmark all files that belong to the current backup ID.

F5 - Refresh
Refresh the list of backup IDs and file names. 

F6 - Fileinfo
Opens a separate window to display file information.

For backup IDs, the sequence number is displayed (backup version count). For files, the IBM Storage Protect expiration date and time are displayed.

F7 - Not available

F8 - Delete
Delete the selected backup ID and all corresponding files. The file manager can delete backup IDs with all included files. It is not possible to delete single files within a backup ID. To delete a backup ID, it must be highlighted. After you press F8, you must confirm the deletion operation. The backup ID and all included files are deleted from the IBM Storage Protect server.

F10 - Exit
Exit from Data Protection for SAP file manager

ENTER - Mark/unmark file
Mark or unmark the file below the cursor.


Note: SAP HANA database must be restored using the SAP HANA Studio or SAP HANA command line utility. Restoring the backups with the file manager will restore them into the file system only. This should be performed only when SAP support instructs you to do so, or if you want to benchmark the restore without impacting the running SAP HANA database.


Support for Multitenant Database Containers (MDC)

SAP HANA supports multiple isolated databases in a single SAP HANA system. These are referred to as multitenant database containers.

Database Isolation

Every tenant database in a multiple-container system is self-contained and isolated in terms of users, database catalog, repository, logs, and so on. However, to protect against unauthorized access at the operating system (OS) level, it's possible to increase isolation further through OS user separation and authenticated communication within databases.

OS User Separation

By default, all database processes in a multiple-container system run under the default OS user <sid>adm. If it's important to mitigate against cross-database attacks through OS mechanisms, you can configure the system for high isolation. In this way, the processes of individual tenant databases must run under dedicated OS users belonging to dedicated OS groups, instead of all database processes running under <sid>adm. Database-specific data on the file system is subsequently protected using standard OS file and directory permissions.

Restore SAP HANA backups by using multiple sessions

With the release of SAP HANA SPS 10, multiple sessions for backup and restore are now supported. Previously, IBM Storage Protect for ERP was restricted to using a single session to do a restore because the objects had to be restored in the same order as they appeared in the inifile. 

In the setup script, you can enter the number of sessions to the IBM Storage Protect server that you want to use, and both IBM Storage Protect for ERP and SAP HANA configuration are adjusted accordingly.`

Create SAP HANA backups with different retention times

To configure Storage Protect for ERP Data Protection for SAP HANA to retain both daily and weekly type backups, it is necessary to set the retention within the IBM Storage Protect Server archive copygroup. Both a daily and a weekly management class with an archive copygroup would be defined on the IBM Storage Protect Server. Each archive copygroup would have the appropriate retentions set to keep the respective backups for the desired amount of time. 

For example, you might want to have a weekly and daily backups of the SAP HANA data that is kept for a longer time period.

The different archive copy groups are assigned to some management classes. e.g. MGMT_DAILY and MGMT_WEEKLY. You would need to create an additional server stanza in the Storage Protect for ERP profile as follows:

...
SERVER tsmsrv2
ADSMNODE HANA_SID
SESSIONS 2 
BRBACKUPMGTCLASS MGMT_DAILY
BRARCHIVEMGTCLASS MGMT_LOG_DAILY

SERVER tsmsrv3
ADSMNODE HANA_SID
SESSIONS 2 
BRBACKUPMGTCLASS MGMT_WEEKLY
BRARCHIVEMGTCLASS MGMT_LOG_WEEKLY

You can create these types of backups either by using the command line, or through the 'SAP HANA Cockpit'.

A command line example would be as follows:

hdbsql -U TSM "backup data using backint ('monthly_june_2016') tooloption 'stanza=tsmsrv3' "

An equivalent configuration in the SAP HANA Cockpit would be as follows:



The 'Backint Parameters' value specifies the archive copy group to use. With 'stanza=tsmsrv3' the server stanza 'tsmsrv3' would be selected.

Note: If no value is specified for 'Backint Parameters', the first available server in the profile is used. In the example above, if 'Backint Parameters' was left blank, tsmsrv2 would then be used. If tsmsrv2 does not respond (because it is down for whatever reason), then server stanza tsmsrv3 would be used.

Password permissions for using the Backup-Archive Client API with Storage Protect for ERP

Each user that is backing up and restoring databases with Storage Protect for ERP must have read and write access to the password or keystore files of the Backup-Archive Client API (BA Client < 8.1.2: TSM.PWD, BA Client >= 8.1.2: TSM.KDB, TSM.IDX and TSM.sth). 

For SAP Oracle, this is particularly important for the group 'dba'. This ensures that the database instance owner 'ora<SID>', the SAP admin '<SID>adm', and the Shared Database owner 'oracle' (for RMAN) can perform backup and restore operations. For information on how to enable these access levels, see the following IBM Storage Protect Knowlege Center topic: Enable non-root users to manage their own data.

On completion of the steps by the system administrator, the user then runs the dsmc q f command to use password files that are pointed to by the passworddir option. For IBM Storage Protect for ERP however, instead of using the command 'dsmc q f', the user must enter an ERP-specific command to set the password. The ERP commands for each environment are as follows:

Oracle: backint -p <initSID.utl> -f password
SAP HANA: hdbbackint -p <initSID.utl> -f password
DB2: backom -c password

----------------------------------------------------------------------------------------------------------------------------

(IT23535) How to ensure there are no interoperability issues due to differing GSKit versions between DB2 and IBM Storage Protect client version 7.1.8/8.1.2

To prevent IBM Storage Protect for Enterprise Resource Planning: Data Protection for DB2 V8.1.x incompatibility issues with IBM Storage Protect V7.1.8/8.1.2 due to different GSKit versions, refer to the following instructions for creating a symbolic link:

https://www.ibm.com/support/knowledgecenter/en/SSEQVQ_8.1.4/client/t_cfg_ssl_symb_lnk_gskit.html

----------------------------------------------------------------------------------------------------------------------------

(IT24403) How to enable redirected restore in batch mode for DB2 databases with non-default storage groups

To ensure that IBM Storage Protect for Enterprise Resource Planning: Data Protection for DB2 V8.1.x can restore DB2 databases having non-default storage groups configured, you must manually update the TDI file to keep non-default storage groups in a restored database.

1. Retrieve the tdi file from an IBM Storage Protect server. 
./backom -c r_tdi -a <DB2 source alias> -t <timestamp> -d <target directory of TDI>

example : > ./backom -c r_tdi -a L2A2 -t 20180409204756 -d /db2/L2A/tc_tool/tc/Files_Out/

2. Manually modify the retrieved TDI file by adding missed automatic storage path(s), correcting 
the storage path(s) according to a new location and correcting container paths if needed.

Example (modified sections are in bold):

[Backup]
Alias = HB2
Instance = db2hb2
Node = 0 
Timestamp = 20180409204756 
Database_Path = /db2/HB2/db2hb2/NODE0000/SQL00001/MEMBER0000/
Automatic_Storage_Path = /db2/HB4/sapdata1
Automatic_Storage_Path = /db2/HB4/sapdata2
Automatic_Storage_Path = /db2/HB4/sapdata3
Automatic_Storage_Path = /db2/HB4/sapdata4 
Automatic_Storage_Path = /db2/HB4/sapdata5
Automatic_Storage_Path = /db2/HB4/sapdata6 

[Tablespace 0 "SYSCATSPACE" dms 16384 2 287314 yes]
Container[0] = file | "/db2/HB4/sapdata1/db2hb2/NODE0000/HB4/T0000000/C0000000.CAT" | 72180
Container[1] = file | "/db2/HB4/sapdata2/db2hb2/NODE0000/HB4/T0000000/C0000001.CAT" | 72180
Container[2] = file | "/db2/HB4/sapdata3/db2hb2/NODE0000/HB4/T0000000/C0000002.CAT" | 72180
Container[3] = file | "/db2/HB4/sapdata4/db2hb2/NODE0000/HB4/T0000000/C0000003.CAT" | 72180

[Tablespace 1 "SAPTOOLS" dms 16384 2 348296 yes]
Container[0] = file | "/db2/HB4/sapdata1/db2hb2/NODE0000/HB4/T0000001/C0000000.LRG" | 94448
Container[1] = file | "/db2/HB4/sapdata2/db2hb2/NODE0000/HB4/T0000001/C0000001.LRG" | 94448
Container[2] = file | "/db2/HB4/sapdata4/db2hb2/NODE0000/HB4/T0000001/C0000002.LRG" | 94448
Container[3] = file | "/db2/HB4/sapdata3/db2hb2/NODE0000/HB4/T0000001/C0000003.LRG" | 94448
....
[Tablespace 6 "ZHB2#NLSD" dms 16384 2 364258 yes]
Container[0] = file | "/db2/HB4/sapdata5/db2hb2/NODE0000/HB4/T0000006/C0000000.LRG" | 182138
Container[1] = file | "/db2/HB4/sapdata6/db2hb2/NODE0000/HB4/T0000006/C0000001.LRG" | 182138

[Tablespace 7 "ZHB2#NLSI" dms 16384 2 1468 yes]
Container[0] = file | "/db2/HB4/sapdata5/db2hb2/NODE0000/HB4/T0000007/C0000000.LRG" | 746
Container[1] = file | "/db2/HB4/sapdata6/db2hb2/NODE0000/HB4/T0000007/C0000001.LRG" | 746 

3. Perform a redirected restore in a batch mode
backom -c rr_db_batch -a <DB2 source alias>,<DB2 target alias> -t <timestamp> -f <fully qualified 
path and name of TDI file>
examples: > ./backom -c rr_db_batch -a L2A2,HB1 -t 20180409204756 -f 
/db2/L2A/tc_tool/tc/Files_Out/L2A2.tdi
> ./backom -c rr_db_batch -a L2A2 -t 20180409204756 -f /db2/L2A/tc_tool/tc/Files_Out/L2A2.tdi

For more information, please refer to the following IBM Knowledge Center topic:

Processing redirected restore in batch mode