I would suggest freqeuncy based shceudling too and used correctly it
can be very powerful and you can build some good caveats into it.

If you want to use calender based and have this issue, you could try
limiting the number of jobs per hours to 1. ( Global Attributes on
master server properties ). This would mean it would not run after a
successfull backup.

Hope this helps


On Wed, 22 Sep 2004 13:17:28 -0400, Nash, Ebon <ebon.nash AT compuware DOT com> 
wrote:
> I have a policy setup with the following calendar based schedule
> 
> Retries after runday checked
> Calendar Schedule:  Recurring Weekdays, Every M,Tu,W,Th,Fri,Sat
> Start Window Mon 10:00pm to Tue 3:00am
> 
> If the job starts and completes before 11:59pm Mon, it runs again at 12:00am
> Tue.  I'm concerned that if we shrink our window to 10:00pm to 11:59pm, and
> the job sits queued for too long that we will get 196 errors.
> 
> Any recommendations on how to handle this?  We would like to solve this
> while using calendar based scheduling, if possible.
> 
> Ebon Nash
> Enterprise Storage Administrator
> Compuware Corporation
> One Campus Martius
> Detroit, MI 48226
> 313-227-5109
> 
> The contents of this e-mail are intended for the named addressee only. It
> contains information that may be confidential. Unless you are the named
> addressee or an authorized designee, you may not copy or use it, or disclose
> it to anyone else. If you received it in error please notify us immediately
> and then destroy it.
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 
>