Schedule randomization only works with schedmode polling, where the clients
contact the server to start a backup.

If you're using schedmode prompted (which we prefer - we can kick off test
jobs
from the server whenever we want), then you have to make several different
schedules to spread out the load.

On the other hand, why NOT hammer the network? at 2 AM, will users suffer?
And
your typical NT box will be done in 10 minutes or less anyway, and alot of
that
time is client think time, not  network transmit time.

Another point is that a lot of organizations have a separate backup network,
or
switches partitioned into VLANs, or even a real Storage Area Network,
dedicated
to doing things like backups.  So it's perfectly alright to slam that
network.

Daniel Swan/TM wrote:

> 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

--
Mr. Lindsay Morris
Mr. Lindsay Morris
Certified: AIX,ADSM, TSM, HACMP,SP
Gresham Enterprise Storage
lmorris AT openmic DOT com
606-253-8000