IBM Spectrum Protect for Enterprise Resource Planning 7.1 Documentation Updates

Content

Tip: Beginning with Version 7.1.3, IBM Tivoli Storage Manager for Enterprise Resource Planning is now IBM Spectrum Protect for Enterprise Resource Planning. Some applications such as the software fulfillment systems and IBM License Metric Tool use the new product name. However, the software and its product documentation continue to use the Tivoli Storage Manager product name. To learn more about the rebranding transition, see http://www.ibm.com/support/docview.wss?uid=swg21963634.

All versions, IBM Spectrum Protect for ERP: Data Protection for SAP HANA:

The following Planning topic in IBM Knowledge Center is incorrect, http://www.ibm.com/support/knowledgecenter/SSZHVN_7.1.3/erp.hana/c_dperp_hana_perf_backupserver.html

This is the updated information that should be used instead,

Backup server optimization

When you are setting up the IBM Spectrum Protect server for use with IBM Spectrum Protect for Enterprise Resource Planning, the following considerations help you to optimize performance.

Consider these items when you set up the IBM Spectrum Protect server. Data Protection for SAP uses the IBM Spectrum Protect archive function for all backup activities.

Dedicated backup server
A dedicated backup server allows sharing of resources and provides an efficient resource usage.
CPU power
For a specific data throughput, the CPU load on the backup server is approximately 60% of the load on the database server. Therefore, backup server CPU power is not as critical as the CPU power of the database server. However, demands on the IBM Spectrum Protect server CPU do increase when several clients access a single IBM Spectrum Protect server.

Storage hierarchy

Not following these requirements can lead to recovery issues and a deadlock situation.

The specific interaction of current SAP HANA versions with IBM Spectrum Protect for Enterprise Resource Planning: Data Protection for SAP HANA implies special requirements for the type of storage media that are used, and the rules for data movement in IBM Spectrum Protect storage. The requirements are different for data files and for log files: you must always use separate management classes and storage pools for BRBACKUPMGTCLASS and BRARCHIVEMGTCLASS.

Data files
For best restore performance it is important that files that were backed up simultaneously, are held ready for parallel access during restore. By internal data movement to physical or virtual tape in IBM Spectrum Protect storage after the backup, files that are bound to be restored in parallel can end up on the same volume.

The following suggestions help to avoid a situation that would lead to an increase of the restore duration by media wait. Use devclass disk, sequential file, directory-container storage (IBM Spectrum Protect Server 7.1.3), or physical tape, Virtual Tape Library (VTL) as the first storage pool for BRBACKUPMGTCLASS.

• Do not move any SAP HANA data files in IBM Spectrum Protect storage from the first stgpool to physical tape or VTL storage. This rule is the case for storage pools on random disk, sequential file, physical tape, or VTL storage.
• Do not use nextstgpool to point to storage other than random disk or sequential file to prevent migration to physical tape or VTL.
• When you use physical tape or VTL storage as the first stgpool for HANA data files, do not run space reclamation on this storage pool.
• Do not use move data from the first stgpool to physical tape or VTL storage, regardless of the devtype of the first storage pool devclass.

Log files
Always use devclass disk, sequential file, or directory-container storage as the first storage pool for BRARCHIVEMGTCLASS. Storage pools that are receiving HANA log files do not require more space allowance beyond the real amount of data to be kept in IBM Spectrum Protect. The estimated size that is assumed by Data Protection for SAP HANA is expected to be sufficiently close to the real log file size.
You can reduce the space consumption in used devclass by using compression. For this specific purpose, the IBM Spectrum Protect API client parameter COMPRESSIon Yes in dsm.sys is expected to be more efficient than the parameter RL_COMPRESSION YES in initSID.utl.
Do not move any HANA log files in IBM Spectrum Protect storage to physical tape or VTL storage. Further considerations for this rule are as follows.

• Only random disk or sequential files are allowed as defined in nextstgpool for migration.
• Run move data actions only to random disk or sequential file.
• If HANA log files are stored on physical tape or VTL, you must move the data to sequential file before the recovery operation.

Parallel sessions
The IBM Spectrum Protect server allows the use of several tape drives in parallel to store data. This setup can increase overall data throughput. To fully use this feature, two conditions must exist. The corresponding IBM Spectrum Protect node must be allowed the appropriate number of mount points and the device class must be allowed the appropriate mount limits.

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

To ensure that IBM Spectrum 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 Spectrum 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