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

backup jobs just start failing

joesjoes Posts: 11
edited September 10, 2007 9:09AM in SQL Backup Previous Versions
I have serveral jobs that do this same thing.. they work for awhile then all the sudden they stop working. The error code is very generic. i have attached the error below.

WIN2k latest service pack and patches..

sql backup version SQL Backup 4.5.0.704 - Professional edition


Executed as user: SCOTTRADECORP\sqlcristl2. SQL Backup job failed with exitcode: 790 SQL error code: 3202 [SQLSTATE 42000] (Error 50000). The step failed.


Has anyone else had this issue?

Need help

Joe
joe s

Comments

  • Options
    peteypetey Posts: 2,358 New member
    Could you pls post the contents of the SQL Backup log file for the failed backup? The default folder for the log file is <system drive>:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\<instance name>

    Thanks.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Options
    here you go

    thanks




    SQL Backup log file
    11/17/2006 1:02:00 PM: Backing up Quote123 (transaction log) to:
    \\SQLBAKSTL\PRODBACK\SQLCRIST\LOG_(local)_Quote12_20061117_130200.sqb

    11/17/2006 1:02:00 PM: BACKUP LOG [Quote123] TO DISK = '\\SQLBAKST\PRODBACK\SQLCRIST\LOG_(local)_Quote12_20061117_130200.sqb' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', ERASEFILES_ATSTART = 23h, COMPRESSION = 2, THREADS = 1

    11/17/2006 1:02:02 PM: Deleting old backup file: \\SQLBAKSTL\PRODBACK\SQLCRISTL\LOG_(local)_Quote12_20061116_130200.sqb
    11/17/2006 1:02:05 PM: Thread 0 error:
    Error 620: Error writing to backup file(s).
    Process terminated unexpectedly. Error code: -2139684860
    Thread 0 warning:
    Warning 210: Error writing to backup file: \\SQLBAKSTL\PRODBACK\SQLCRIST\LOG_(local)_Quote12_20061117_130200.sqb
    Warning: System error code: (Insufficient system resources exist to complete the requested service)

    11/17/2006 1:02:05 PM: Server: Msg 3013
    BACKUP LOG is terminating abnormally.
    11/17/2006 1:02:05 PM: Server: Msg 3202
    Write on 'SQLBACKUP_2F97A62D-D62B-44B5-8152-78143C495100' failed, status = 112. See the SQL Server error log for more details.
    joe s
  • Options
    peteypetey Posts: 2,358 New member
    The error indicates that the SQL Backup failed to write to the backup file.

    I would like to know when the process failed. Does the file (
    \\SQLBAKSTL\PRODBACK\SQLCRIST\LOG_(local)_Quote12_20061117_130200.sqb) exist, and if so, what is its size? Thanks.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Options
    the file doesn't get created..
    joe s
  • Options
    peteypetey Posts: 2,358 New member
    Does the failure consistently happen at the same time? Would it be possible to attempt a manual backup to the same network share when the error occurs? If a manual backup also fails, try backing up with the MAXDATABLOCK option, to reduce the size of each block that's written to the network share e.g.

    master..sqlbackup '-sql "BACKUP LOG Quote123 TO DISK = [\\SQLBAKSTL\PRODBACK\SQLCRIST\<AUTO>] WITH MAXDATABLOCK = 524288 " '
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Options
    that seemed to fix the issue, my question is why do I have to put this on some jobs and not on other that are on the same server?

    thanks for you help

    joes
    joe s
  • Options
    I had a backup failure with the same error codes the other day and looking at the log it said this:

    9/8/2007 12:37:26 AM: Backing up MYDATABASE (full database) on PROD instance to:
    E:\Backups\MSSQL\MYDATABASE\FULL_PROD_MYDATABASE_20070908_003726.sqb

    9/8/2007 12:37:26 AM: BACKUP DATABASE [MYDATABASE] TO DISK = 'E:\Backups\MSSQL\MYDATABASE\FULL_PR
    OD_MYDATABASE_20070908_003726.sqb' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', PASSWORD = 'XXXXXX
    XXXX', KEYSIZE = 256, ERASEFILES_ATSTART = 4, COMPRESSION = 3, THREADS = 1

    9/8/2007 12:37:27 AM: Deleting old backup file: E:\Backups\MSSQL\MYDATABASE\FULL_PROD_MYDATABASE_2
    0070903_002916.sqb
    9/8/2007 1:36:23 AM: Thread 0 error:
    Error 620: Error writing to backup file(s).
    Process terminated unexpectedly. Error code: -2139684860
    Thread 0 warning:
    Warning 210: Error writing to backup file: E:\Backups\MSSQL\MYDATABASE\FULL_PROD_MYDATABASE_20070
    908_003726.sqb
    Warning: System error code: (Insufficient system resources exist to complete the requested service)

    9/8/2007 1:36:23 AM: Server: Msg 3013
    BACKUP DATABASE is terminating abnormally.
    9/8/2007 1:36:23 AM: Server: Msg 3271
    A nonrecoverable I/O error occurred on file "SQLBACKUP_1E4CD5EC-5A80-4ECC-961E-870A26F5860D:" 995(The I/O operation has been aborted because of either a thread exit or an application request.).
    9/8/2007 1:36:23 AM: Server: Msg 3202
    Write on "SQLBACKUP_1E4CD5EC-5A80-4ECC-961E-870A26F5860D" failed: 112(There is not enough space on the disk.)

    The error claims that I had insufficient disk space. But checking the drive, I had over 199gb of disk space free. The backup worked (at least according to the UI and I see a file there - it's 10gb (compressed/encrypted) and the other backups after it continued without a problem.

    I didn't look in the directory to see if it had actually deleted the old backup that supposedly failed above that day - so I don't know if it got deleted then or on the next backup cycle.

    Anyway - thought you would like to know that this happened. Using version 5.1.0.2781.
Sign In or Register to comment.