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

Restore fails first time, then works.

jpassarellijpassarelli Posts: 7
edited November 22, 2006 10:36AM in SQL Backup Previous Versions
We have a backup that runs nightly from one server to another, DBSrvr5 (production) to DBSrvr4 (test). When the backup is complete, another process restores the database on DBSrvr4. It fails every time on the first run, but then will run successfully with the exact same script when I rerun the process. The first failure is always 30-60 minutes after the start of the restore. Any ideas?

SQL Backup log file
11/20/2006 10:41:20 PM: Restoring BCBS3 (database) from:
\\DBSrvr4\Backup\DBSRVR5.BCBS3_FullBackup_20061120.193018_01.sqb
\\DBSrvr4\Backup\DBSRVR5.BCBS3_FullBackup_20061120.193018_02.sqb
\\DBSrvr4\Backup\DBSRVR5.BCBS3_FullBackup_20061120.193018_03.sqb
\\DBSrvr4\Backup\DBSRVR5.BCBS3_FullBackup_20061120.193018_04.sqb

11/20/2006 10:41:20 PM: RESTORE DATABASE [BCBS3] FROM DISK = '\\DBSrvr4\Backup\DBSRVR5.BCBS3_FullBackup_20061120.193018_01.sqb', DISK = '\\DBSrvr4\Backup\DBSRVR5.BCBS3_FullBackup_20061120.193018_02.sqb', DISK = '\\DBSrvr4\Backup\DBSRVR5.BCBS3_FullBackup_20061120.193018_03.sqb', DISK = '\\DBSrvr4\Backup\DBSRVR5.BCBS3_FullBackup_20061120.193018_04.sqb' WITH RECOVERY, MOVE 'BCBS_idx' TO 'T:\SQLData\BCBS3_1.mdf', MOVE 'BCBS_ax2' TO 'T:\SQLData\BCBS_ax2_Data.NDF', REPLACE

11/20/2006 11:50:32 PM: Thread 0 error:
File read error for 229425 bytes (balance 228967 bytes). Backup file is incomplete or corrupted.
11/20/2006 11:50:32 PM: Thread 1 error:
Failed to service command. Error code: -2139684860
Process terminated unexpectedly. Error code: -2139684860
11/20/2006 11:50:32 PM: Thread 2 error:
File read error for 305777 bytes (balance 70113 bytes). Backup file is incomplete or corrupted.
Process terminated unexpectedly. Error code: -2139684860
11/20/2006 11:50:32 PM: Thread 3 error:
Failed to service command. Error code: -2139684860
Process terminated unexpectedly. Error code: -2139684860

11/20/2006 11:50:32 PM: Server: Msg 3013
RESTORE DATABASE is terminating abnormally.
11/20/2006 11:50:32 PM: Server: Msg 3203
Read on 'SQLBACKUP_68EEA17E-3B73-4175-A45A-E173C28457DF02' failed, status = 995. See the SQL Server error log for more details.


SQL Error Log entries:

2006-11-20 23:50:32.43 spid57 BackupMedium::ReportIoError: read failure on backup device 'SQLBACKUP_68EEA17E-3B73-4175-A45A-E173C28457DF02'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

2006-11-20 23:50:32.44 spid57 Internal I/O request 0x7C4AC370: Op: Read, pBuffer: 0x11E30000, Size: 1048576, Position: 34167521280, UMS: Internal: 0x0, InternalHigh: 0x0, Offset: 0x0, OffsetHigh: 0x0, m_buf: 0x11E30000, m_len: 0, m_actualBytes: 1048576, m_errcode: 995, BackupFile: SQLBACKUP_68EEA17E-3B73-4175-A45A-E173C28457DF02

2006-11-20 23:50:32.59 spid57 BackupMedium::ReportIoError: read failure on backup device 'SQLBACKUP_68EEA17E-3B73-4175-A45A-E173C28457DF'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

2006-11-20 23:50:32.60 spid57 Internal I/O request 0x80347E70: Op: Read, pBuffer: 0x10830000, Size: 1048576, Position: 23740350464, UMS: Internal: 0x1, InternalHigh: 0x34218F, Offset: 0x7CA10001, OffsetHigh: 0x342237, m_buf: 0x10830000, m_len: 655361, m_actualBytes: 1048576, m_errcode: 995, BackupFile: SQLBACKUP_68EEA17E-3B73-4175-A45A-E173C28457DF

2006-11-20 23:50:32.63 spid57 BackupMedium::ReportIoError: read failure on backup device 'SQLBACKUP_68EEA17E-3B73-4175-A45A-E173C28457DF03'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

2006-11-20 23:50:32.63 spid57 Internal I/O request 0x80348BD8: Op: Read, pBuffer: 0x11030000, Size: 1048576, Position: 32980533248, UMS: Internal: 0x1, InternalHigh: 0x80348C68, Offset: 0x80348C68, OffsetHigh: 0x0, m_buf: 0x11030000, m_len: 0, m_actualBytes: 0, m_errcode: 995, BackupFile: SQLBACKUP_68EEA17E-3B73-4175-A45A-E173C28457DF03

2006-11-20 23:50:32.66 spid57 BackupMedium::ReportIoError: read failure on backup device 'SQLBACKUP_68EEA17E-3B73-4175-A45A-E173C28457DF01'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

2006-11-20 23:50:32.66 spid57 Internal I/O request 0x80348DA8: Op: Read, pBuffer: 0x11230000, Size: 1048576, Position: 34506211328, UMS: Internal: 0x0, InternalHigh: 0x2, Offset: 0x0, OffsetHigh: 0x0, m_buf: 0x11230000, m_len: 0, m_actualBytes: 0, m_err

Comments

  • Options
    peteypetey Posts: 2,358 New member
    Do you encounter the same situation if you used local paths instead of UNC paths, for the restore? As you are performing the restore on the DBSrvr4 server, you should be able to use local paths instead of \\DBSrvr4\Backup\...
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Options
    I am using UNC paths for flexibility since the script is built dynamically. I will hardcode the local drive information and see if it happens again.

    Thanks,
    John
Sign In or Register to comment.