Well, we don't advertise them as such, but several options can be used to throttle performance (just as increasing their values can improve performance, decreasing their values can inhibit performance):
- Turn down the TCPBUFFSIZE and TCPWINDOWSIZE settings - Turn on client compression (uses more CPU, which may or may not impact network performance, but will reduce the amount of data going across the network, which may contribute to the desired effect) - Set RESOURCEUTILIZATION to its lowest setting - Set TXNBYTELIMIT to its lowest setting - On the TSM server, reduce TXNGROUPMAX (if you want to do this for all TSM clients) - On the TSM server, set VALIDATEPROTOCOL=ALL for the node (note that this will consume more CPU on client and server in order to calculate CRCs, see Admin Guide and Reference for more info) There may be some others, but those are the ones that come immediately to mind. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply) The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. Eric Winters <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 12/02/2002 15:45 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Can backup throughput be deliberately throttled on a per node basis. I have an unusual situation where we are interested in deliberately throttling network performance, that's right, we might want to slow down backups from nodes and from server to server. Furthermore it has been suggested to me that this capability is available in TSM. Apart from tweaking the communication options to impair client and server communication performance (breaks my heart to consider doing it), is there something specificly designed to restrict bandwidth usage within TSM? I appreciate the feedback, Regards, Eric Winters Sydney Australia