What are the challenges you face when working across database platforms? Take the survey
Options

operating System error runing backup

rand201rand201 Posts: 9
edited November 1, 2008 10:53PM in SQL Backup Previous Versions
BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device 'SQLBACKUP_5DDAAAAD-74EC-43C3-9083-4271A642C299'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

Any one see this before?
Thanks

Art

Comments

  • Options
    Hi Art,

    Could you please paste the contents of the SQL Backup log file for this failed job?

    By default they are located in :

    %:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\<instance name>

    Thanks
    Matthew Flatt
    Redgate Foundry
  • Options
    SQL Backup log file 5.3.0.178

    -SQL "BACKUP DATABASE ProMaxOnLine TO DISK = 'R:\Backups\ProMaxOnLine.sqb

    ERRORS AND WARNINGS


    9/8/2008 2:21:29 PM: Backing up ProMaxOnLine (full database) to:
    9/8/2008 2:21:29 PM: R:\Backups\ProMaxOnLine.sqb

    9/8/2008 2:21:30 PM: BACKUP DATABASE [promaxonline] TO VIRTUAL_DEVICE = 'SQLBACKUP_5DDAAAAD-74EC-43C3-9083-4271A642C299' WITH BUFFERCOUNT = 6, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576, NAME = N'Database (ProMaxOnLine), 9/8/2008 2:21:29 PM', DESCRIPTION = N'Backup on 9/8/2008 2:21:29 PM Server: SQLSERVER3 Database: ProMaxOnLine'

    9/8/2008 2:23:47 PM: Thread 0 error:
    Process terminated unexpectedly. Error code: -2139684860
    Process terminated unexpectedly. Error code: -2139684860
    9/8/2008 2:23:47 PM:
    SQL error 3013: SQL error 3013: BACKUP DATABASE is terminating abnormally.
    SQL error 3204: SQL error 3204:
    Thanks

    Art
  • Options
    Hi,

    That doesn't seem to be the whole log file?

    If you don't wish you paste it here you can private message me or send it to support@red-gate.com with this forum post referenced.

    Thanks
    Matthew Flatt
    Redgate Foundry
  • Options
    This is the whole log.
    SQL Backup log file 5.3.0.178

    -SQL "BACKUP DATABASE ProMaxOnLine TO DISK = 'R:\Backups\ProMaxOnLine.sqb

    ERRORS AND WARNINGS


    9/8/2008 2:21:29 PM: Backing up ProMaxOnLine (full database) to:
    9/8/2008 2:21:29 PM: R:\Backups\ProMaxOnLine.sqb

    9/8/2008 2:21:30 PM: BACKUP DATABASE [promaxonline] TO VIRTUAL_DEVICE = 'SQLBACKUP_5DDAAAAD-74EC-43C3-9083-4271A642C299' WITH BUFFERCOUNT = 6, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576, NAME = N'Database (ProMaxOnLine), 9/8/2008 2:21:29 PM', DESCRIPTION = N'Backup on 9/8/2008 2:21:29 PM Server: SQLSERVER3 Database: ProMaxOnLine'

    9/8/2008 2:23:47 PM: Thread 0 error:
    Process terminated unexpectedly. Error code: -2139684860
    Process terminated unexpectedly. Error code: -2139684860
    9/8/2008 2:23:47 PM:
    SQL error 3013: SQL error 3013: BACKUP DATABASE is terminating abnormally.
    SQL error 3204: SQL error 3204:
    Thanks

    Art
  • Options
    Was there a solution?

    I am seeing the exact same errors. I'm running SQL Backup 5.2 on a Windows 2000 / SQL 2000 box if that matters.

    I'm backing up directly to a network drive - uncompressed (part of the requirements). But I've tried it compressed as well, multi-thread, lowest possible Max block size. And all combinations of these.

    Of note: it doesn't fail on ALL the backups - but the largest database that DOES work is 3.5GB - and I've got a SEVERAL databases larger than that that need to get backed up properly.

    I wasn't receiving this error when this job was going to the old network drive.

    However, I've got 10 other SQL servers all pointing at the new network drive and the are NOT experiencing this error.

    The new network drive location has a very low load - and I'm running all the backups in their own window so they aren't stepping on each other.

    Thanks for any help in advance!
Sign In or Register to comment.