period / period units, NOT duration...
A period unit of hours and period of 84 would result in a twice per week
schedule, 56 for a 3 per week schedule. The example below of 48 and 72 could
be accomplished easier with period unit of days not hours.
Two posts in about 90 minutes, excited Kelly?

From: "Kelly J. Lipp" <lipp AT STORSOL DOT COM>
Reply-To: lipp AT storsol DOT com
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: 1 Schedule with different day's
Date: Thu, 7 Oct 1999 16:29:06 -0600

Looks like he's back!

Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs CO 80949
719-531-5926
www.storsol.com
lipp AT storsol DOT com

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
ADSM DUDE
Sent: Thursday, October 07, 1999 4:00 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: 1 Schedule with different day's


>>i have a question concerning the ADSM scheduler. I was looking   > >>for
the feature to say that a backup should run "Mon to Wed and  > >>Fri" in
one schedule.
>>But it seems that this is not possible. So i have to create >>several
schedules, one for each day.

>We solve a similar problem to this by resetting the startdate >of the
schedule to "today+2" each Wednesday (after the Wednesday  > >schedule has
run!).
>With the ADSM server running on AIX, we do this via a cron job
>Regards,
>Bob Douglas
>Oxford University Computing Services

Although this won't do a run 3, skip 1, run 1 scenario as easily as >Bob's
suggestion, another way to tackle running a schedule when you >want it
would be to update the schedule period units to hours and >then set the
schedule period to 48 for every 2 days, 72 for every 3 days, etc.
Unexpected boots, or anything else causing the >scheduler process to
recycle, would cause a
little trouble though! Scheduling client scheduler stop/start via NT >at or
Unix cron could be used to re-sync.

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com