Troubleshooting
Problem
An include option is configured in a client options set that is defined on a Tivoli Storage Manager server. The include option bind files to a specific management class. The client backs up the involved files but the files are not bound to the specified class.
Diagnosing The Problem
Run the QUERY CLOPT server administrative command to verify the options specified in the options set. For example :
tsm: MYTSM>q clopt myclopt
Optionset: MYCLOPT
Description:
Last Update by (administrator): ADMIN
Managing profile:
Option: INCLEXCL
Sequence number: 0
Use Option Set Value (FORCE): No
Option Value: include '/testfs/*.txt class1'
In this example, the intention is to bind the /testfs/*.txt files to the class1 management class.
From the backup-archive client that is associated to this client options set, run the QUERY INCLEXCL client command. Use the -detail parameter to verify the management class that is used by the include option. For example :
# dsmc q inclexcl -detail
*** FILE INCLUDE/EXCLUDE ***
Mode Function Pattern (match from top down) Source File
---- --------- ------------------------------ -----------------
No exclude filespace statements defined.
Excl Directory /.../.TsmCacheDir TSM
Excl Directory /.../.SpaceMan Operating System
Include All /testfs/*.txt class1 Server
MC NAME:
Exclude HSM /etc/adsm/SpaceMan/config/.../* Operating System
Exclude HSM /.../.SpaceMan/.../* Operating System
Exclude Restore /.../.SpaceMan/.../* Operating System
Exclude Archive /.../.SpaceMan/.../* Operating System
No DFS include/exclude statements defined.
In this example, the /testfs/*.txt files will not be bound to the class1 management class because the "MC NAME:" field has a blank value. This indicates that the include statement was incorrectly configured in the client options set.
Resolving The Problem
To bind files to a specific management class in a client options set, do not surround the file specification and management class with quotes.
In this specific case, quotation marks were incorrectly used for the client options set:
define clientopt myclopt inclexcl "include '/testfs/*.txt class1'"
The following command shows the correct syntax to use to bind the /testfs/*.txt files to the class1 management class:
define clientopt myclopt inclexcl "include /testfs/*.txt class1"
Use the DELETE CLIENTOPT and DEFINE CLIENTOPT administrative commands to correct the client options set on the server.
After the client options set is corrected, run the QUERY CLOPT server administrative command to verify the options that are specified in the options set. For example :
tsm: MYTSM>q clopt myclopt
Optionset: MYCLOPT
Description:
Last Update by (administrator): ADMIN
Managing profile:
Option: INCLEXCL
Sequence number: 0
Use Option Set Value (FORCE): No
Option Value: include /testfs/*.txt class1
From the backup-archive client that is associated to this client options set, run the QUERY INCLEXCL client command. Use the -detail parameter to verify the management class that is used by the include option. For example :
# dsmc q inclexcl -detail
*** FILE INCLUDE/EXCLUDE ***
Mode Function Pattern (match from top down) Source File
---- --------- ------------------------------ -----------------
No exclude filespace statements defined.
Excl Directory /.../.TsmCacheDir TSM
Excl Directory /.../.SpaceMan Operating System
Include All /testfs/*.txt Server
MC NAME: CLASS1
Exclude HSM /etc/adsm/SpaceMan/config/.../* Operating System
Exclude HSM /.../.SpaceMan/.../* Operating System
Exclude Restore /.../.SpaceMan/.../* Operating System
Exclude Archive /.../.SpaceMan/.../* Operating System
No DFS include/exclude statements defined.
In this example, the /testfs/*.txt files will be bound to the class1 management class because the "MC NAME:" field has a value of CLASS1.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21651636