No backup until service restarted

[szp]

Hello,

I have a Windows 2008 R2 64-bit server with SP1.
I have TSM BA client 6.4.1 and TSM TDP SQL client 6.4.1.1 installed.

Everything works OK - almost. The issue here is that no new SQL backup will start until I restart the TSM service. Once it's done, the backup completes fine. After that the service stays "Started".


These are the details of the service:

TSM Windows NT Client Service Configuration Utility
Command Line Interface - Version 6, Release 4, Level 1.0
(C) Copyright IBM Corporation, 1990, 2013, All Rights Reserved.
Last Updated Jul 18 2013
TSM Api Version 6.4.1

Command: Query TSM Client Service Parameters
Machine: <mymachine> (Local Machine)

Connecting to service 'TSM SQL Client Scheduler' ...

Service Configuration/Status:

Service Name   : TSM SQL Client Scheduler
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\dsm.opt
TSM Client Node     = <mymachine_sql>
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\dsmsched.log
Error Log           = C:\Program Files\Tivoli\TSM\TDPSql\dsmerror.log
Cluster Enabled     = (value not currently set)
Cluster Name        = (value not currently set)

Some of the entries in the option file. (I have removed the TSM server address and the node name.)

TCPPort    1501
TCPCLIENTPORT    1510
passwordaccess    generate
schedmode    PROMPTED
ERRORLOGRetention 31 D
SCHEDLOGRetention 31 D

Again: once the service is restarted (after each backup), the next scheduled backup kicks off and completes successfully.

I have recreated the service, restarted the computer, same thing happens. I have a bunch of servers with the exact same setup, they work OK. This one is acting the maggot.
Any idea why and how to fix it?
Thanks in advance

 

[moon-buddy]

Delete the services and do a repair of the TSM BA and TDP for SQL installation.

Reinstall the services after the repair.

 

[marclant]

Any idea why and how to fix it?

First, we need to know why it stopped.

Before restarting, check the tail of dsmsched.log and dsmerror.log for errors. It may indicate a reason why it did not run.

 

[marclant]

I just noticed your schedmode is prompted. Check the TSM Server at the time of the previous schedule to see if the TSM Server had issues contacting the client.

Also, if you don't need prompted (firewall or need to run clientaction), then may want to use schedmode polling instead.

 

[LED888]

If there are not hints the any of the logs. And if the results are the same with schedmode prompted.

Update the schedule backup to start in 60 seconds, start the schedule service for the API in the foreground and watch the messages to see if there are any hints.

Also in the actlog, are there any messages around the time frame of the schedule backup?

Are there enough schedule sessions?

Good Luck,
Sias