Richard,
what kind of timeout values should I be looking at ?
If these values are set globally I cannot see why this one should fail since
I'm backing up much larger databases with no problem.
Just for reference this database is about 30G large.
Thanks
Yiannakis


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Richard Sims
Sent: 14 January 2004 14:35
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TDP for SQL backup fails


>I'm running 5 backups using TDP for SQL on Win2000 SP3 servers. One of them
>fails with errors that don't give me any clues as to what goes wrong.
>I've got TSM Server at 5.1.5 on Windows and TDP for SQL 5.1.5.
>The error message ANS1017E is unknown to my TSM. ACO5436E suggests to look
>for the next message for clues. And rc=418 or rc=402 cannot be found in the
>return code section of the messages manual.
...
>01/12/2004 20:32:18 Sqlserver                     : DWDSS
>01/12/2004 20:32:18
>01/12/2004 23:48:54 ACO5436E A failure occurred on stripe number (1), rc =
>418

Yiannakis - Indeed, all the return codes *should* be in the Messages manual:
            by all means use IBM feedback procedures to have the
publications
people get them in there.

Always keep in mind that the TDPs are based upon the TSM API; hence, you can
always fall back to the API manual for return code information...up to a
point.
That manual has the 418 (but not 402):
 DSM_RC_OPT_CLIENT_DOES_NOT_WANT 418 /* Client doesn't want this value*/
                                     /* from the server */

I'd recommend looking in the server Activity Log for further reasons.
Note the long period between the 20:32 session initiation time and the
23:48 failure message.  This *might* reflect the server abandoning the
client session because it exceeded timeout values - which may reflect a
problem with client processing (delays from disk reliability or being
pushed aside by other processes on the client) or the server timeout
values being too low.

  Richard Sims, BU