You know, that randomization thing only works if the client is using POLLING mode, which most people don't like. If you're using PROMPTED mode for most/all clients, RANDOMIZATION is ignored. So, to keep from slamming your network, you have to make an 8PM schedule with 20 nodes, and a 9PM schedule with 20 more, etc.
Of course, nowadays many people have a dedicated backup network for their larger clients (SAN or maybe just another 100Mbps switch), so slamming a network that you own is probably OK. > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of > Mark Stapleton > Sent: Monday, September 30, 2002 2:48 PM > To: [EMAIL PROTECTED] > Subject: Re: Discussion: 1 server sched for all vs 1 for each node > > > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of > > Markus Veit > >>if you have several client nodes, would it be better to have one client > >>schedule > >>were all nodes are in or would it be better to have one schedule > >>per node spread over time. > > TSM uses a randomization factor in all schedules, so as to avoid multiple > clients all hitting the server at the same time. You didn't > specify which OS > platform, so I'll point you at the Windows 5.1 Administrator > Guide page 376 > for details. > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of > Tomas Hrouda > > by my opinion you must not make extra schedules for simple > > clients, because > > files are migrated form diskpool "per node" at the time. If several > > migrations occured during backups, I thing your diskpool is too small. > > This is incorrect. > > -- > Mark Stapleton ([EMAIL PROTECTED]) > Certified TSM consultant > Certified AIX system engineer > MCSE > > > > > Hope this helps. > > > > Wiht best regards > > Tom > > > > > > > > Any feedback would be appreciated. > > > > Mit freundlichen Gr|_en / Best Regards > > > > Markus Veit > > > > > > = > > >
