Restore Error with SQL Backup 5.3
phowlett
Posts: 5
I have received the following error when attempting to restore a full backup using SQL backup 5.3:
MSSQL2K5-MIR01: Restore - Failed
================================
Restoring full backup - Failed
This operation failed with errors.
Restoring ispi_live (database) from:
E:\MSSQL\Backup\FULL_(local)_live_20081106_141420.sqb
Thread 0 error:
Process terminated unexpectedly. Error code: -2139684853
Thread 1 error:
Failed to service command. Error code: -2139684860
Process terminated unexpectedly. Error code: -2139684860
Thread 2 error:
Failed to service command. Error code: -2139684860
Process terminated unexpectedly. Error code: -2139684860
SQL error 3013: SQL error 3013: RESTORE DATABASE is terminating abnormally.
SQL error 3203: SQL error 3203: Read on "SQLBACKUP_43FF1451-84E8-4E4B-BCE7-2674E9CB69E002" failed: 995(The I/O operation has been aborted because of either a thread exit or an application request.)
SQL error 3271: SQL error 3271: A nonrecoverable I/O error occurred on file "SQLBACKUP_43FF1451-84E8-4E4B-BCE7-2674E9CB69E001:" 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: 3271
Updating SQL Server information - Pending
Operation pending.
I was able to repeat this same problem with 3 different full backups of the same database instance. Those 3 failed restores were all backed up using multiple threads (3) and full compression. When I took a backup without using the multiple threads option (and lower compression) the restore operation succeeded.
Are there any known issues with use of multiple threads (a new feature in 5.3?) during a backup?
Thanks,
Paul
MSSQL2K5-MIR01: Restore - Failed
================================
Restoring full backup - Failed
This operation failed with errors.
Restoring ispi_live (database) from:
E:\MSSQL\Backup\FULL_(local)_live_20081106_141420.sqb
Thread 0 error:
Process terminated unexpectedly. Error code: -2139684853
Thread 1 error:
Failed to service command. Error code: -2139684860
Process terminated unexpectedly. Error code: -2139684860
Thread 2 error:
Failed to service command. Error code: -2139684860
Process terminated unexpectedly. Error code: -2139684860
SQL error 3013: SQL error 3013: RESTORE DATABASE is terminating abnormally.
SQL error 3203: SQL error 3203: Read on "SQLBACKUP_43FF1451-84E8-4E4B-BCE7-2674E9CB69E002" failed: 995(The I/O operation has been aborted because of either a thread exit or an application request.)
SQL error 3271: SQL error 3271: A nonrecoverable I/O error occurred on file "SQLBACKUP_43FF1451-84E8-4E4B-BCE7-2674E9CB69E001:" 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: 3271
Updating SQL Server information - Pending
Operation pending.
I was able to repeat this same problem with 3 different full backups of the same database instance. Those 3 failed restores were all backed up using multiple threads (3) and full compression. When I took a backup without using the multiple threads option (and lower compression) the restore operation succeeded.
Are there any known issues with use of multiple threads (a new feature in 5.3?) during a backup?
Thanks,
Paul
Comments
Also, if you were to convert the SQL Backup file to regular SQL Server backup files, using the CONVERT command or the sqb2mtf utility, are you able to restore the database using the converted files?
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8
Logs from successful restore (after backup using single thread)
Sorry about the delay in getting these logs to you. Hope they help.
Paul