Hi again,

On UNIX machines, some parameters could be better tuned than on NT


On the client dsm.opt

TCPBUFFSIZE                   32
TCPWINDOWSIZE           48          * could be set to 64 on UNIXEX (RFC1323)
                                    * Windows platforms are not compliant,
=> 63 max
                                    * 48 is the best choice for Windoze 
TXNBytelimit            25600           * 2048 if UNIX TSM SRV, 25600 if NT
TSM SRV



> -----Message d'origine-----
> De : Dirk Billerbeck [mailto:dirk.billerbeck AT GECITS-EU DOT COM]
> Envoyé : jeudi 15 mars 2001 16:34
> À : ADSM-L AT VM.MARIST DOT EDU
> Objet : Re: TSM vs NSR Performance
> 
> 
> Hello Stefano,
> 
> performance tuning isn't easy but after what I have learned 
> there are some
> parameters that can have a great impact on backup/restore performance:
> 
> On the client side:
> 
> - Increase the value for TXNBYTELIMIT (e.g. 25600 according 
> to the old ADSM
> v3.1 performance tuning guide)
> - Increase the value for RESOURCEUtilization to a value > 3 
> (remember: no.
> of data sessions = resourceutilization - 1, because there is 
> always one
> control session)
> - Set TCPBuffsize 31 (With TWO f !!!)
> - Set TCPNodelay YES
> - Set LOGMODE QUIET (For scheduled sessions)
> - Set QUIET (For non-scheduled sessions)
> - Set COMPRESSION No
> 
> On the server side:
> 
> - Increase the TCPWINDOWsize parameter to 63 (Important for the backup
> performance)
> - Set TCPBufsize 32 (With ONE f !!!)
> - Use TCPNOdelay YES
> - Set TXNGROUPMAX to 256
> - Set USELARGEBUFFERS to YES
> 
> Good luck!
> 
> Mit freundlichen Grüßen,
> Met vriendelijke groeten,
> With best regards,
> Bien amicalement,
> 
> CU/2,
>                 Dirk Billerbeck
> 
> 
> Dirk Billerbeck
> GE CompuNet Kiel
> Enterprise Computing Solutions
> Am Jaegersberg 20, 24161 Altenholz (Kiel), Germany
> Phone: +49 (0) 431 / 3609 - 117, Fax: +49 (0) 431 / 3609 - 190,
> Internet: dirk.billerbeck @ gecits-eu.com
> 
> 
> This email is confidential. If you are not the intended recipient,
> you must not disclose or use the information contained in it.
> If you have received this mail in error, please tell us
> immediately by return email and delete the document.
> 
> 
> 
> 
> 
> Stefano_Massi AT SACMI DOT [email protected] on 15.03.2001 15:41:53
> 
> Please respond to ADSM-L AT VM.MARIST DOT EDU
> 
> Sent by:  ADSM-L AT VM.MARIST DOT EDU
> 
> 
> To:     mailbox.dekelnsm
> cc:
> Subject:  TSM vs NSR Performance
>                                                               
>               
>                                                               
>               
>  
> --------------------------------------------------------------
> ------------ 
> 
> 
> 
> Hi all,
> 
> we are using TDP for SAP R/3 v3.1.0.4 for NT/Oracle, on a 
> client connected
> to a TSM Server 4.1.2.0 (Windows NT) through a Gigabit 
> network. An online
> backup of the whole DB (about 130 MB), directly to DLT tapes with two
> sessions, lasts over 2 hours, that means about 60 GB/h.
> 
> Before migrating to TSM, we were able to back up the same 
> database in about
> 1 hour and 15 minutes (about 105 GB/h) using Legato NSR.
> 
> I tried to change network parameters to improve the data 
> transfer rate, but
> without success. So I tried to backup to disk storage pools 
> and I got a
> poor 30 GB/h.
> 
> Finally, I decided to define disk storage pools in EMC2 
> storage disks, back
> up directly to them, and I obtained about 107 GB/h! But my 
> customer doesn't
> want to "waste EMC storage space for TSM storage pools", so 
> I'm looking for
> an alternative  solution...
> 
> Any ideas?
> 
> Thanks in advance,
>                Stefano Massi
> 
>