Hello, Folks!
We happened to have the TSM Server down during a time when a certain client
would have been polled for a backup that was to take place 12 hours later.
Our polling intervals are 4 hours apart. TSM last polled this clients 4
hours previously, and did not resume any polling of this client until the
next day, when the client scheduler service was recycles. In the meantime,
they missed their backup.

Did polling for this client stop because the TSM Server happened to be down
during the time this client would have been polled? Does missing even 1 poll
suffice to require recycling of the scheduler service for the client?

It seems that we are always needing to have clients recycle their scheduler
services, for reasons often unclear. We often don't know until the client
has missed their backup -- we really need to know beforehand, so we can
better prevent missed schedules. If somebody can produce or point us to a
summary of which conditions require recycling of client scheduler services,
we would be most grateful. We would also welcome any other tips on how to
deal with this situation -- especially if there is a way to automate this
into a non-issue. Thanks, in advance.

Peter Glass
Distributed Storage Management (DSM)
Wells Fargo Services Company
> * peter.k.glass AT wellsfargo DOT com
>