I'd like to thank everyone for their help with my question... It's quite
clear to me now.
I think it also makes moot my question about a visual schedule managing
tool.


Best regards,
Dan.


Daniel Swan
HP Unix Team
ISM-BC
3030 2nd Ave SE
Calgary, AB, T2A 5N7
ph. 403-530-1726
fax: 403-530-1066




> -----Original Message-----
> From: Joe Gross [SMTP:jgross AT STIMPY DOT NET]
> Sent: Friday, July 07, 2000 3:50 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Conceptual question on ADSM scheduling
>
> On Fri, Jul 07, 2000 at 12:56:13PM -0700, Daniel Swan/TM wrote:
> > Lets assume I backup 15 NT servers, all of them associated with a
> schedule
> > named "NT-DAILY", which
> > kicks off at midnite sharp, Doesn't this cause a huge spike in load at
> > midnight sharp?  Is there a better way to spread this load, or do I have
> to
> > create different schedules like:  "NT-DAILY-1AM", "NT-DAILY-2AM", and
> > associate them with a few servers each?
>
> It tends to be better to spread things out if you can then all your
> clients
> don't hammer the database at the same time when they first start up.
>
> I have a lot of big servers to backup and I tend to spread things out from
> about 8pm til about 6am. To keep myself sane I name my schedules the time
> they run and just directly associate the client with the time I want to
> have
> it run:
>
> adsm> q sched
>
> Domain           *     Schedule Name        Action     Start Date/Time
> Duration     Period     Day
> ------------     -     ----------------     ------
> --------------------     --------     ------     ---
> STANDARD               0000                 Inc Bk     10/27/1999 00:00:00
> 1 H        1 D      Any
> STANDARD               0100                 Inc Bk     10/27/1999 01:00:00
> 1 H        1 D      Any
> [...]
> STANDARD               2200                 Inc Bk     10/27/1999 22:00:00
> 1 H        1 D      Any
> STANDARD               2300                 Inc Bk     10/27/1999 23:00:00
> 1 H        1 D      Any