Run "Q STATUS" command, and look at "schedule randomization percentage".

You can read about it in the Admin Guide, look in the index under
"randomization".

In my experience, whenever you can, make the schedule startup window as
large as possible.
If you have a group of severs that can back up any time between 6pm and 6am,
give them the whole 12 hours as the startup window for the schedule.  That
puts the lowest load on your network, and gives your clients time for a
couple of retries if they have to.  

***********************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
************************************************************************


     

> -----Original Message-----
> From: Rupp Thomas (Illwerke) [SMTP:thomas.rupp AT ILLWERKE DOT AT]
> Sent: Friday, July 07, 2000 4:23 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      AW: Conceptual question on ADSM scheduling
> 
> When you define a schedule you can also define a "startup window".
> ADSM spreads the startup of the defined nodes over this time frame.
> Maybe in the archives you can find the algorith ADSM uses to start
> the backups.
> We backup about 40 clients defined in one schedule with a startup window
> of
> 1 hour.
> Hope this helps
> 
> Kind regards
> Thomas Rupp
> Vorarlberger Illwerke AG
> MAIL:   thomas.rupp AT illwerke DOT at
> TEL:    ++43/5574/4991-251
> FAX:    ++43/5574/4991-820-8251
> 
> > -----Ursprüngliche Nachricht-----
> > Von:  Daniel Swan/TM [SMTP:Daniel.Swan AT TELUS DOT COM]
> > Gesendet am:  Freitag, 7. Juli 2000 21:56
> > An:   ADSM-L AT VM.MARIST DOT EDU
> > Betreff:      Conceptual question on ADSM scheduling
> > 
> > I'm just learning ADSM, but have been tasked to take over the ADSM of a
> > national corportation.  I'm having some trouble getting my head around
> > certain ADSM concepts.
> > 
> > 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 seems a bit ludicrous to me that similar servers will be backed up
> > simultaneously..... can anyone clarify this for me?
> > 
> > Best regards,
> > Daniel Swan