We recently changed the destination of the majority of our backups from a tape
pool to a disk pool. When we were backing up to the tape pool the number of
active backups was restricted by the number of tape drives we allowed ADSM to
use. Now, without this restriction we have so many backups running
simultaneously that, although all the backups are completing in the backup
window, the run time of each individual client backup is, in some cases more
than twice what it used to be. I know that the purpose of the MAXSCHEDSESSIONS
is to regulate the number of sessions. I hesitate to lower our (it's currently
set at 40) because there are times, even at the current setting, when the 'no
available sessions' message is sent to clients - usually when the system is
bogged down with other work. Has anyone else found another way of dealing with
this? I can't see myself spending alot of time monitoring the run times of
130+ backups and tuning the schedule to accomodate. Thanks for any responses.
|