More Information on TDP SQL V2 as requested.
TSM Server Activity Log:
ANE4993E (Session: 377, Node: PACVMSDBQ) TDP MSSQLV2 NT
ACO3002 TDP for Microsoft SQL Server: full backup of
database MSDB_PROD from server PACVMSDBQ failed, rc = 418.
----------------------------------------------------------
No errors in the DSIERROR.LOG
----------------------------------------------------------
DSMERROR.LOG:
03/21/2003 00:10:33 sessSendVerb: Error sending Verb, rc: -50
03/21/2003 00:10:33 sessSendVerb: Error sending Verb, rc: -50
03/21/2003 00:10:53 ANS1909E The scheduled command failed.
03/21/2003 00:10:53 ANS1512E Scheduled event 'DAILY_MSDB_DB' failed. Return
code = 402.
-----------------------------------------------------------
DP for SQL Log file:
03/21/2003 00:10:34 ACO0302E A failure occured on stripe number (0), rc = 418
03/21/2003 00:10:34 ANS1017E (RC-50) Session rejected: TCP/IP connection
failure
03/21/2003 00:10:34 Backup of MSDB_PROD failed.
03/21/2003 00:10:34 ANS1017E (RC-50) Session rejected: TCP/IP connection
failure
------------------------------------------------------------
I hope this helps.
Thanks for your time,
Prasanna
--
On Fri, 21 Mar 2003 11:55:00
Del Hoobler wrote:
>Prasanna,
>
>"write failure on backup device" during a backup indicates
>that when SQL tried to write backup data to the VDI device
>that DP for SQL created, it failed. This could be because
>the TSM Server closed down a session for some reason,
>(size estimate was exceeded, device error, etc.) or because the
>the DP for SQL process consuming the data had some problem.
>More information is needed.
>
>What messages appear in the DP for SQL log file?
>What messages appear on the TSM Server activity log?
>What messages appear in the DSIERROR.LOG files?
>How many stripes are you using?
>
>Thanks,
>
>Del
>
>----------------------------------------------------
>
>Del Hoobler
>IBM Corporation
>hoobler AT us.ibm DOT com
>
>- Remember that the best job security is
>doing a job well and doing it cheerfully.
>
>=============================================================
>> I've been backing up quite a few databases from a SQL Cluster using TDP
>for SQL V2 for some time.
>> for the past few days, I've started getting an error and the backup
>started failing for one particular
>> database on the SQL cluster. I tried to find out more looking at the
>event logs but could not find
>> anything on Microsoft for the SQL event ID's. Any Help is greatly
>appreciated.
>>
>> Event ID: 17055
>> Category: Kernel
>> Description:
>> BackupMedium::ReportIoError: write failure on backup device
>'TDPSQL-00000226-0000'. Operating system
>> error 1003(Cannot complete this function.)
>>
>> Event ID: 17055
>> Category: Kernel
>> Description:
>> BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup
>device 'TDPSQL-00000226-0000'.
>> Operating system error 995(The I/O operation has been aborted because of
>either a thread exit or an
>> application request.)
>
_____________________________________________________________
Get 25MB, POP3, Spam Filtering with LYCOS MAIL PLUS for $19.95/year.
http://login.mail.lycos.com/brandPage.shtml?pageId=plus&ref=lmtplus
|
