From: Alex Mounayar <Alex.Mounayar AT SMED DOT COM>
Subject: question about postschedulecmd if backup command does run
To: ADSM-L AT VM.MARIST DOT EDU
Content-Length: 680
Status: RO

We have noticed a possible problem with postschedulecmd processing
if the backup command doesn't run for some reason.

We use the pre and post -schedulecmd to stop and start a database
application.  However if the scheduled backup command(incremental in this case)
doesn't run neither does the postschedulecmd which leaves the database
application down because the preschedulecmd had already run.
*** *snip*



     We are actually using the presched to take it down and postsched to bring
it back up, and the presched also kicks off a monitoring tool which keeps an
eye on things to verify nothing has gone awry.

***
-preschedcmd
 Down the database
 Down the database

 Monitor the backup to verify that it is still running, and to verify that
   the allowable amount of time has not passed (DB people seem to be unhappy
   when their database is still down at 8am). We send notifications when
   things go bad, but depending on the necessity, you could kill the adsm
   process and up the database using this script as well.

-postschedcmd
 Bring the DB back up.
 Bring the DB back up.
***

     Of course, it is imperative that the monitor is bulletproof - it doesn't
help things a bit if everyone thinks they will be notified in case of failure,
and they aren't.

Hope this helps!

Regards,
David Barber