That sounds to me like your volume mount got preempted by a higher
priority operation, like a restore.  Can you check the server actlog and
see if something grabbed your volume/mount point?

-Lloyd

On 09/06/2011 01:12 PM, Zoltan Forray/AC/VCU wrote:

I don't think there is a firewall.

Well, it got further (700GB) before being killed by the TSM server.

9/6/2011 12:05:04 PM ANR0524W Transaction failed for session 59224 for
node ACIPENSER.VCU.EDU (TDP MSSQL Win32) - data transfer interrupted.
9/6/2011 12:05:05 PM ANR0487W Session 59224 for node ACIPENSER.VCU.EDU
(TDP MSSQL Win32) terminated - preempted by another operation.

At this rate, I don't think it is possible to back it up, especially if it
is making this 1-4TB transaction.

I again have to ask the question - can you tell the SQL TDP to break-up
the backup into multiple transactions, like you can with the Oracle TDP?



From:   Thomas Denier<Thomas.Denier AT JEFFERSONHOSPITAL DOT ORG>
To:     ADSM-L AT VM.MARIST DOT EDU
Date:   09/06/2011 10:27 AM
Subject:        Re: [ADSM-L] LARGE MS-SQL TDP backup keeps failing
Sent by:        "ADSM: Dist Stor Manager"<ADSM-L AT VM.MARIST DOT EDU>



-----Zoltan Forray wrote: -----

I am trying to backup a LARGE SQL (4TB) database via the SQL TDP,
without success.

It will run for a while and then die - usually with the error:
ANS1017E (RC-50): Session Rejected : TCP/IP communications failure.
The last try backed up 125GB before failing.

I have greatly increased the server communication timeout (6000
seconds) guessing it is a timeout issue.

I know very little about the SQL TDP (v5.5.5.0 - base TSM client is
6.1.3.2 - yes I know it needs updating) and config options.  Is there
a way to breakup the backup into chunks, like you can do with Oracle
backups?

Suggestions?

Does the backup pass through a firewall? Firewalls generally have a
timeout period for idle TCP sessions. This is rarely more than an
hour, and I have heard of firewalls with the timeout set as low as
15 minutes.