Rose, we scheduled a script to verify the scheduler is up and running,
about 2 hours
before backup schedule.
This enables up to catch problems near backup point.
The verification is done by killing the process and restarting it verfying
the logs indicate
it succeeds in reaching the server.
We first kill since their is no 100% way we know of to ACK it's running and
available.


Jack Bezalel
Systems Management & Development support manager
MIS
MEMCO Software
Phone: 972-3-6450072
mailto:jack AT memco.co DOT il






vkm/09:13 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



  To:          ADSM-L AT VM.MARIST DOT EDU

  cc:          (bcc: Yaakov Bezalel/Tel Aviv/Memco Software)



  Subject      Re: keeping scheduler started on version 3
  :            clients







At 12:44 PM 3/9/99 -0700, Campbell, Rose wrote:
>Has anybody experienced problems keeping the scheduler started in the
>version 3 client?  We have Sun and Irix clients that we cannot keep the
>scheduler going on.  If you have had this how was it remedied?  We have
>tried every conceivable way to keep this started to no avail.
>
>Thanks,
>Rose M. Campbell

Rose,
We use a script that we call dsmsched.startup, which looks like this:
--
#!/bin/sh
#!/bin/sh
#
# This shell script will start up the ADSM Scheduler.
#

INSTDIR=/usr/lpp/adsm/bin

# Start up the ADSM Scheduler.
if [ -f ${INSTDIR}/dsmc ]; then
        cd /tmp
        nohup ${INSTDIR}/dsmc schedule 2>&1 > /dev/null &
        (/bin/echo ' Starting ADSM Scheduler.') > /dev/console
else
        /bin/echo "File ${INSTDIR}/dsmc was not found."
        /bin/echo " The ADSM Scheduler could not be started."
        /bin/echo " This probably means that ADSM is not installed."
fi
--
I have noticed on two occasions recently that a scheduler has gotten hung
I have noticed on two occasions recently that a scheduler has gotten hung
up.  The scheduler log looks like the scheduler just stopped in the middle
of a backup.  The scheduler is still a running process, but the ADSM
session is gone.  Is this what you are seeing, or is your scheduler process
disappearing as well?  If the latter, then the above technique may help
you.

..Paul