Yotin,

If you mean "can you tell if the scheduler is running", issue the
ps command and grep for 'dsmc sched' and look to see if there is
a process running. If, however, you mean to ascertain whether or
not the actual scheduled command (backup or archive) is running,
you can still do this. In this case, what you need to look for in
the ps output is a 'dsmc' process that is the child of the
aforementioned 'dsmc sched' process. When the server contacts the
client, the client process forks a child to do the actual
work--the first processor is in a sense the "listener," while the
child is the one doing the actual work.

There are actually many reasons why a scheduled client event
might be missed. A network outage between server and client will
cause the client schedule to be missed, as will an overloaded
server that simply runs out of time during the schedule window.
When ADSM flags a client as having "MISSED" its schedule, it
means simply that: the server and client were unable to get
together and perform the scheduled operation, and the window of
time has passed.

As for restarting the scheduler, there are ways far less drastic
than rebooting the machine in order to get the dsmc process
running again. In most cases, there is either a startup script
(often found in /etc/init.d/adsm) or an entry in the inittab.
Simply running the startup script, or forcing the system to
re-read the inittab can get the scheduler running. Or you can
start it by hand, simply executing the command 'dsmc sched' from
a command line. You need to run this as a detached process, which
is accomplished by a myriad array of methods, depending on your
OS and shell.

 -- Tom

Thomas A. La Porte
DreamWorks Feature Animation
tlaporte AT anim.dreamworks DOT com


On Tue, 26 Jan 1999, Nelson Reis wrote:

>Yotin,
>At the ADSM admin command line type in q event * * to see if the
>schedules are completed, failed or missed. If the Unix box says missed
>then the dsmc sched is not running. The only way to get it running again
>is to restart the Unix box where the dsmc startup commands are in the
>initab file.
>
>Hope this helps,
>Nelson.
>
>>>> Yotin Chennavasin <yotin.chennavasin AT HGUARD DOT COM> 01/26/99
>01:58pm >>>
>Is there a way to tell if the ADSM backup or archive (schedule) is
>currently
>running by using the UNIX "ps" command ?
>or is there any other way to tell at all.
>