.trn files are not restoring

Question

Post reply

.trn files are not restoring

sundar329

Say Hey Kid

Points: 680
More actions
July 5, 2016 at 8:04 am

#319725

Hi All,
I have a database log shipped between 2 servers. I get below error message captured in restored job:
Transaction log file I:\ABC_LS\602BAF84-E664-4BD4-BFBA-D7F782F59704_ABC_20160704200001.trn was skipped. More recent transaction log file must be applied to database.
To fix this,
Am restoring a t-log manually and running restore job in secondary server. It starts restoring other T-logs. Is there any way to fix this issue completely. Recommendations are welcome.
Thanks in advance.

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

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

rvsc48 SSCertifiable Points: 7685 More actions · Answer 1

Is the log shipping process trying to work with a very large transaction log backup when this issue occurs?

sundar329 Say Hey Kid Points: 680 More actions · Answer 2

Size of T-logs that was skipped was not more than 250 MB.

Steve Jones - SSC Editor SSC Guru Points: 736222 More actions · Answer 3

Somehow a log file was not transferred or not restored. Do you still have the missing file?

rvsc48 SSCertifiable Points: 7685 More actions · Answer 4

Let's go the other direction, due to the size you stated, it could be a database with very little or no activity which could be causing the restore to "skip" files. This was taken from another thread, but probably still may apply to your issue:

I found two solutions to this problem:

In this test environment, there are no active transactions happening. The log shipping restore job kept skipping the log shipping backups, UNTIL, I created a table in the primary DB...then when I ran the restore job it still skipped the previous backups but it restored the latest backup since there were changes to apply. This is just an issue in the quiet testing environment. Makes sense, SQL doesn't need to restore a log backup initially until something changes.

One other work around is you can update log_shipping_monitor_secondary to a known good backup and after doing that the restore job started applying the backups:

UPDATE [msdb].[dbo].[log_shipping_monitor_secondary]

SET [last_restored_file] = 'X:\SomeLogshippingFolder\LogshippedDB_20130308222505.trn'

sundar329 Say Hey Kid Points: 680 More actions · Answer 5

when I restore the next T-Log file it starts restoring rest of the files. It happens every day on different timings 🙁