Quoting Karel Bos [EMAIL PROTECTED]:
Hi,
We have changed our scheduling mode from prompted to polling. Scheduled
back-ups run fine. The immediate client schedule won't run. The status of
the immediate schedule turns to pending and will not function.
It will run as soon as your client polls
Quoting Ted Byrne [EMAIL PROTECTED]:
Has anyone received a similar response from TSM support in the past? We
are working on an issue with a process running for a very long time, and
received the following as part of the response from TSM support:
[W]as that the
run-time
Quoting Philippe Girard [EMAIL PROTECTED]:
I do not know what platform you are working on,
but with your scheduler if you can send command to TSM like:
DSMCADMC -ID=xxx -PA= command
you can control TSM from your scheduler.
You got the question the wrong way around. We
Quoting Daniel Sparrman [EMAIL PROTECTED]:
Hi
I don't know what kind of OS you're using, but the pending move is only on
the TSM server. That because it's not the server that controls the
schedule, only the client.
If you look at the log on your client , it will tell you if it has received
Quoting Remco Post [EMAIL PROTECTED]:
The problem is that if for example you have 1000 clients scheduled to
backup during an 8 hour window, it would be nice to know which clients
have non functioning scheduler daemons at the beginning of the window
rather than at the end of the window
Does anyone know of a 3rd party scheduler that works well
with TSM. Preferrably one that has a scripting or programming
api, since our goal is to automate adminstration of TSM. If
the scheduler has a client portion then it should have a small
footprint install and admin wise, and adequate
