Our live instance of SQL server 2005 crashed last night but managed to write out a corrupted transaction log file.
Partial results from RESTORE HEADERONLY commands below:
193000.trn OK - First LSN 140773000030325500001 / Last LSN 140773000304635700001
195224.trn Corrupted *Incomplete*
203000.trn OK - First LSN 140773000304635700001 / Last LSN 140773001216537800001
So it looks to me as though I should be able to ignore the 195224.trn file to continue the log restore. Unfortunately our automated log restore job tried to restore the 195224.trn file and of course got an error.
So now when i try to run
RESTORE LOG [dbname] FROM DISK =N'H:\Logs\203000.trn' WITH NORECOVERY
I get the below error
A previous restore operation was interrupted and did not complete processing on file 'log'. Either restore the backup set that was interrupted or restart the restore sequence.
I have tried running both this file and the previous OK file WITH RESTART but that has not worked.
Is there anything else I can do without having to resort to something slower like restore using diff?
Aucun commentaire:
Enregistrer un commentaire