TDP Node platform issue

[dms19]

I have a TDP node thats showing up as a WINNT machine in the platform parameter of a q node. It should be showing as TDP MSSQL Win 64???!!??

Has anyone seen this before? Q occ and q Files show its getting the proper db data, but its showing up as the wrong platform.


Node Platform Policy Domain Days Name Name Last Access Password Set
----------------- ------- -------------- ---------- ----------
SQL_Server1 WinNT SQL 1 50
SQL_Server2 TDP MSS- SQL 1 50
QL Win64


Thanks!

 

[Efim]

Hi
I think you use TSM Scheduler with opt file from TDP.
When it update schedule from TSM Server it use TSM B/A client code. So it is normal.
If you run TDP for SQL GUI and run q node you can see right information.
Efim

 

[dms19]

thats the issue - its all configured properly and backing up normally however regardless of where I look the q node info returns WINNT not TDP SQL 64

 

[Efim]

We can check my assumption if you post output from:
dsmcutil query /name:"TSM Scheduler Service name for run TDP for SQL"
Efim

 

[dms19]

Both instances are (non-clustered) on the same machine, showing the same output but different platforms within TSM:


C:\Program Files\Tivoli\TSM\baclient>dsmcutil query /name:"TDP_SQL1"

TSM Windows NT Client Service Configuration Utility
Command Line Interface - Version 5, Release 5, Level 2.0
(C) Copyright IBM Corporation, 1990, 2009, All Rights Reserved.
Last Updated Mar 22 2009
TSM Api Verison 5.5.2

Command: Query TSM Client Service Parameters
Machine: SQL_SERVER(Local Machine)

Connecting to service 'TDP_SQL1' ...

Service Configuration/Status:

Service Name : TDP_SQL1
Image Path : "C:\Program Files\Tivoli\TSM\baclient\dsmcsvc.exe"
Logon Account : LocalSystem
Start Type : Auto
Current Status : Started

TSM Client Service Registry Settings:

Client Service Type = Client Scheduler Service
Options file = C:\Program Files\Tivoli\TSM\TDPSql\sql1.opt
TSM Client Node = SLQ1
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\TDPSql\SQL1_SCHED.LOG
Error Log = C:\Program Files\Tivoli\TSM\TDPSql\SQL1.LOG
Cluster Enabled = (value not currently set)
Cluster Name = (value not currently set)


#############################################################################

C:\Program Files\Tivoli\TSM\baclient>dsmcutil query /name:"TDP_SQL2"

TSM Windows NT Client Service Configuration Utility
Command Line Interface - Version 5, Release 5, Level 2.0
(C) Copyright IBM Corporation, 1990, 2009, All Rights Reserved.
Last Updated Mar 22 2009
TSM Api Verison 5.5.2

Command: Query TSM Client Service Parameters
Machine: SQL_SERVER(Local Machine)

Connecting to service 'TDP_SQL2' ...

Service Configuration/Status:

Service Name : TDP_SQL2
Image Path : "C:\Program Files\Tivoli\TSM\baclient\dsmcsvc.exe"
Logon Account : LocalSystem
Start Type : Auto
Current Status : Started

TSM Client Service Registry Settings:

Client Service Type = Client Scheduler Service
Options file = C:\Program Files\Tivoli\TSM\TDPSql\sql2.opt
TSM Client Node = SQL2
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\TDPSql\SQL2_SCHED.LOG
Error Log = C:\Program Files\Tivoli\TSM\TDPSql\SQL2_ERROR.LOG
Cluster Enabled = (value not currently set)
Cluster Name = (value not currently set)

 

[Efim]

Hi
You use Options file = C:\Program Files\Tivoli\TSM\TDPSql\sql1.opt for schedule and TDP backup. My assumption confirmed.
I try to explain again:
Schedule is B/A Client process. When nodename login to server it save platform as WINNT.
When TDP login to server (during backup) platform is "TDP MSSQL Win 64".
Depending on who is last login to server you can see different platform.
It is normal situation.

Efim

 

[dms19]

I wasnt sure what you were getting at the first time around. I agree with your assessment and when the scheduler last talks to TSM its WINNT, when the TDP client is last, its TDP SQL.

Just wanted to make sure we werent missing the boat!

Thanks!