|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: Today @ 9:53 PM
Points: 817,
Visits: 2,394
|
|
Hi,
Database backup failed due to server four HD failure and RAID 5 configuration also OS crashed...not able to reboot the server.. in this case, change the new four HD and install fresh OS then restored database from last day good backup from Tape.. so 1 day data was lost..
I try to restore the failed backup file but it won't allowed ...
Checked by VERIFYONLY command as below errors..
restore verifyonly from disk = 'D:\emsevent\emsevents_backup_2013_03_02_000002_3310132.bak' with checksum
Msg 3189, Level 16, State 1, Line 3 Damage to the backup set was detected. Msg 3013, Level 16, State 1, Line 3 VERIFY DATABASE is terminating abnormally.
restore by CONTINUE_AFTER_ERROR; this command will not help
Processed 528 pages for database 'emsevents', file 'EMSEvents_dat' on file 1. Processed 0 pages for database 'emsevents', file 'EMSEventsIndex_dat' on file 1. Processed 16 pages for database 'emsevents', file 'EMSTimeAndLocalTimeIdx_dat' on file 1. Processed 16 pages for database 'emsevents', file 'EMSLocalDateAndTimeIdx_dat' on file 1. Processed 16 pages for database 'emsevents', file 'EMSLocalDateAndTimeAndLocalTimeIdx_dat' on file 1. Processed 2 pages for database 'emsevents', file 'EMSEvents_log' on file 1. Msg 3283, Level 16, State 1, Line 1 The file "EMSEventsIndex_dat" failed to initialize correctly. Examine the error logs for more details. Msg 3283, Level 16, State 1, Line 1 The file "EMSTimeAndLocalTimeIdx_dat" failed to initialize correctly. Examine the error logs for more details. Msg 3283, Level 16, State 1, Line 1 The file "EMSLocalDateAndTimeIdx_dat" failed to initialize correctly. Examine the error logs for more details. Msg 3283, Level 16, State 1, Line 1 The file "EMSLocalDateAndTimeAndLocalTimeIdx_dat" failed to initialize correctly. Examine the error logs for more details. Msg 3283, Level 16, State 1, Line 1 The file "EMSEvents_log" failed to initialize correctly. Examine the error logs for more details. The database cannot be recovered because the log was not restored. This RESTORE statement successfully performed some actions, but the database could not be brought online because one or more RESTORE steps are needed. Previous messages indicate reasons why recovery cannot occur at this point. Damage to the backup set was detected. RESTORE WITH CONTINUE_AFTER_ERROR was successful but some damage was encountered. Inconsistencies in the database are possible. RESTORE DATABASE successfully processed 578 pages in 0.479 seconds (9.427 MB/sec).
Error log Message
RESTORE detected an error on page (16640:1409297664) in database "emsevents" as read from the backup set.
If any alternative ways how to resolved failed backup set?
thanks ananda
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 4:15 PM
Points: 37,651,
Visits: 29,903
|
|
I think you're going to have to restore an older backup. That looks too damaged to be useful.
Gail Shaw Microsoft Certified Master: SQL Server 2008, MVP SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter We stand on the bridge and no one may pass
|
|
|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: Today @ 9:53 PM
Points: 817,
Visits: 2,394
|
|
sorry for mention above errores I have tested failed backup files, and encounterd errors were from damaged backup file set on 02-03-2013
Successfully restored last day at 01-03-2012 good backup set and database working & fine..
|
|
|
|