Did you check the Dr. Watson Log to see if there was an error posted to it.
If there was then call Tivoli support and send them the log. They can
usually figure things out from there.
We have different levels of clients. One thing we have seen cause this
problem is to much work going on ,on the server. What size of server to you
have and how much memory do you have in it? We have seen with older 166 Mhz
machines the schedule will just stop some times do to workload of the
backup. Sometimes other applications running on the box have caused the
scheduler service to fail. Even faster boxes with the new clients (3.7 and
4.l) if you resource utilization set to high the scheduler service can stop.
In most cases when it stops you should see a Dr. Watson error.
What do try? First thing we try is a reboot of the machine. Magically in
most cases that fixes the problems. For some smaller servers they are OK
for a while but the problem just returns. For these we set
memeoryeffecientbackup yes.
If you set backup registry to no realize that your registry won't be backed
up during incremental backups. If you set this you should backup the
registry manually. However, I don't suggest doing this.
Kyle
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Selva, Perpetua
Sent: Thursday, October 05, 2000 07:52
To: [EMAIL PROTECTED]
Subject: Re: ADSM SCHEDULER
Hi
Thanks for all the responses.. However, i have tried everything that has
been suggested.
I'm puzzled... Could it be something to do with the Version i'm running..
Server 3.1.2.20 and
Client 3.1.08
Thanks in Advance
-----Original Message-----
From: Palmadesso Jack [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 05, 2000 10:53 AM
To: [EMAIL PROTECTED]
Subject: Re: ADSM SCHEDULER
You may want to try removing and reinstalling the service with the dsmcutil
command.
As to why it stopped in the first place look in the nt event viewer also
review your activity log on the server. Also look in the dsmsched.log and
dsmerror.log if you have not.
Jack
-----Original Message-----
From: Selva, Perpetua [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 05, 2000 10:34 AM
To: [EMAIL PROTECTED]
Subject: Re: ADSM SCHEDULER
There is no specific errors that seem to point to anything unusual.. One day
it will work, the other day, it won't.. Sometimes 'it says client severed',
at other times, it has missed schedules. Whatever the case maybe, the
client server's adsm scheduler would have stopped by itself..
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 05, 2000 10:27 AM
To: [EMAIL PROTECTED]
Subject: Re: ADSM SCHEDULER
>Can someone please let me know why the 'adsm scheduler' would stop for no
>reason .. especially on an NT4.0 running metaframe/winframe applications..
I don't have a specific answer for you, but would seek out any dsmerror.log
indications that may be left behind. Richard
