I am assuming you mean NT 4.0 versus 2000 (or higher).

The exclude works for me. Some things to check:

- Double-check your client options set and verify the syntax of the
statement.

- Double-check that this options set is specified for the node
ANR3.VCU.EDU.

- From the client machine run DSMC Q INCLEXCL. What does that show?

- Does putting the exclude directly in the dsm.opt file make any
difference?

The pagefile.sys file is not a "system object" per se, so this wouldn't
fall into a "system object" issue. Also, if this is NT 4.0, system objects
don't apply, anyway.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
01/13/2003 09:48
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Whats wrong with this EXCLUDE ?



Just installed V5.1.5.7 client on an NT machine.

Have the following INCLEXCL in a CLOPTSET that I verified is applied to
this node:

EXCLUDE *:\...\pagefile.sys

Doing the initial backup, I receive the error:

1/13/2003 11:32:06 AM ANE4987E (Session: 15261, Node: ANR3.VCU.EDU)  Error
processing '\\anr3\e$\pagefile.sys': the object is in use by another
process

So, why isn't it working ?  I use this same CLOPTSET for lots of W2K and
NT boxes without getting this message.

Could it be since the pagefile.sys is on the E: drive ?   I seem to recall
a problem with an earlier version of the client that had problems with
some systemobjects on other than C: drive that caused heartburn but I
thought it was fixed ?