The duration is the window in which a scheduled event must start.
It also is the window in which a scheduled event which encounters errors may
attempt a "restart"
        Say a client node restarts (gets booted) during an incremental, if
it comes back up within the incremental
        backup's window then the event will restart and run to completion
A scheduled event runs either to completion or some critical error which
terminates it.

Why you get a "missed start up window", remember only one scheduled event at
a time, before an event may start, any previous scheduled event must
complete.  You have probably one of the following
        1) scheduler isn't running or is hung
        2) an earlier scheduled event is still running through the start
window of the one that misses
        3) that earlier scheduled event could be that same event from the
previous day... :-(

hope this helps
later,
      Dwight

> ----------
> From:         Joel Fuhrman[SMTP:joelf AT CAC.WASHINGTON DOT EDU]
> Reply To:     ADSM: Dist Stor Manager
> Sent:         Tuesday, April 18, 2000 5:36 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Question about scheduled backups !!
>
> If your talking about the DURation value as defined in the schedule, I
> have
> a different understanding of its use.  I believe it defines when the
> backup
> must start.  If the backup starts before the duration expires, the backup
> can run well past the duration.  If you increase the duration, you may
> avoid
> the error.
>
> Check your server and client logs to see if the server was trying to
> contact
> the client during the startup window.  If not, you may not have enough
> server sessions available.  From QUERY STATUS check Maximum Sessions,
> Maximum Scheduled Sessions and Schedule Randomization Percentage.
>
> On Mon, 3 Apr 2000, Mark Brown wrote:
>
> > The backup of the client may take 4 hours but you set the backup window
> > size at 3 hours (as an example).
> > Even though the backup does complete it ADSM is just comapling that it
> > did not end inside the 3 hour window.
> >
> > Increase the size of the backup window length. Thats one quick solution.
> > Juan Obando wrote:
> > >
> > > Hi ADSM'ers
> > >
> > > I have a RS/600 S70 Node, with ADSM server Ver 3.1 for AIX, The
> > > production data resides in the same box, then we set the schedule
> > > to run an incremental backup every day. But from time to time
> > > (ussualy after 4 or 5 days) the server shows the following message :
> > >
> > > ANR2578I Schedule RESPALDO_DIARIO in domain SAFI for node
> > > MHSAFI has missed its scheduled start up window.
> > >
> > > What could be wrong ?
> > >
> > > Thanks in advance.
> > >
> > > Juan Reynaldo Obando
> > > Ministerio de Hacienda
> > > Proyecto SAFI
> > > El Salvador Central America
> >
>