How can I restart LSRestore step in Log Shipping process

Question

Post reply

How can I restart LSRestore step in Log Shipping process

Viewing 6 posts - 16 through 20 (of 20 total)

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

lw1990 SSC-Addicted Points: 435 More actions · Answer 1

Thank you Jon.Morisi and Perry Whittle for the valuable replies.

I got an error when doing the log restoring in log shipping and want to know why.

When I restored the log file(UserInfo_1_20160301100007.trn) of 03/01/2016 at 5:00am, it was done:

"The restore of database 'UserInfo_1' completed successfully."

But, When I restored the next one(UserInfo_1_20160301101501.trn) of 03/01/2016 at 5:15am, I got this error:

Restore failed for Server 'UserInfo_1'. (Microsoft.SqlServer.SmoExtended)

For help, click: ---

ADDITIONAL INFORMATION:

System.Data.SqlClient.SqlError: The log in this backup set begins at LSN 171240000001726900001, which is too recent to apply to the database. An earlier log backup that includes LSN 171240000001695900001 can be restored. (Microsoft.SqlServer.Smo)

Does this error mean the .trn file at 5:15am is corrupted? The log backup was not running? Or the server had a glitch or a latency issue?

Jon.Morisi SSChampion Points: 12846 More actions · Answer 2

The log in this backup set begins at LSN 171240000001726900001, which is too recent to apply to the database. An earlier log backup that includes LSN 171240000001695900001 can be restored.

It's saying you missed a LOG restore. There's another file older than the one your restoring that needs to be restored first.

lw1990 SSC-Addicted Points: 435 More actions · Answer 3

Thanks Jon.Morisi,

That's my question. I had 03/01/2016, 5:00 am restored successfully and 5:15 am with a "too recent" error! There is no backup and .trn file between these two logs, what is missing?

I even copied 4:45am, 5:00am, 5:15am manually from the primary server to the secondary server and got the same error.

There must be something wrong with the log backup processing at 5:15am in the primary server and made a bad .trn file. I just don't know what could be wrong.

Thanks,

lw

Jon.Morisi SSChampion Points: 12846 More actions · Answer 4

You can query backupset and look for your needed LSN between first_lsn and last_lsn.

lw1990 SSC-Addicted Points: 435 More actions · Answer 5

Thank you Jon.Morisi,

It is great to query the table Backupset and I found that there is an extra log backup between 5:00 and 5:15. The log shipping ships the log files at 5:00 and 5:15 from the backup location. So, the extra log file was missing to send to the secondary DB! (Actually, I don't know where that extra log was backed up to).

I can't find how that log backup was setup and where. It's not in maintenance plans, not in scheduled tasks. (There was a SQL developer/DBA before me set up them and never documented them). The only clue from the table Backupset is that all DBs are backup with type (I and L) plus master, msdb and model are with type D. The running time is between 4:55 and 5:09 am by server/Administrator.

How can I find the setting of this log backup and where?

Thanks,

lw

Jon.Morisi SSChampion Points: 12846 More actions · Answer 6

The "physical_name" of the backup can be found in: backupfile