Re: [ADSM-L] Client domain statement exclude not working as expected

Andy, Richard, and all others,
1. THANKS for the instruction and advice.
2. I don't want to abuse the list or its members.  I think the exclude
fix will work, even though it is not perfection (I know your admonition
about "good enough").  This is just an exercise to determine why the
correct method didn't work as expected.


You may note that a different Client version is in use now.  My
co-worker upgraded this to address problems with memory allocation
(ANS1030E).

1 & 2 follow below
3 - My coworker and I have restarted the service repeatedly
today...while that could have been the problem, this had been working a
week ago.  This drive HAD to be excluded, because when it was
"successfully" backing up data it was blowing up the recovery log and DB
by itself.  In some respects it is like an HP Polyserve PSFS filesystem.
So you may ask, what changed?  We are not sure.

C:\Program Files\Tivoli\TSM\baclient>dsmcutil list

TSM Windows NT Client Service Configuration Utility
Command Line Interface - Version 6, Release 1, Level 3.5
(C) Copyright IBM Corporation, 1990, 2010, All Rights Reserved.
Last Updated Jul 25 2010
TSM Api Version 6.1.3

Command: List Installed TSM Client Services
Machine: NODENAME(Local Machine)
Installed TSM Client Services:
   1. TSM Central Scheduler
1 TSM Client Service was located.
C:\Program Files\Tivoli\TSM\baclient>dsmcutil query /name:'TSM Central
Schedule
'
TSM Windows NT Client Service Configuration Utility
Command Line Interface - Version 6, Release 1, Level 3.5
(C) Copyright IBM Corporation, 1990, 2010, All Rights Reserved.
Last Updated Jul 25 2010
TSM Api Version 6.1.3

Command: Query TSM Client Service Parameters
Machine: NODENAME(Local Machine)
Connecting to service 'TSM Central Scheduler' ...
Service Configuration/Status:
Service Name   : TSM Central Scheduler
Image Path     : "C:\Program Files\Tivoli\TSM\baclient\dsmcsvc.exe"
Logon Account  : ...blanked...
Start Type     : Auto
Current Status : Started

TSM Client Service Registry Settings:

Client Service Type = Client Scheduler Service
Options file        = C:\Program Files\Tivoli\TSM\baclient\dsm.opt
TSM Client Node     = NODENAME
Event Logging       = YES
Comm Protocol       = (value not currently set)
Server              = (value not currently set)
Server Port         = (value not currently set)
Schedule Log        = C:\Program Files\Tivoli\TSM\baclient\dsmsched.log
Error Log           = C:\Program Files\Tivoli\TSM\baclient\dsmerror.log
Cluster Enabled     = (value not currently set)
Cluster Name        = (value not currently set)

C:\Program Files\Tivoli\TSM\baclient>

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Andrew Raibeck
Sent: Thursday, January 20, 2011 4:17 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Client domain statement exclude not working as
expected

I suggest using dsmcutil to check the scheduler services:

1. Run

   dsmcutil list

to query for a list of installed services. I expect you have only one
scheduler service, but in general good to make sure that is the case.

2. For scheduler service xxx in the output from (1) above, run

   dsmcutil query /name:"xxxx"

to be *certain* it isn't using a different client options file.

3. Unless you are *certain* you stopped and restarted the scheduler
*after*
modifying the DOMAIN statement, stop and restart again and see if that
makes any difference.

If you are still coming up empty on this, then I suggest contacting IBM
technical support for further assistance.


IMPORTANT:  E-mail sent through the Internet is not secure. Legg Mason 
therefore recommends that you do not send any confidential or sensitive 
information to us via electronic mail, including social security numbers, 
account numbers, or personal identification numbers. Delivery, and or timely 
delivery of Internet mail is not guaranteed. Legg Mason therefore recommends 
that you do not send time sensitive 
or action-oriented messages to us via electronic mail.

This message is intended for the addressee only and may contain privileged or 
confidential information. Unless you are the intended recipient, you may not 
use, copy or disclose to anyone any information contained in this message. If 
you have received this message in error, please notify the author by replying 
to this message and then kindly delete the message. Thank you.