Andy, His additions are at the bottom of his dsm.opt file. There is also a client optionset that has: Include ?:* FILESERVER Fred Johanson TSM Administrator University of Chicago 773-702-8464 --Origi
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Thu, 29 Nov 2007 14:47:36 -0700
Yes, but it's not position in the dsm.opt file that matters when client option sets are at issue. Use "dsmc query inclexcl" to see the final list that TSM actually uses. I suspect it is that client o
Author: "Strand, Neil B." <NBStrand AT LMUS.LEGGMASON DOT COM>
Date: Thu, 29 Nov 2007 16:50:59 -0500
The options defined in server client optins have precidence Any include-exclude statements in the server client option set have priority over the include-exclude statements in the local client option
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Thu, 29 Nov 2007 22:11:38 -0700
Hi Fred, FORCE has no effect on INCLEXCL, so that's a nonstarter. Try this: remove the INCLUDE statement from the dsm.opt file and instead add it to the client option set on the server. But instead o
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Mon, 3 Dec 2007 11:33:41 -0700
A couple of things: 1. Is the actual machine name "tank1.ad.uchicago.edu"? In other words, if from that machine you run SET COMPUTERNAME from an OS prompt, is that what it shows? Or does it just show
There are no 'INCLUDE' lines in the option set other than the initial one. This is the dsm.opt: EXCLUDE.BACKUP "*:\microsoft uam volume\...\*" EXCLUDE.BACKUP "*:\microsoft uam volume\...\*.*" EXCLUDE
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Mon, 3 Dec 2007 11:44:49 -0700
OK, so my comments re: your INCLUDE file spec stand. Once that is fixed up to match the actual file space name, it should work. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Cl
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Thu, 29 Nov 2007 15:21:03 -0700
OK, the Q INCLEXCL output is what we're interested in. You read the Q INCLEXCL from the top down (opposite of the dsm.opt file). Notice that all the dir excludes (EXCLUDE.DIR) are at the top, since t
Andy, I think I have it. Neither of us spotted the "$f" instead of "f$", but here is the latest inclexcl list. He'll let me know tomorrow morning. ** FILE INCLUDE/EXCLUDE ** Mode Function Pattern (ma
So how does he get what he wants. The option set is to set a management class for a number of clients. The new management class applies to 1 of the 10. Will setting the OVERRIDE=yes have the desired
Our desktop support unit has a user that wants a new retention policy on their file share. The admin added this to the dsm.opt: INCLUDE "F:\NSIT\FieldSupport\University Administration\Budget Office\
"Does not work", his term, which means the files show up on the gui as being in the default management class. The new management class does not show up in "Q inclexcl". The new management class shows
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Thu, 29 Nov 2007 17:53:46 -0700
Fred, I cannot give you a definitive to answer your question since I do not know your shop, its policies, service level agreement, etc., For example, it could be your shop policy that the INCLUDE *:\
Andy, The machine admin wasn't in on Friday, but today he reports the new mgmtc still doesn't show up. He sent along the inclexcl from this morning: ** FILE INCLUDE/EXCLUDE ** Mode Function Pattern (
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Thu, 29 Nov 2007 13:28:51 -0700
Nothing wrong per se, although the second INCLUDE appears redundant. The first place to start with these kinds of issues is to use "dsmc query inclexcl" to makes sure those files aren't being picked
Our desktop support unit has a user that wants a new retention policy on their file share. The admin added this to the dsm.opt: INCLUDE "F:\NSIT\FieldSupport\University Administration\Budget Office\*
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Mon, 3 Dec 2007 14:15:18 -0700
Hi Fred, good to hear you have it straightened out. Yes, that looks correct now; notice that the drive letter is resolved to F:. Also don't forget that you want to use "...\*" at the end of the file
Thanks Andy, I'll try to make this brief. I had thought of making a special cloptset for this client, but the machine admin figures that once this special exception becomes known, the other 15 to 20
Andy, I got a note that said that all is now as the users want. thanks for the help. ________________________________ Hi Fred, good to hear you have it straightened out. Yes, that looks correct now;