Error Code: -2139684860 on SQL Backup

  • I have a weekly full backup job that works perfectly for most databases but fails on some of them.

    When it fails the messages listed are:

    Thread 0 error:

    Process terminated unexpectedly. Error Code: -2139684860

    Thread 1 error:

    Process terminated unexpectedly. Error Code: -2139684860

    Thread 2 error:

    Process terminated unexpectedly. Error Code: -2139684860

    SQL error 3013: Backup Database is terminated Abnormally

    SQLError 3271: A nonrecoverable I/O error occurred on file.

    This is using Red Gate SQL Backup 5.3.0.178 with SQL Server 2005 SP2 on Windows Server 2003. The compression level is set to 1, encryption is turned on, and it is set to break up the backups in 3 files. At the time this runs there is virtually no other demand on the server.

    All the databases that are having the failure are relatively large (150GB up to 500GB), but I have very similar settings with similarly sized databases on other servers with no problem.

    I tried looking this up and the main suggestion I found was upgrading to 5.3 which I already have. Does anyone have any other ideas?

    (Note: Cross posted on the Red Gate Forums.)

    ---
    Timothy A Wiseman
    SQL Blog: http://timothyawiseman.wordpress.com/

  • I would perform a checkdb on that db, just to be sure that is OK.

    If it is ok, the cause will be your backup drive

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • an OLD post for version 3.5 of Redgate implies that this error could occur if you are running out of disk space, or backing up over a network share...could that be it? an intermittant network issue doinked the backup?

    Posted: Thu Nov 17, 2005 8:17 pm Post subject: Error code: -2139684860

    --------------------------------------------------------------------------------

    I've been fairly happy with red gate, until about 12:15am this morning.

    Today i've suddenly received the following error:

    Error code: -2139684860

    My automated backups are run using a stored proc and have worked flawlessly for over a month.

    The same procedure is working smoothly on 3 identical clusters.

    The strangest thing is that my full backups were failing, but my transaction log backups are still working.

    ** a 1K file is written to local disk, but nothing else.

    ** tried this with and without the -E flag...both do not work.

    here is an example of one of the database backups which is not happening:

    Code:

    master..sqlbackup'-SQL "BACKUP DATABASE [server22]

    TO DISK = ''D:\server22\server22_db_FULLBACKUP_200511171508.sqb''

    WITH NAME = ''Database (server22) Full'',

    COPYTO =''\\sql4kbackup\D$\server22\'',

    ERASEFILES = 7, COMPRESSION = 1"'

    SQLBACKUP ERROR:

    SQL Backup 3.2.0.5, (c) Red Gate Software Ltd 2004 - 2005

    Serial number: 010-005-025534-D183

    Backing up server12 (full database) to

    D:\server12\server12_db_FULLBACKUP_200511171424.sqb ...

    Thread 0 error:

    Process terminated unexpectedly. Error code: -2139684860

    Msg 3013, Level 16, State 1, Server SQLCLUSTER, Line 1

    BACKUP DATABASE is terminating abnormally.

    last few lines in SQLBACKUPERRORLOG:

    ----------------------------------------------

    2005/11/17 14:24:23 pid(3012) tid(3928)

    Error on Global\SQLBACKUP_{C97583B4-DAF5-4FB8-AB86-87F2377D5981}

    Error at ServerBufferAreaManager::Allocate: Map buffers Status Code: 8, x8

    Explanation: Not enough storage is available to process this command.

    Lowell


    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • Thanks everyone. It looks like it is insufficient disk space. There is enough space to store the final compressed files, but it looks like there may not be enough working space for it right now.

    ---
    Timothy A Wiseman
    SQL Blog: http://timothyawiseman.wordpress.com/

Viewing 4 posts - 1 through 3 (of 3 total)

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