Re: TDP for SQL backup fails
>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. Yiannakis - You would approach adjustment of server timeout values if your review of the server Activity Log indicated that it terminated the session due to IDLETimeout or COMMTimeout issues. (If your server is using the defaults for these values, I'd recommend boosting them, as the the defaults are too low for ordinary use.) As the old expression goes, the size of the database doesn't matter: what would matter is the responsiveness of the client in its session with the server. We've seen how various things going on in a client at the same time (the classic being virus scanning) can impede progress. Be sure to follow Del's recommendations in looking into other areas for possible evidence of cause. Richard Sims, BU
Re: TDP for SQL backup fails
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:[EMAIL PROTECTED] Behalf Of Richard Sims Sent: 14 January 2004 14:35 To: [EMAIL PROTECTED] 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
Re: TDP for SQL backup fails
Yiannakis RC=418 means there was a TSM API error. The DSIERROR.LOG file should have something that explains what the TSM API thought was the problem. Please look there. Also, look in the TSM Server activity log file to look for a message that might tell you what went wrong. RC=402 is the general error that means errors occurred processing the command. Thanks, Del > > 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.
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
TDP for SQL backup fails
Hi, 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. Please help if you can, Thanks Yiannakis Here's what I get from the error logs: 01/12/2004 20:32:14 == Log file pruned using log retention period of 60 day(s) 01/12/2004 20:32:14 == No log entries pruned 01/12/2004 20:32:17 = 01/12/2004 20:32:18 = 01/12/2004 20:32:18 Request : FULL BACKUP 01/12/2004 20:32:18 Database Input List : BOCDSS 01/12/2004 20:32:18 Group Input List : - 01/12/2004 20:32:18 File Input List : - 01/12/2004 20:32:18 Number of Buffers : 5 01/12/2004 20:32:18 Buffer Size : 1024 01/12/2004 20:32:18 Number of SQL Buffers : 0 01/12/2004 20:32:18 SQL Buffer Size : 1024 01/12/2004 20:32:18 Number of Stripes specified : 2 01/12/2004 20:32:18 Estimate : - 01/12/2004 20:32:18 Truncate Log? : - 01/12/2004 20:32:18 Wait for Tape Mounts? : Yes 01/12/2004 20:32:18 TSM Options File : C:\Progra~1\Tivoli\TSM\TDPSql\dsm.opt 01/12/2004 20:32:18 TSM Nodename Override : - 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 01/12/2004 23:48:54 ANS1017E (RC-50) Session rejected: TCP/IP connection failure 01/12/2004 23:48:55 Backup of BOCDSS failed. 01/12/2004 23:48:55 ANS1017E (RC-50) Session rejected: TCP/IP connection failure 01/12/2004 23:48:55 Total SQL backups selected: 1 01/12/2004 23:48:55 Total SQL backups attempted: 1 01/12/2004 23:48:55 Total SQL backups completed: 0 01/12/2004 23:48:55 Total SQL backups excluded: 0 01/12/2004 23:48:55 Total SQL backups inactivated:0 01/12/2004 23:48:55 Throughput rate: 2,808.32 Kb/Sec 01/12/2004 23:48:55 Total bytes transferred: 33,917,686,272 01/12/2004 23:48:55 Elapsed processing time: 11,794.51 Secs 01/12/2004 23:48:55 ACO0151E Errors occurred while processing the request. 01/12/2004 23:48:56 ACO0151E Errors occurred while processing the request. dsierror.log 01/08/2004 23:48:07 cuConfirm: Received rc: -50 trying to receive ConfirmResp verb 01/08/2004 23:48:07 sessSendVerb: Error sending Verb, rc: -50 01/08/2004 23:48:07 sessSendVerb: Error sending Verb, rc: -50 01/12/2004 23:48:53 cuConfirm: Received rc: -50 trying to receive ConfirmResp verb 01/12/2004 23:48:53 sessSendVerb: Error sending Verb, rc: -50 01/12/2004 23:48:53 sessSendVerb: Error sending Verb, rc: -50 dsmerror.log 01/08/2004 23:48:09 ANS1909E The scheduled command failed. 01/08/2004 23:48:09 ANS1512E Scheduled event 'DWDSS_BOCDSS_FULL' failed. Return code = 402. 01/12/2004 23:48:56 ANS1909E The scheduled command failed. 01/12/2004 23:48:56 ANS1512E Scheduled event 'DWDSS_BOCDSS_FULL' failed. Return code = 402.
