August 22, 2013 at 4:52 am
Hi everyone.
Hope someone can offer some guidance here.
Set up log shipping. All looked ok. The noticed that I was getting the [SQLSTATE 42000] (Error 14421). The step failed. Error on the secondardy server in regards to the LSAlert job.
when I run
select * from msdb.dbo.log_shipping_monitor_secondary
I do intend see the last_restored_file as blank for the database.
However I do see the log shipped from Primary and does exist on secondary.
The copy and restore jobs say everything is ok , but as I can see from the above query it is not being restored onto the secondary Database.
When looking at the restore job on the secondatry server I see these messages :
2013-08-22 11:45:27.57Skipped log backup file. Secondary DB
Anything I can do to check \ resolve this ?
Is the quickest way to resolve it , is to reconfigure the LS for this DB again ?
many thanks all.
August 22, 2013 at 6:42 am
sounds like you are missing a log backup. Check the databases backup history from the backupset table in msdb on the primary. If there are missing log backups and you still have them apply them manually
If you do not have them and if you have not taken another full backup since you initialised logshipping you can restart from a differential, else restart from a new full backup (just disable the logshipping jobs whilst you do that, you dont have to drop\recreate logshipping)
---------------------------------------------------------------------
August 22, 2013 at 6:58 am
george sibbald (8/22/2013)
sounds like you are missing a log backup. Check the databases backup history from the backupset table in msdb on the primary. If there are missing log backups and you still have them apply them manuallyIf you do not have them and if you have not taken another full backup since you initialised logshipping you can restart from a differential, else restart from a new full backup (just disable the logshipping jobs whilst you do that, you dont have to drop\recreate logshipping)
Thanks for that. Think I have solved it.
I still had a log backup job enabled for this database on the primary server. This was a standard log backup job , and not related to Log shipping backup job. Removed that log backup and it seems to be functioning and move trn files as expected.
August 22, 2013 at 7:29 am
yep, thats the classic cause of that type of error in logshipping.
glad you sorted it.
---------------------------------------------------------------------
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply