How to reset or resume transaction log chain for a database in high availability during restore of database

by Nasy Deen   Last Updated August 02, 2018 02:06 AM

I ran into this specific error "The log in this backup set begins at LSN X:Y:Z, which is too recent to apply to the database. An earlier log backup that includes LSN A:B:C can be restored."

I came across this when i had previously removed a database which was in HA group. Due to various reason, i deleted the secondary database and tried to re-initialize the database in HA by adding back into the group again via the Add database to HA wizard. At the end of the final step, it hit an error prompting for transaction logbackup to be restored before syncing to secondary replica. I tried but failed giving the above mentioned error with LSN. Tried a few more times and still fails.

I would like to point out, best is to restore the log file which it is required and continue. What really confuses me is that, doing a full backup and restore would be able to resolve the LSN issue but it did not. why is this behavior? what are the factors that affect this? Would appreciate any insight on the subject of log chain and how to reset it.

Thanks in advance. Cheers.

Related Questions

Transaction Log Truncation with Copy Only

Updated March 28, 2018 17:06 PM

`AVAILABILITY_REPLICA` `log_reuse_wait_desc`

Updated January 29, 2018 17:06 PM