Verify failure on Sql Backup

theredmiatatheredmiata Posts: 13
edited September 16, 2008 6:38PM in SQL Backup Previous Versions
All,

Currently running SQL Backup v5.1.0.2781 on a SQL 2005 SP2 64bit / Win2k3 SP2 ProLiant Dl585 G1 4 AMD Opterons w/ 20gb of RAM, database size is about 300gb uncompressed. I've had SQL Backup running for over a month now without issue and during some reindexing maintenance the backups were successful however the verify failed 2 out of 6 times. This is the first that this has happened. First time the following was recorded:

-1st Failure
Thread 0 - 6 error:
Failed to service command. Error code: -2139684860
Process terminated unexpectedly. Error code: -2139684860
Device index out of range: 19
SQL error 3013: VERIFY DATABASE is terminating abnormally
SQL error 3203: Read on "SQLBACKUP _87AA32F8-89DA-4394-9186-C224AC97AE3C01" failed: 995(The I/O operation has been aborted because of either a thread exit or an application request.)

-2nd Failure
Similar to 1st Failure except Device index out of range: 71
Same SQL error codes

Event logs show application errors
Event Type: Error
Event Category: (2)
Event ID: 18210
Date: 11/10/2007
Time: 9:58:00 PM
Computer: WVSAP408
Description:
BackupMedium::ReportIoError: read failure on backup device 'SQLBACKUP_DE230C25-FF44-4497-BD7A-0115C4EE904F03'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

Data:
0000: 22 47 00 00 10 00 00 00 "G......
0008: 10 00 00 00 57 00 56 00 ....W.V.
0010: 53 00 41 00 50 00 34 00 S.A.P.4.
0018: 30 00 38 00 5c 00 4e 00 0.8.\.N.
0020: 41 00 56 00 50 00 52 00 A.V.P.R.
0028: 44 00 00 00 00 00 00 00 D.......

Event Type: Error
Event Source: SQLVDI
Event Category: None
Event ID: 1
Date: 11/10/2007
Time: 9:58:00 PM
Description:
SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=1628. Thread=1948. Server. Instance=NAVPRD. VD=Global\SQLBACKUP_DE230C25-FF44-4497-BD7A-0115C4EE904F_SQLVDIMemoryName_0.


I've checked the server diagnostics and no errors are reported on the hardware.

Any help would be appreciated...

Regards,

Ian

Comments

  • Eddy!Eddy! Posts: 17
    edited November 14, 2007 2:40AM
    I am receiving a similar problem when backing up several databases using the same version of SQL Backup, the largest one of 105Gb uncompressed is failing on the verify. This is a test system and i was getting it on other backup jobs that were being backed up to a UNC path on a NAS. I have moved this job to backup to a RAID 5, again to a UNC path.

    The errors i get reported are:

    SQL error 3013: SQL error 3013: VERIFY DATABASE is terminating abnormally.
    SQL error 3241: SQL error 3241: The media family on device 'SQLBACKUP_DE229A8D-A138-4280-99C9-5B95C8865005' is incorrectly formed. SQL Server cannot process this media family.
    13/11/2007 00:39:39: Validation of all backup files failed.

    And in the application log:

    Event Type: Error
    Event Source: MSSQLSERVER
    Event Category: (2)
    Event ID: 17055
    Date: 13/11/2007
    Time: 00:39:39
    Description:
    18210 :
    BackupIoRequest::WaitForIoCompletion: read failure on backup device 'SQLBACKUP_DE229A8D-A138-4280-99C9-5B95C8865005'. Operating system error 38(error not found).

    Can anyone help either of us why the verify is reporting a failure???
  • What happens if you try running the verification process seperately? You can try this using the following command:
    execute master..sqlbackup '-SQL "RESTORE VERIFYONLY FROM DISK = ''<disk_location>''"';
    

    If this is successful, then the backup should be fine. If it's not, then you should look in the following log directory for the full SQL Backup log text, which should give more information as to what happened during the backup:

    C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\<instance>The logs in this directory will be sorted by date, so should be fairly easy to identify the log in question. If the verification does fail, you can post this log here (but please make sure to remove any email addresses, passwords or other confidential information first - since this is a public forum).

    Hope that helps,
    Jason
  • VerifyOnly does confirm the same error codes. The log file you mention confirms the same findings as well.


    Processed 171008 pages for database 'NavisionPRD', file 'Navision_Data' on file 1.
    Processed 16626200 pages for database 'NavisionPRD', file 'Navision_1_Data' on file 1.
    Processed 17301472 pages for database 'NavisionPRD', file 'Navision_2_Data' on file 1.
    Processed 13 pages for database 'NavisionPRD', file 'Navision_Log' on file 1.
    BACKUP DATABASE successfully processed 34098693 pages in 1179.384 seconds (236.849 MB/sec).
    11/10/2007 9:47:07 PM:
    11/10/2007 9:47:07 PM: Validating files:
    11/10/2007 9:47:07 PM: K:\Backup\Database\NavisionPRD.sqb
    11/10/2007 9:47:07 PM:
    11/10/2007 9:47:07 PM: RESTORE VERIFYONLY FROM DISK = 'K:\Backup\Database\NavisionPRD.sqb'

    11/10/2007 9:58:00 PM: Thread 0 error:
    Failed to service command. Error code: -2139684860
    Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 71
    11/10/2007 9:58:00 PM: Thread 1 error:
    Failed to service command. Error code: -2139684860
    Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 71
    11/10/2007 9:58:00 PM: Thread 2 error:
    Failed to service command. Error code: -2139684860
    Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 71
    11/10/2007 9:58:00 PM: Thread 3 error:
    Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 71
    11/10/2007 9:58:00 PM: Thread 4 error:
    Failed to service command. Error code: -2139684860
    Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 71
    11/10/2007 9:58:00 PM: Thread 5 error:
    Failed to service command. Error code: -2139684860
    Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 71
    11/10/2007 9:58:00 PM: Thread 6 error:
    Failed to service command. Error code: -2139684860
    Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 71

    SQL error 3013: SQL error 3013: VERIFY DATABASE is terminating abnormally.
    SQL error 3203: SQL error 3203: Read on "SQLBACKUP_DE230C25-FF44-4497-BD7A-0115C4EE904F03" failed: 995(The I/O operation has been aborted because of either a thread exit or an application request.)
    11/10/2007 9:58:00 PM: Validation of all backup files failed.
    11/10/2007 9:58:01 PM: Mail sent successfully to:
  • I have run the RESTORE VERIFYONLY myself and luckily all the database backups that were reporting validation errors have reported the backup set is valid.

    This is good but I still have a problem that everyday the scheduled backup job reports verification errors and whoever is doing the morning checks for us shouldn't have to go through the process of doing a RESTORE VERIFYONLY every morning to prove the backup is ok.

    Is there anything else you know i could look at regarding this?

    thanks

    Eddy
  • Hi theredmiata,
    I believe that you have a support request open with our Technical Support team. They are currently waiting for a backup file to pass on to our developers so that they can investigate the problem further. If you can follow-up on their request we should be able to follow up and help identify what the cause is.

    Thanks.
    ===

    Hi Eddy!,
    We are looking into why issues are occurring with the WITH VERIFY step of the backup process, that do no appear in the RESTORE VERIFYONLY step (especially as many of the failures can be of a temporal nature - such as network I/O, disk issues or similar).

    The workaround I would suggest at the moment would be much along the lines of what we've already discussed - running the RESTORE VERIFYONLY step manually if required. If the RESTORE VERIFYONLY step shows a problem, you should contact our support team at [email protected] and they will be able to investigate the matter further.

    You can also drop our support team an email if you want to know when improvements have been made to the verification process in a future patch or release, and they will contact you when this occurs.

    Hope that helps,
    Jason
  • peteypetey Posts: 2,358 New member
    Hi theredmiata and eddy,

    Could you pls provide the backup command that was used to back up the databases? I would like to know exactly which options were used.

    Eddy, could you pls also post details of your server where the verification failed i.e.

    - SQL Backup version
    - SQL Server version, service pack level and bitness (32, 64, Itanium)
    - OS version, service pack level and bitness ((32, 64, Itanium)

    Thanks.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • After a couple of successful verifies after backup I just recieved another verify failure.

    SQL Backup v5.1.0.2781
    SQL Server 2005 64bit 9.0.3054

    SQL backup command - EXECUTE master..sqlbackup N'-SQL "BACKUP DATABASE [DB] TO DISK = ''K:\Backup\Database\DB.sqb'' WITH COMPRESSION = 1, ERASEFILES_ATSTART = 1, INIT, MAILTO = ''[email protected]iz.com;[email protected]'', THREADCOUNT = 7, VERIFY"'

    Backup size - 51,814,924,288 bytes

    I ran a verifyonly first (unsuccessful), full restore to another server (successful), verifyonly (unsuccessful). Error is below. I can try and ftp the backup but at close to 50gb this would take 3 - 5 days to even complete if it even complete. Any help would be appreciated.

    -Verify Only
    Verifying file:
    K:\NavisionPRD.sqb

    Thread 0 error:

    Device index out of range: 29
    Thread 1 error:

    Device index out of range: 29
    Thread 2 error:

    Device index out of range: 29
    Thread 3 error:

    Device index out of range: 29
    Thread 4 error:

    Device index out of range: 29
    Thread 5 error:

    Device index out of range: 29
    Thread 6 error:

    Device index out of range: 29

    SQL error 3013: SQL error 3013: VERIFY DATABASE is terminating abnormally.
    SQL error 3203: SQL error 3203: Read on "SQLBACKUP_9F78AAA9-B70D-48A2-9368-6F1687D2DE62" failed: 995(The I/O operation has been aborted because of either a thread exit or an application request.)

    SQL Backup exit code: 790
    SQL error code: 3203

    exitcode 790
    sqlerrorcode 3203
    filename001 K:\NavisionPRD.sqb

    -Restore to a different db server
    Restoring NavisionPRD (database) from:
    K:\NavisionPRD.sqb

    Processed 18512 pages for database 'NavisionPRD', file 'Navision_Data' on file 1.
    Processed 17323728 pages for database 'NavisionPRD', file 'Navision_1_Data' on file 1.
    Processed 18101312 pages for database 'NavisionPRD', file 'Navision_2_Data' on file 1.
    Processed 396 pages for database 'NavisionPRD', file 'Navision_Log' on file 1.
    RESTORE DATABASE successfully processed 35443948 pages in 2524.857 seconds (114.999 MB/sec).
    SQL Backup process ended.

    exitcode 0
    sqlerrorcode 0
    filename001 K:\NavisionPRD.sqb

    -Verify Only after successful Restore
    Verifying file:
    K:\NavisionPRD.sqb

    Thread 0 error:
    Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 52
    Thread 1 error:
    Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 52
    Thread 2 error:
    Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 52
    Thread 3 error:
    Failed to service command. Error code: -2139684860
    Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 52
    Thread 4 error:
    Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 52
    Thread 5 error:
    Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 52
    Thread 6 error:
    Failed to service command. Error code: -2139684860
    Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 52

    SQL error 3013: SQL error 3013: VERIFY DATABASE is terminating abnormally.
    SQL error 3203: SQL error 3203: Read on "SQLBACKUP_1224556F-D724-4B82-836F-32CC6AAD1640" failed: 995(The I/O operation has been aborted because of either a thread exit or an application request.)

    SQL Backup exit code: 790
    SQL error code: 3203

    exitcode 790
    sqlerrorcode 3203
    filename001 K:\NavisionPRD.sqb
  • peteypetey Posts: 2,358 New member
    Could you pls run a file integrity check on that backup file using our test tool? I've sent you instructions via a private message on where to obtain it. Thanks.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • petey wrote:
    Could you pls run a file integrity check on that backup file using our test tool? I've sent you instructions via a private message on where to obtain it. Thanks.

    Here are the results:

    11/20/2007 8:21:35 PM Not encrypted
    11/20/2007 8:21:35 PM Multiple device file: 7
    11/20/2007 8:21:35 PM Compression level: 1
    11/20/2007 8:21:35 PM File size: 51,814,924,288
    11/20/2007 9:02:52 PM Found terminating marker for device 0, position 51,814,924,128
    11/20/2007 9:02:52 PM Found terminating marker for device 1, position 51,814,924,137
    11/20/2007 9:02:52 PM Found terminating marker for device 2, position 51,814,924,146
    11/20/2007 9:02:52 PM Found terminating marker for device 3, position 51,814,924,155
    11/20/2007 9:02:52 PM Found terminating marker for device 4, position 51,814,924,164
    11/20/2007 9:02:52 PM Found terminating marker for device 5, position 51,814,924,173
    11/20/2007 9:02:52 PM Found terminating marker for device 6, position 51,814,924,182
    11/20/2007 9:02:52 PM File read stopped at position: 51,814,924,182
    11/20/2007 9:02:52 PM Remaining: 106
    11/20/2007 9:02:52 PM Validating remaining bytes...
    11/20/2007 9:02:52 PM File appears to be valid
    11/20/2007 9:02:52 PM File read ended at position: 51,814,924,288
  • peteypetey Posts: 2,358 New member
    Thanks for the update. I'm arranging wth our support staff to work out how best to get a copy of your file for us to analyse further.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Latest update... last night's backup and verify was successful

    SQL Backup log file
    11/20/2007 9:29:14 PM: Backing up DB (full database) on DB instance to:
    11/20/2007 9:29:14 PM: K:\Backup\Database\DB.sqb

    11/20/2007 9:29:14 PM: BACKUP DATABASE [DB] TO DISK = 'K:\Backup\Database\DB.sqb' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', INIT, VERIFY, ERASEFILES_ATSTART = 1, MAILTO = '[email protected];[email protected]', COMPRESSION = 1, THREADCOUNT = 7

    11/20/2007 9:48:39 PM: Database size : 402.730 GB
    11/20/2007 9:48:39 PM: Compressed data size: 48.429 GB
    11/20/2007 9:48:39 PM: Compression rate : 87.97%

    Processed 18520 pages for database 'DB', file 'Navision_Data' on file 1.
    Processed 17377208 pages for database 'DB', file 'Navision_1_Data' on file 1.
    Processed 18124920 pages for database 'DB', file 'Navision_2_Data' on file 1.
    Processed 14948 pages for database 'DB', file 'Navision_Log' on file 1.
    BACKUP DATABASE successfully processed 35535596 pages in 1159.160 seconds (251.136 MB/sec).
    11/20/2007 9:48:39 PM:
    11/20/2007 9:48:39 PM: Validating files:
    11/20/2007 9:48:39 PM: K:\Backup\Database\DB.sqb
    11/20/2007 9:48:39 PM:
    11/20/2007 9:48:39 PM: RESTORE VERIFYONLY FROM DISK = 'K:\Backup\Database\DB.sqb'

    The backup set on file 1 is valid.
    11/20/2007 10:07:04 PM: SQL Backup process ended.

    Backup Size - 52000056832kb
  • Is there any status on this issue?
  • peteypetey Posts: 2,358 New member
    We currently have an internal build that we are testing to see if it resolves the issue.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Peter,

    Apologies for not getting back to you, I have been off sick for a cpl of weeks and just piling through all the logs etc now, in summary our verification is looking healthier than it had been in the past.

    I will monitor this again this week and speak to colleagues and see if they are still seeing an issue, if so I will post the details you require.

    many thanks,

    Eddy
  • Has there been any progress on this issue:

    Last night's backup verified failed:

    SQL Backup log file
    1/9/2008 9:30:32 PM: Backing up NavisionPRD (full database) on NAVPRD instance to:
    1/9/2008 9:30:32 PM: K:\Backup\Database\NavisionPRD.sqb

    1/9/2008 9:30:32 PM: BACKUP DATABASE [NavisionPRD] TO DISK = 'K:\Backup\Database\NavisionPRD.sqb' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', INIT, VERIFY, ERASEFILES_ATSTART = 1, MAILTO = '[email protected];[email protected]', COMPRESSION = 1, THREADCOUNT = 7

    1/9/2008 9:50:18 PM: Database size : 402.730 GB
    1/9/2008 9:50:18 PM: Compressed data size: 51.092 GB
    1/9/2008 9:50:18 PM: Compression rate : 87.31%

    Processed 18768 pages for database 'NavisionPRD', file 'Navision_Data' on file 1.
    Processed 18712584 pages for database 'NavisionPRD', file 'Navision_1_Data' on file 1.
    Processed 18664704 pages for database 'NavisionPRD', file 'Navision_2_Data' on file 1.
    Processed 391 pages for database 'NavisionPRD', file 'Navision_Log' on file 1.
    BACKUP DATABASE successfully processed 37396447 pages in 1183.054 seconds (258.949 MB/sec).
    1/9/2008 9:50:18 PM:
    1/9/2008 9:50:18 PM: Validating files:
    1/9/2008 9:50:18 PM: K:\Backup\Database\NavisionPRD.sqb
    1/9/2008 9:50:18 PM:
    1/9/2008 9:50:18 PM: RESTORE VERIFYONLY FROM DISK = 'K:\Backup\Database\NavisionPRD.sqb'

    1/9/2008 10:02:32 PM: Thread 0 error:
    Failed to service command. Error code: -2139684860 Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 248
    1/9/2008 10:02:32 PM: Thread 1 error:
    Failed to service command. Error code: -2139684860 Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 248
    1/9/2008 10:02:32 PM: Thread 2 error:
    Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 248
    1/9/2008 10:02:32 PM: Thread 3 error:
    Failed to service command. Error code: -2139684860 Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 248
    1/9/2008 10:02:32 PM: Thread 4 error:
    Failed to service command. Error code: -2139684860 Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 248
    1/9/2008 10:02:32 PM: Thread 5 error:
    Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 248
    1/9/2008 10:02:32 PM: Thread 6 error:
    Failed to service command. Error code: -2139684860 Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 248

    SQL error 3013: SQL error 3013: VERIFY DATABASE is terminating abnormally.
    SQL error 3203: SQL error 3203: Read on "SQLBACKUP_8B976A59-3085-4DFC-BA16-4211C975550302" failed: 995(The I/O operation has been aborted because of either a thread exit or an application request.)
    1/9/2008 10:02:33 PM: Validation of all backup files failed.

    Running the SQL Backup Test Utilities shows the following:

    1/10/2008 11:54:35 AM Not encrypted
    1/10/2008 11:54:35 AM Multiple device file: 7
    1/10/2008 11:54:35 AM Compression level: 1
    1/10/2008 11:54:35 AM File size: 54,859,328,512
    1/10/2008 12:50:05 PM Found terminating marker for device 0, position 54,859,328,279
    1/10/2008 12:50:05 PM Found terminating marker for device 1, position 54,859,328,288
    1/10/2008 12:50:05 PM Found terminating marker for device 2, position 54,859,328,297
    1/10/2008 12:50:05 PM Found terminating marker for device 3, position 54,859,328,306
    1/10/2008 12:50:05 PM Found terminating marker for device 4, position 54,859,328,315
    1/10/2008 12:50:05 PM Found terminating marker for device 5, position 54,859,328,324
    1/10/2008 12:50:05 PM Found terminating marker for device 6, position 54,859,328,333
    1/10/2008 12:50:05 PM File read stopped at position: 54,859,328,333
    1/10/2008 12:50:05 PM Remaining: 179
    1/10/2008 12:50:05 PM Validating remaining bytes...
    1/10/2008 12:50:05 PM File appears to be valid
    1/10/2008 12:50:05 PM File read ended at position: 54,859,328,512

    I performed a restore onto another server and was successful. The last time it occured, the Check File Integrity failed and the restore failed.

    Is there any insight as why this error appears intermittently? What does the error mean?

    Ian
  • Second straight night that the verify has failed.. same error:

    SQL Backup log file
    1/10/2008 9:30:31 PM: Backing up NavisionPRD (full database) on NAVPRD instance to:
    1/10/2008 9:30:31 PM: K:\Backup\Database\NavisionPRD.sqb

    1/10/2008 9:30:31 PM: BACKUP DATABASE [NavisionPRD] TO DISK = 'K:\Backup\Database\NavisionPRD.sqb' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', INIT, VERIFY, ERASEFILES_ATSTART = 1, MAILTO = '[email protected];[email protected]', COMPRESSION = 1, THREADCOUNT = 7

    1/10/2008 9:50:19 PM: Database size : 402.730 GB
    1/10/2008 9:50:19 PM: Compressed data size: 50.447 GB
    1/10/2008 9:50:19 PM: Compression rate : 87.47%

    Processed 18792 pages for database 'NavisionPRD', file 'Navision_Data' on file 1.
    Processed 18358576 pages for database 'NavisionPRD', file 'Navision_1_Data' on file 1.
    Processed 18690880 pages for database 'NavisionPRD', file 'Navision_2_Data' on file 1.
    Processed 336 pages for database 'NavisionPRD', file 'Navision_Log' on file 1.
    BACKUP DATABASE successfully processed 37068584 pages in 1185.259 seconds (256.202 MB/sec).
    1/10/2008 9:50:19 PM:
    1/10/2008 9:50:19 PM: Validating files:
    1/10/2008 9:50:19 PM: K:\Backup\Database\NavisionPRD.sqb
    1/10/2008 9:50:19 PM:
    1/10/2008 9:50:19 PM: RESTORE VERIFYONLY FROM DISK = 'K:\Backup\Database\NavisionPRD.sqb'

    1/10/2008 10:04:38 PM: Thread 0 error:
    Failed to service command. Error code: -2139684860
    Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 43
    1/10/2008 10:04:38 PM: Thread 1 error:
    Failed to service command. Error code: -2139684860
    Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 43
    1/10/2008 10:04:38 PM: Thread 2 error:
    Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 43
    1/10/2008 10:04:38 PM: Thread 3 error:
    Failed to service command. Error code: -2139684860
    Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 43
    1/10/2008 10:04:38 PM: Thread 4 error:
    Failed to service command. Error code: -2139684860
    Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 43
    1/10/2008 10:04:38 PM: Thread 5 error:
    Failed to service command. Error code: -2139684860
    Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 43
    1/10/2008 10:04:38 PM: Thread 6 error:
    Failed to service command. Error code: -2139684860
    Process terminated unexpectedly. Error code: -2139684860

    Device index out of range: 43

    SQL error 3013: SQL error 3013: VERIFY DATABASE is terminating abnormally.
    SQL error 3203: SQL error 3203: Read on "SQLBACKUP_5DFB2335-62BE-469E-8F4E-818A195F322601" failed: 995(The I/O operation has been aborted because of either a thread exit or an application request.)
    1/10/2008 10:04:38 PM: Validation of all backup files failed.

    Help please...
  • Ran the query: execute master..sqbdata 'SELECT * from backuphistory
    WHERE dbname = ''NavisionPRD'' AND backup_start > ''2008-01-09''
    AND backup_start < ''2008-01-11'' ';

    With the results:
    105 {8E4C5040-30EB-4819-B4E8-82A03C16F101} 2008-01-09 21:30:32.567 2008-01-09 21:50:18.713 D NavisionPRD 0 87.31366 1 1185 432428351488 54859328512 258.949 7 1 WATKINSMFG\GSA_SQL2005 -1 0 0
    106 {43E72595-C27D-4FBA-99C7-F9A4DF7B1B12} 2008-01-10 21:30:31.030 2008-01-10 21:50:19.397 D NavisionPRD 0 87.47369 1 1187 432428351488 54167337472 256.202 7 1 WATKINSMFG\GSA_SQL2005 -1 0 0
  • Restore of 'suspect' backup was successful. File Integrity check was successful, no errors. Backup size-50.4gb - 54,167,337,472 bytes.
  • I am having the same problem. What was the resolution??

    Backup restores on our offsite server, but not on the local one.

    25 other database work fine on both servers. This database had been backing up on both for about 3 years. Suddenly stuck in loading and giving the IoError. It is one of the larger databases (but not the largest).
Sign In or Register to comment.