Corrupted differential backup?

meastlandmeastland Posts: 47
edited April 20, 2011 10:04AM in SQL Backup Previous Versions
I am occasionally having trouble restoring from a differential backup created by SQL Backup 6.4.

Here are the symptoms:

I am using the LATEST_ALL functionality to restore a given database. The FULL backup set restores fine. When process tries to restore from the DIFFERENTIAL backup set, it goes immediately to something like 98% complete and hangs indefinitely until the process times out.

When I execute the verification commands against the same differential backup file (RESTORE...VERIFYONLY, RESTORE...FILELISTONLY, RESTORE...SQBHEADERONLY), everything comes back clean. Is there any other way to check for corruption of the differential backup? If not, what else am I missing?

Thanks in advance for any response.

Regards,

-Mike Eastland
· Share on Twitter

Comments

  • meastlandmeastland Posts: 47
    Some additional information...

    I attempted to convert the DIFFERENTIAL backup set into the native backup format, and I'm seeing the same behavior when trying to restore from the converted backup set.
    · Share on Twitter
  • meastlandmeastland Posts: 47
    I spoke too soon on my previous reply. After converting the differential backup into the native format, the restore DOES complete successfully. However, restoring from the same backup set while it is in the SQL Backup compressed state continues to hang indefinitely.

    Here is the error message that results after the process is finally killed:

    4/18/2011 11:54:25 AM: Thread 0 error:
    Process terminated unexpectedly. Error code: -2139684861 (The api was waiting and the timeout interval had elapsed.)
    4/18/2011 11:54:25 AM:
    4/18/2011 11:54:25 AM: Thread 1 error:
    Process terminated unexpectedly. Error code: -2139684861 (The api was waiting and the timeout interval had elapsed.)
    4/18/2011 11:54:25 AM:
    4/18/2011 11:54:25 AM: Thread 2 error:
    Process terminated unexpectedly. Error code: -2139684861 (The api was waiting and the timeout interval had elapsed.)
    4/18/2011 11:54:25 AM:
    4/18/2011 11:54:25 AM: Thread 3 error:
    Process terminated unexpectedly. Error code: -2139684861 (The api was waiting and the timeout interval had elapsed.)
    4/18/2011 11:54:25 AM:
    4/18/2011 1:08:46 PM: SQL error 3013: SQL error 3013: RESTORE DATABASE is terminating abnormally.
    4/18/2011 1:08:46 PM: SQL error 3203: SQL error 3203: Read on "SQLBACKUP_8B2CA8C7-096B-4367-B2E5-62828678140001" failed: 995(The I/O operation has been aborted because of either a thread exit or an application request.)


    Looking forward to some input. Thanks.
    · Share on Twitter
  • peteypetey Posts: 2,358 New member
    If you can reproduce the error and get the restore to hang, could you please run the following
    EXEC master..sqbutility 9997
    when the restore hangs? This generates a stack trace of all active threads in a file named SQBCoreService_<instance name>_bugreport.txt, and is located in 'C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\' on Windows 2003 and older, and 'C:\ProgramData\Red Gate\SQL Backup\Log\' on Windows Vista and newer. Could you please send me that file?

    Thanks.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
    · Share on Twitter
  • meastlandmeastland Posts: 47
    I wasn't able to reproduce the error. When I attempted to restore from the same backupset this morning, it completed successfully. About the only thing I know that changed is that I rebooted the server on which the test was being performed.

    I'm not really sure where we go from here, other than I can try to run the trace command if I run into the issue again in the future.

    Thanks anyway for the reply.
    · Share on Twitter
Sign In or Register to comment.