Logshipping issue 2005 to 2014 in no recovery mode

all the jobs are running successful but the restore job is showing following message Skipped log backup file. Secondary DB: '5T', File: 'F:\SecondaryShared\5T_20160422144001.trn' 2016-04-22 09:48:01.97 Could not find a log backup file that could be applied to secondary database '5T'. 2016-04-22 09:48:01.97 The restore operation was successful. Secondary Database: '5T', Number of log backup files restored: 0 2016-04-22 09:48:01.98 Deleting old log backup files. Primary Database: '5T' 2016-04-22 09:48:01.98 The restore operation was successful. Secondary ID: '603bba1a-f150-4acf-a994-da5763fc0436'

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

JohnM commented · Apr 22, 2016 at 07:08 PM

Does the sql agent account have the appropriate permissions to the folder where the backup files are being shipped to?

1 ·

munnast commented · Apr 22, 2016 at 07:16 PM

yes, they have full control to the folder, t-log files are been shipped to secondary folder the only issue is it is unable to restore it. when I manually tried to restore the log file it is throwing an error lsn is so earlier to apply.there is a brake in LSN

1 ·

JohnM commented · Apr 22, 2016 at 08:25 PM

If the log shipping is now in sync and that backup file is from prior to the differential then you should be able to remove it from the folder and error would go away. Or to make things cleaner, you can stop the jobs, clear the destination folder (I'd copy them somewhere for safe keeping), take a differential, restore it, and then resume the jobs.

1 ·

JohnM commented · Apr 22, 2016 at 07:21 PM

Sounds like it's out of sync. Can you take a differential of the primary, restore it to the secondary and then resume the backup jobs?

0 ·

munnast commented · Apr 22, 2016 at 07:24 PM

I have done it already but still the same

0 ·

Show more comments