TSM 5.1on W2K server, all clients miss schedules

[Marv72]

TSM 5.1 installed on W2K server, and 2 w2k clients. The clients backup when backup is started from client, and data is migrated within the storage pools. However both the clients miss their scheduled backup windows, even though they are associated with the schedule, and the scheduler runs prompted on the clients.

 

[gwichman]

if you examin the TSM server activity log around the time of the backup window, does it have entries to the effect of attempting to contact client such and such? but never receives an answer and therefore the client misses it's backup?

are you sure your TSM scheduler service is installed and running (or tsm accepter service depending on what mode you're running)? have you tried stopping and restarting the tsm scheduler and checking the dsmsched.log file and/or the tsm server activity log to see if it contacts the tsm server ok when the service is first started?

honestly the most common reason a client misses it's schedule is because the scheduler isnt running.

 

[davemak]

Agree with gwichman, we had similar problems with W2K and NT, was down to scheduler not running, check dsmsched.log also watch out for mis-match on release levels, ensure your client is at the latest level (5.1.5.6) have seen problems with older levels especially 4.2.