Zlatko, This is SAN throughput. The NamedPipe setting is for the Storage Agent to talk to the Backup/Archive client. We are writing to STK 9940 tape drives and letting the tape drives do the compression.
Thanks, Brian Scott EDS - Enterprise Distributed Capabilities MS 3278 Troy, MI 48098 * phone: 248-265-4596 (8-365) * mailto:[EMAIL PROTECTED] -----Original Message----- From: Zlatko Krastev/ACIT [mailto:[EMAIL PROTECTED]] Sent: Sunday, December 16, 2001 9:12 PM To: [EMAIL PROTECTED] Subject: Re: NamedPipe settings on W2K client Where are you getting this throughput - LAN or SAN? LAN-free storage agent transfer relatively small ammounts of metadata over LAN and you cannot achive best possible peak rates there. For LAN data transfer you should be able to achieve at least 7-8 MB/s so the problem could be with TCP/IP settings not Named Pipes. SAN throughput is limited by both tape drive and the application providing the data stream. For filesystems this is the storage agent itself. But what is the tape drive you are writting to and isn't it the bottleneck (LTO can be too fast and constantly lose streaming)? Are you using client or tape compression? Zlatko Krastev IT Consultant "Scott, Brian" <[EMAIL PROTECTED]> on 14.12.2001 21:13:11 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: NamedPipe settings on W2K client Does anyone know if any NamedPipe performance settings? We're running the latest 4.2.x TSM B/A client on a Win2K box running LAN-free to a Sun Microsystems Sunfire backup server (TSM 4.2.1.7). We've noticed that using NamedPipe between the TSM Storage Agent and the TSM backup server is almost twice as fast as traditional IP based but we're only able to get about 3 - 4MB/s throughput. Are there any settings pertaining to NamedPipe we can use? Thanks, Brian Scott Infrastructure Analyst EDS - Enterprise Distributed Capabilities MS 3278 Troy, MI 48098 * phone: 248-265-4596 (8-365) * mailto:[EMAIL PROTECTED]
