Mahesh, This came up, in a slightly different fashion, last week. As I noted then, the last thing in a trace on the TDP is a TCPFLUSH. We haven't tried a trace with the .BAK, but I wouldn't be surprised if it was similar. A new NIC gave some relief, but Support has been scratching their coolective heads for months.
________________________________ From: ADSM: Dist Stor Manager on behalf of Mahesh Tailor Sent: Mon 12/17/2007 9:33 AM To: [email protected] Subject: [ADSM-L] MSSQL Server Backup 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
