ADSM-L

Re: [ADSM-L] Win2K3 backup performance

2008-02-01 02:52:39
Subject: Re: [ADSM-L] Win2K3 backup performance
From: Henrik Vahlstedt <SHWL AT STATOILHYDRO DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 1 Feb 2008 08:52:10 +0100
Hi,

Have you recently upgraded the client, and are you using scheduled
backups with sessioinitiation=serveronly?
>From 5.3.5.3 to latest 5.4 client I have an issue with above settings
and performance. 
Ie, with newer clients performace drops with 70-80% when I backup larger
files > 1Gb.
Dsmc and sessioinitiation=clientorserver works fine.

//Henrik


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Sam Sheppard
Sent: den 1 februari 2008 01:09
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Win2K3 backup performance

We have a Windows 2003 client running TSM 5.4.1 backing up to a Solaris
10 TSM server running the 5.4.1 server.

The client has several very large files to be backed up (300-400GB). We
are finding on a 1.3GB test file that we can only get a throughput of
about 10MB/sec (looks like 100Mb speed) even though this client is
configured on a GigE VLan.  One interesting aspect just discovered is
that a restore of the same file got speeds of 37MB/sec, which is about
the same as an FTP of the same file from the client to the server.
Client, switch, and server all set to 1GB full.

At this point, I'm completely mystified as to what might be behind these
performance anomalies.  I would expect much higher throughput rates on
all of these tests, but would be satisfied if the backup would just
perform at the same speed as the others.

Client options:                  Server Options:

TCPWindowsize   63               TCPWindowsize      131072
TCPBuffsize  32

Thanks
Sam Sheppard
San Diego Data Processing Corp.
(858)-581-9668


-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.

<Prev in Thread] Current Thread [Next in Thread>