Syntactically, your INCLUDE looks correct, so that is why TSM doesn't
A couple of things come to mind:
1. There is another INCLUDE or EXCLUDE statement that encompasses the
specification. Use "dsmc query inclexcl" to check the final
include-exclude list. This is "INCLUDE-EXCLUDE Debugging 101" :-)
2. "Backup" is a directory, not a file... in which case, the INCLUDE has
no effect since files are bound either to the management class with the
highest RETONLY setting or to the management class specified by DIRMC. In
this case, correct the statement to include files in that dir or files in
that dir and its subdirs, e.g., "\*" or "\...\*".
3. The management class does not exist (you said you are not in a position
to check, but I state this anyway for completeness).
4. Is there at least one blank space between the ending quote and the
management class name? When I reply using internet-style quoting, the
management class name appears butted right up against the file spec (no
intervening blank space). When I reply without internet-style quoting, it
doesn't appear that way; so it is hard to tell. Force a blank space
between those two elements.
If none of these answers the question, then it would help to have more
- Complete include-exclude list as shown by "dsmc query inclexcl"
- Results you are seeing
- Results you think you are supposed to see
- In plain English, what directory/files you are trying to bind.
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/[email protected]
Internet e-mail: storman AT us.ibm DOT com
IBM Tivoli Storage Manager support web page:
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"Gill, Geoffrey L." <GEOFFREY.L.GILL AT SAIC DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
ADSM-L AT VM.MARIST DOT EDU
dsm.opt include statement
Seems as though some folks are having issues with management classes in
the dsm.opt that point includes to a management class that holds data for
a longer period of time than the default. I was wondering if anyone had an
idea as to why this statement seems to not work. There are no errors in
the log and no indications elsewhere of an issue.
the client is the latest version Windows client running onWindows 2003.
Unfortunately I am out of the country and can't double check the
management class itself to make sure it is properly defined.
Include "E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup"