September 20, 2013 at 9:59 am
I have an issue with my SQL 2012 database server and restoring a full backup (norecovery) then applying a differential backup. The error message is that there is a break in the LSN chain. The First LSN of the full backup is the same as the Full LSN of the differential backup so I'm confident there is not a break in the backup chain. I am restoring a Production Backup to our DEV Server, so the issue is not currently critical, but I don't feel confident that I could recover to a point in time if I had a Production failure.
Does anyone have knowledge of a Hot Fix or work around?
September 20, 2013 at 4:11 pm
Could you post the exact error message?
How do deduce that the first LSNs are the same?
[font="Times New Roman"]Erland Sommarskog, SQL Server MVP, www.sommarskog.se[/font]
September 23, 2013 at 6:53 am
The header file on each backup contains the LSN numbers. Querying the msdb database also produces matching LSN numbers.
September 25, 2013 at 5:55 am
I am travelling, and don't have the time to research this further. Anyone else who can step in?
[font="Times New Roman"]Erland Sommarskog, SQL Server MVP, www.sommarskog.se[/font]
September 25, 2013 at 6:10 am
Could you post the full error message?
There's a connect item related to restoring a SQL 2008 database using SSMS 2012 GUI, which posts an erroneous error message about LSN chain breaks, are you hitting that scenario?
It should still work through T-SQL restore commands if you're hitting that
September 25, 2013 at 6:42 am
I was able to successfully restore a smaller database (12GB). I'll have to wait to try this larger one (about 300GB) when we have to do another refresh. I can't really do it now.
September 25, 2013 at 7:34 am
So here's what did and did not work:
Didn't work:
1. Add full backup
2. Restore with NoRecovery
3. Add differential backup
What did work:
1. Add full backup
2. Add differential backup
3. Restore With Recovery and prompt for each file.
September 29, 2013 at 4:15 pm
So that is the problem: you are using the UI, instead of using T-SQL commands directly. At very least if you use the UI, and things don't work out, you should use the Script button to see what SSMS intend to do.
[font="Times New Roman"]Erland Sommarskog, SQL Server MVP, www.sommarskog.se[/font]
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy