SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Options with a TL Backup goes bad


Options with a TL Backup goes bad

Author
Message
Shawn Therrien
Shawn Therrien
SSC-Enthusiastic
SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)

Group: General Forum Members
Points: 103 Visits: 158
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?
Orlando Colamatteo
Orlando Colamatteo
SSCoach
SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)

Group: General Forum Members
Points: 15359 Visits: 14396
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
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search