Backup-failing with I/O error

  • Hello,

    We are use to take backup with Sql Lite speed.I am getting this error while trying for backup database.

    I have checked the space, its ok.

    Does anybody faced this kind of error ever??

    Date  10/13/2005 7:31:34 PM

    Log  SQL Server (Current - 10/13/2005 10:33:00 PM)

    Source  spid92

    Message

    BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device 'VDI_8E00F75A-F768-4959-ABBC-BB9F2C3F7163_1'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

    Regards

    Binu John

  • This was removed by the editor as SPAM

  • I don't think there is anything to do with the space, it says "of either a thread exit or an application request" - something interrupted your backup...Can it be another job ran or application something...update or so - and there were something like "kill other processes" and your backup got killed?

    Check activities around your backup.

  • I see you wrote this two years ago. I am seeing this same problem today, using LiteSpeed also. Did you ever resolve this? Thanks.

  • I AM GUSESSING this happens when an other job either an full backup starts before completing of the previous log backup.....because even i got th same error...

    Error: 18210, Severity: 16, State: 1.

    BackupMedium::ReportIoError: write failure on backup device 'VDI_209FE1C2-2F07-46D7-B966-BB2E687AAB24_0'. Operating system error 1223(The operation was canceled by the user.).

    Error: 3041, Severity: 16, State: 1.

    BACKUP failed to complete the command BACKUP DATABASE Aris702P. Check the backup application log for detailed messages.

    Error: 18210, Severity: 16, State: 1.

    BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device 'VDI_209FE1C2-2F07-46D7-B966-BB2E687AAB24_0'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

    The alert for 'unsent log' has been raised. The current value of '97985' surpasses the threshold '20000'.

    Error: 18456, Severity: 14, State: 11.

  • It seems that Sql Server is unable to access the database files at startup....could you please once again check the permissions and provide modify privilege to the folder containing database files to the startup account.....also ensure that antivirus/anti-spyware is not accessing these files. If you are using third party tool to perform backup, then check whether the relevant drivers or fixes are updated.

  • The solution of this is posted here...

    http://www.tek-tips.com/viewthread.cfm?qid=308642">

    http://www.tek-tips.com/viewthread.cfm?qid=308642

    its some connectivity (networking) issue between client and the server

    Atif Sheikh

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
    Sometimes, winning is not an issue but trying.
    You can check my BLOG
    [font="Arial Black"]here[/font][/url][/right]

  • Please note that the post you are answering is almost a year old.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Nice to see comments after long three years..:)

  • I think I accessed this post by SSC homepage....

    I really didnt see the post started in 2005...

    Atif Sheikh

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
    Sometimes, winning is not an issue but trying.
    You can check my BLOG
    [font="Arial Black"]here[/font][/url][/right]

  • Hope this helps....

    http://support.microsoft.com/kb/934396

    but i dont understand wat "Race Condition" is???

  • I have one similar issue now:

    2008-11-28 21:44:53.68 spid120 BackupMedium::ReportIoError: write failure on backup device 'model_00__5ee91f46_f190_4be7_98d1_40a71edea809_'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application

    request.).

    2008-11-28 21:44:53.68 backup BACKUP failed to complete the command BACKUP DATABASE [model] TO virtual_device = 'model_00__5ee91f46_f190_4be7_98d1_40a71edea809_'

    2008-11-28 21:44:53.68 spid120 Internal I/O request 0x2879FB90: Op: Write, pBuffer: 0x18E80200, Size: 512, Position: 0, UMS: Internal: 0x2879F820, InternalHigh: 0x0, Offset: 0x0, OffsetHigh: 0x0, m_buf: 0x00995C78, m_len: 2, m_actualBytes: 0, m_errcode:

    995, BackupFile: model_00__5ee91f46_f190_4be7_98d1_40a71edea809_

    2008-11-28 21:44:53.68 spid120 BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device 'model_00__5ee91f46_f190_4be7_98d1_40a71edea809_'. Operating system error 995(The I/O operation has been aborted because of either a thread exit

    or an application request.).

  • I did encounter this issue not a long time ago.

    The backup is done via Veritas software (netbackup I believe) 10d which is a old software (they are up to version 12.5 now). Are you happening to use that also?

    I do believe it is related to the software rather than SQL (we are not using the fiber mode on that instance). It does behave weirdly (Veritas) (it (Windows & SQL) does log warnings and errors now and then) Unfortunately I can't do anything about it. I'm going to monitor it even when applying SP3.

    One other thing I've heard about it was a reverse lookup issue. Not sure how much this information is reliable but could be something to check out.

  • I know this post is old but I would like to add what was the cause of

    Error: 3041, Severity: 16, State: 1.

    BACKUP failed to complete the command BACKUP DATABASE XYZ. Check the backup application log for detailed messages.

    on our database for others if needed someday.

    It is simply because the database in question was offline and the backup was done remotely using a third party software. The software was not configured to avoid the offline database thus resulting in an error message of this kind in the SQL error logs.

  • been getting this

    we have a new tape library with netbackup 6.5.3 and the latest client installed. we also run a job to clear transaction logs manually. rescheduled the job so that it doesn't run during backups. will see what happens.

    i did test backups during the day of the same databases and it worked. seems like a random occurence

Viewing 15 posts - 1 through 15 (of 20 total)

You must be logged in to reply to this topic. Login to reply