Andrew21210
ADSM.ORG Member
- Joined
- Apr 10, 2008
- Messages
- 97
- Reaction score
- 2
- Points
- 0
We are backing up several large SQL flat file .bak, .trn and .diff files on a nightly basis. Approximately 2.3 TB. This takes 12-14 hours to complete. I have been looking for possible solutions to speed this backup time and I may have stumbled across something but I wanted to get some expert input.
TSM Server version is 5.5.6 and the client is a Windows 2003 cluster. Our TCPWINDOWSIZE is set to 131,072 on the TSM server and 128 on the client (although that only affects restores/retrieves). The client does NOT have TCP Windows Scaling enabled in the OS so therefore defaults to 64k. The Windows 2003 operating system CAN leverage TCP Windows Scaling but it must be manually enabled via a registry edit.
So my question is this: If I get the Windows OS group to enable TCP Windows Scaling, should I see a positive performance bump for this backup?
TSM Server version is 5.5.6 and the client is a Windows 2003 cluster. Our TCPWINDOWSIZE is set to 131,072 on the TSM server and 128 on the client (although that only affects restores/retrieves). The client does NOT have TCP Windows Scaling enabled in the OS so therefore defaults to 64k. The Windows 2003 operating system CAN leverage TCP Windows Scaling but it must be manually enabled via a registry edit.
So my question is this: If I get the Windows OS group to enable TCP Windows Scaling, should I see a positive performance bump for this backup?