locked
Backup and Restore RRS feed

  • Question

  • How to overcome the below error?

    Msg 4326, Level 16, State 1, Line 1
    The log in this backup set terminates at LSN 48000000040000001, which is too early to apply to the database. A more recent log backup that includes LSN 48000000047200001 can be restored.
    Msg 3013, Level 16, State 1, Line 1
    RESTORE LOG is terminating abnormally.

    Thursday, February 11, 2016 4:53 AM

Answers

  • You must be aware that transaction log backups are incremental and are linked via LSN chain if you miss the chain or if engine finds out you are trying to restore log file which does not matches with chain such message is flashed.

    In your case you missed some transaction log file to restore. See backup history to find out what is missed


    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My Wiki Articles

    MVP

    • Marked as answer by saravana raj Thursday, February 11, 2016 8:43 AM
    Thursday, February 11, 2016 7:12 AM

All replies

  • What the error message tell you. You are trying to restore a series of log backups and skip one or more in the log backup chain. No can do. you need to find that missing log backup and restore that as well.

    Tibor Karaszi, SQL Server MVP (Web Blog)

    • Proposed as answer by Shanky_621MVP Thursday, February 11, 2016 7:11 AM
    Thursday, February 11, 2016 4:56 AM
  • You must be aware that transaction log backups are incremental and are linked via LSN chain if you miss the chain or if engine finds out you are trying to restore log file which does not matches with chain such message is flashed.

    In your case you missed some transaction log file to restore. See backup history to find out what is missed


    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My Wiki Articles

    MVP

    • Marked as answer by saravana raj Thursday, February 11, 2016 8:43 AM
    Thursday, February 11, 2016 7:12 AM