Troubleshooting
Problem
A DB2 backup is sent to Tivoli Storage Manager. The backup is expected to run via LAN-free but instead runs via the LAN.
Symptom
In this case, a database backup was done via LAN-free. The following command was used.
db2 backup db INF tablespace online use tsm
Similarly, a table space backup was also done via LAN-free.
However, a table space incremental backup used the LAN instead of LAN-free.
Cause
Incorrect include options in the Tivoli Storage Manager API dsm.sys file.
Diagnosing The Problem
Review the include options that are used by the DB2 backup. In this example, the following include statements were configured in the Include/Exclude file identified by the InclExcl option in the dsm.sys stanza used by the DB2 backup :
include /*/NODE????/FULL_BACKUP.??????????????.* LANFREE_MC
include /*/NODE????/DB_INCR_BACKUP.??????????????.* LANFREE_MC
include /*/NODE????/TSP_BACKUP.??????????????.* LANFREE_MC
In this example, tablespace backups are bound to the LANFREE_MC management class with :
include /*/NODE????/TSP_BACKUP.??????????????.* LANFREE_MC
However, an incremental table space backup was performed. Because no include statement was specified for incremental table space backups, the process used the default management class, which in this case uses the LAN instead of LAN-Free.
Resolving The Problem
Review the type of DB2 backup that you need to perform, for example, full database backup, incremental database backup, table space backup, and so on. To ensure that the LAN-free path is used, verify that the dsm.sys file has a correct include statement for the object to be backed up. The include statement must specify a management class that uses a LAN-free path.
The following table provides object names used by DB2 and a sample Tivoli Storage Manager include statement.
| Object | DB2 object name | Tivoli Storage Manager include statement with management class |
|---|---|---|
| Full database recovery object | /<dbname>/NODEnnnn/FULL_BACKUP.timestamp.seq_no | include /.../NODE????/FULL_BACKUP.* LANFREE_MC |
| Incremental database recovery object | /<dbname>/NODEnnnn/DB_INCR_BACKUP.timestamp.seq_no | include /.../NODE????/DB_INCR_BACKUP.* LANFREE_MC |
| Incremental delta database recovery object | /<dbname>/NODEnnnn/DB_DELTA_BACKUP.timestamp.seq_no | include /.../NODE????/DB_DELTA_BACKUP.* LANFREE_MC |
| Full table space recovery object | /<dbname>/NODEnnnn/TSP_BACKUP.timestamp.seq_no | include /.../NODE????/TSP_BACKUP.* LANFREE_MC |
| Incremental table space recovery object | /<dbname>/NODEnnnn/TSP_INCR_BACKUP.timestamp.seq_no | include /.../NODE????/TSP_INCR_BACKUP.* LANFREE_MC |
| Incremental delta table space recovery object | /<dbname>/NODEnnnn/TSP_DELTA_BACKUP.timestamp.seq_no | include /.../NODE????/TSP_DELTA_BACKUP.* LANFREE_MC |
where <dbname> is the database alias name, and NODEnnnn is the node number. The names shown in uppercase characters must be entered as shown.
Refer to the "DB2 Considerations for using Tivoli Storage Manager" information for further details on objects names used by DB2.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21672871