Fix for Unable to create restore plan due to break in the LSN Chain in SQL Server
Hello and welcome, today lets explore on Fix for Unable to create restore plan due to break in the LSN Chain in SQL Server. This may happen to because of many reasons, one of the common reason is that if you take a differential backup and change the database’s recovery model and switched to simple recovery for some reason and then switched back to its original state (differential or full) to reinitialize the LSN, but that does leave a gap. so for whatever reason if you get that kind of backup file and some one asks you to restore in the server, you will get a error stating Unable to create restore plan due to break in the LSN Chain – Lets fix it
To restore this kind of .bak files instead of doing a restore we go with “Restore File and File Groups”. when you click on this tab you should see a new dailouge box opening up as show in the following picture
To Database: it’s up to you to restore in existing database or if you give a specific name over there SQL Server will create a new Database for you and restore in it.
From Device : Just give the path where your .bak file is located
Check only the Full type of backup check box as we are having a mismatch in LSN we don’t want TLog db to get restored.
your database will get restored. hope you like the tutorial