Hi Bob, The QUERY INCLEXCL command should show also cover include/exclude statements coming from the server. What it looks like on my workstation: (see the "Include All" entry):
C:\TSM\baclient>dsmc q inclexcl -optfile=dsm.opt.local IBM Tivoli Storage Manager Command Line Backup/Archive Client Interface Client Version 5, Release 3, Level 4.6 Client date/time: 01/19/2007 14:56:45 (c) Copyright by IBM Corporation and other(s) 1990, 2006. All Rights Reserved. Node Name: ANDY Session established with server BABYLON5: Windows Server Version 5, Release 3, Level 3.0 Server date/time: 01/19/2007 14:56:46 Last access: 01/19/2007 14:55:04 *** FILE INCLUDE/EXCLUDE *** Mode Function Pattern (match from top down) Source File ---- --------- ------------------------------ ----------------- Excl Directory C:\adsm.sys Operating System Include All C:\DirSpecifiedByCloptSet\...\* Server Exclude All C:\WINDOWS\usrclass.dat.log Operating System Exclude All C:\WINDOWS\usrclass.dat Operating System Exclude All C:\WINDOWS\system32\wbem\Repository\...\* Operating System Exclude All C:\WINDOWS\system32\NtmsData\...\* Operating System Exclude All C:\WINDOWS\system32\NtmsData\* Operating System ... Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 01/19/2007 02:14:10 PM: > Andy: > As usual, your suggestion was better than most manuals...initial > testing (well, okay, on my > workstation) indicates that the clientoptset settings will override the > operating system directives > (so the hierarchy for includes/excludes seems to be client options file, > client OS directives, > server's clientoptset settings). We are proceeding with testing on the > user's system. > > However, in the course of doing this, we discovered that the "query > inclexcl" command is, > well, less than useless - it failed to show the impact of the server > side client option set settings > (and specifiying a "test patten" produced nothing of use). The preview > include/exclude feature > in the GUI was not only more informative, it was also more accurate. > One of the few times > I've found the GUI more useful than the command line client. Is this a > known issue with > the "query inclexcl"? > (TSM CLient for Windows x32 v5.3.4.4) > > Andrew Raibeck wrote: > > Hi Bob, > > > > The excludes for DFS come from VSS, which TSM queries upon startup. This > > is why using PRESCHEDULECMD to stop DFS before the backup begins does not > > help: because by the time the client runs the PRESCHEDULECMD command, the > > exclude has already been set (hence my suggestion to use a separate > > schedule that runs prior to the backup, and to use the CAD-managed > > scheduler rather than the old-style scheduler service). > > > > Adjusting the service startup order is a form of circumvention, but as you > > noticed, if you stop and restart the scheduler, the exclude will kick in > > again. > > > > One thing you could try is to use an INCLUDE in a client option set (not > > in the client options file) for the affected directories. I haven't tested > > it myself, though, so I cannot say from experience how well that will > > work. And depending on the number of directories involved, maintaining the > > INCLUDE statements might be cumbersome. But that is the only other thing I > > can think of. > > > > Best regards, > > > > Andy > >
