November 29, 2012 at 9:20 pm
I have a full backup, I made a mistake with some data and made a transaction log backup so I could restore the db on another server and compare data.
Now, I made a mistake can called it something like "dbname 5:30pm.trn", which wasn't caught by SSMS, but created a file "dbname 5", because the colon caused an issue.
Once it was done I refreshed the directory and it was 0k in size.
It seems that just broke the restore chain entirely and no TL backups after that corrupt file would be of any use. Time to just do another full backup and start the chain fresh?
Any advice on what a more experienced DBA would do in this situation? Any way to recover the situation or is it just making the best of the situation at this point?
December 5, 2012 at 10:58 pm
Are you sure the TL backup completed successfully?
It should not matter the name of the file, or even that it has an extension. SQL Server will still read it as long as it is in the proper format and begins with the correct LSN.
At any rate, if this operation did in fact break the log chain by marking VLF's for reuse but not writing the data to the backup file then you can always re-establish the log chain by taking a differential backup from the source (provided no new FULL backups have been taken since this unfortunate event) and applying it to the secondary database.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply