In version 5.x of the TSM client I believe you can use domain -D: to exclude a domain.
I havn't actually tried this, but when I installed a client (v5.1.5.1) it default excluded domains in dsm.opt this way -and I couldn't see the drives excluded in the GUI or CL. Could be wirth a try. Rgds, Geirr G. Halvorsen -----Original Message----- From: Lisa Cabanas [mailto:[EMAIL PROTECTED]] Sent: 6. december 2002 15:37 To: [EMAIL PROTECTED] Subject: Re: domain c: in cloptset is not excluding the d: drive I tried it with yes, with domain c: in the client dsm.opt, but that didn't work. The domain statements are cumulative, so if I set override to yes, and left the default (which is to not code domain statement which is then all-local), I'd still have the problem. I guess I could put the exlude.dir statements in the cloptset (like Doug Nelson suggested), but the domain option is not working as designed. I don't even want the clients to examine the other drives, which is what the domain option would do. thanks lisa Niklas Lundstrom <niklas.lundstrom@FORENINGSSPAR To: [EMAIL PROTECTED] BANKEN.SE> cc: Sent by: "ADSM: Dist Stor Subject: Re: domain c: in cloptset is not excluding the d: drive Manager" <[EMAIL PROTECTED]> 12/06/2002 07:51 AM Please respond to "ADSM: Dist Stor Manager" Hello Try to put overrride yes for domain in your clientopt set. How does your dsm.opt look like? Regards Niklas -----Original Message----- From: Lisa Cabanas [mailto:[EMAIL PROTECTED]] Sent: den 6 december 2002 14:38 To: [EMAIL PROTECTED] 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
