Del,
 
We made the change and the backups have been running successfully.
 
Thanks for the tip.
 
Mahesh

>>> Del Hoobler <hoobler AT US.IBM DOT COM> 12/17/2007 11:13 >>>
Did you look into the known network issues that are being caused
by the Windows Server 2003 Scalable Networking Pack that Microsoft
added with regards to TCP Chimney offload, Receive Side Scaling,
and Network Direct Memory Access?

Here are a few KB articles to look at:

http://support.microsoft.com/kb/945977 

http://support.microsoft.com/kb/942861 


We have seen sporadic problems with symptoms like this
being caused by the TCP Chimney offload.
Disabling the TCP Chimney Offload feature is one way that
some customers have seen relief.

Thanks,

Del

----------------------------------------------------

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 12/17/2007
10:33:24 AM:

> Hello.
>
> TSM: 5.3.4.1 on AIX 5.3 TL5
> TSM BA Client: 5.3.4.0 (also tried a new patch level)
> TDP for MSSQL: 5.2.1.6
>
> Having a very odd problem.
>
> I have several TDP for MSSQL clients having a similar issue.  A
> backup starts at the scheduled hour.  All files that are <MAXSIZE
> backup fine.  If a file that is >MAXSIZE is found, on the client we
> see a "Waiting for Tape Mount" message in the log file.  On the
> server we see a tape mounted, however the client never proceed and
> the backup hangs.  We've let a backup sit until the session times-
> out and beyond to no avail.  To complicate this further, we took TDP
> out of the equation and created a MSSQL dump backup.  When we try to
> backup the dump using the regular TSM BA client, we get the same result.

>
> We thought network, however while the client is hung if we open an
> ftp session to the TSM server and do a dd transfer of ~3GB, no problems.
>
> This is happening only on some nodes.  Others are fine.
>
> Has anyone else seen this?  And, if so what was the resolution?
>
> TIA
>
> Mahesh
>