Hi Lisa,
   How about exclude.dir d:\  (etc.) that should exclude anything on the d:
drive.

Douglas C. Nelson
Distributed Computing Consultant
Alltel Information Services
Chittenden Data Center
2 Burlington Square
Burlington, Vt. 05401
802-660-2336



-----Original Message-----
From: Lisa Cabanas [mailto:CABANL AT MODOT DOT NET]
Sent: Friday, December 06, 2002 8:38 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: domain c: in cloptset is not excluding the d: drive


Hello *,

I have a problem with some of my NT SP5 clients (running client 4.2.1.20
mostly, with a 4.2.1.9 TSM server on 4.3 ML10 server.  I am trying to only
back up the c drive on a number of servers.  I have tried putting the
domain c: line in the dsm.opt on the client (manually and via the wizard),
saving, stopping and restarting the scheduler service and it doesn't work.
(I have deleted all the files spaces of the type d$ or e$, but they
reappear after a plain ol' incr).  I have put it in a cloptset just for
those servers, and specified the cloptset for those clients, and it still
backs up the d$ drive (but NOT the e$ that still physically exists).

Another weird thing I have noticed, is that when I deleted the filespaces
the were numbered like this:
c$   fsid=1
d$   fsid=2
e$   fsid=3

But after the deletion of the fsid's 2 & 3 and after an incr backup, the
newly backed up d$ has a fsid=4.

What gives??


Here's the cloptset:
(See attached file: CLOPTSET.TXT)


and the scheds all run as an unspecified INCR.  Also, if I browse the
client thru the Web GUI or the user interface locally on the client's
desktop, those drives still show up and they don't have Xs on them, either.

I'm stumped.

Any of you good folk have an idea???


thanks!

lisa