Log Shipping re-sync

  • Hi,

    I just notice logshipping restore job is failling on Secondary server not sure how long but copy job is running successfully.

    I tried to execute restore job and got below error.

    *** Error: The log in this backup set begins at LSN 7291000009045100001, which is too recent to apply to the database. An earlier log backup that includes LSN 7291000006306300001 can be restored.

    Can you please help me to resolve this issue.

  • You missed some of the logs in chain... a Broken Log Chain.

  • Restore the last FULL Backup, then Differential backup (if any) & finally all log backups in proper sequence.

  • You can review the restore history in msdb to determine the last successfull restore. If you still have access to the log files, you can just pick up from that point forward until current. The automated process will continue on from there once it's at the correct point.

  • I try to look for log files but not able to find. so i am thiking to remove the Logshipping and set-up again or is there any other way to perform this task??

  • Jinu43 (11/29/2011)


    I try to look for log files but not able to find. so i am thiking to remove the Logshipping and set-up again or is there any other way to perform this task??

    You dont have to remove log shipping, just restore a full backup and all subsequent logs, leave the DB in standby so that more logs can be applied.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply