Log Shipping - Working or not working

Hello there,

I set up Log Shipping and all was working fine till this morning when I queried the secondary db to see if the DB is is sync with the primary Db and it turned out that since 21th Sept, the secondary DB is not getting updated.Under LSAlert job report in primary & secondary server the status shows 'Alert' in red whereas the copy & restore jobs are running properly.Also the share folders, I see all the files with the correct dates. but the secondary db is not in sync. One thing to mention is that the 2 servers time has gone 1 hour back since 22 Sept due to Daylight saving. Could that have messed the log shipping. Now what is the way out to this. Do i need to del the log shipping which I created and again create a new one again.Please help!!!!

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

EugeneZ ZhitomirskySQL SERVER EXPERTCommented:
try to find the exact error of this Alert. Is it native logship\ 3rd party backup sw logship?
it can be due to size of your prim DB trans log size\network  slowness..delay)

and if your Secondary DB is out of sync for long time due to corrupted trans log file
you may need to reinit log ship ...

before you start reinit:

please check for the issues that sounds like corrupted trans log backup file that you may got by rebooting server during trans log backup ( as an example)
Different ways to monitor Log Shipping for SQL Server databases
zolfAuthor Commented:
Thanks for your feedbacks.

I am using the native MSSQL 2008R2 Log Shipping.

I have attached the screenshot also. Weird this mornign I again created a new logshipping and as you can see it worked good for some time and then again I statred gettign this error.see screeshot. Why is this happening.Please help!!!


EugeneZ ZhitomirskySQL SERVER EXPERTCommented:
if you'll see 1 line down from your highlighted (details)
you'll this alert is actually "warning"
delayed restore

it looks like your default (or what it is 15 mins (as an example) restore is running to often and you'd need to adjust it (e.g every 30 mins) unless
check details to see when last restore ran successfully

IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

zolfAuthor Commented:
if you'll see 1 line down from your highlighted (details)
Can you please tell me the time...I could not see that warning you mentioned.

it looks like your default (or what it is 15 mins (as an example) restore is running to often and you'd need to adjust it (e.g every 30 mins)
Why do you say Restore?? and where do I need to change this.
EugeneZ ZhitomirskySQL SERVER EXPERTCommented:
please click on this line and see the full error ..

zolfAuthor Commented:
Ok, the full error says. what do you recon

Date            9/28/2015 8:46:00 AM
Log            Job History (LSAlert_PPG-REPORT)

Step ID            1
Server            PPG-REPORT
Job Name            LSAlert_PPG-REPORT
Step Name            Log shipping alert job step.
Duration            00:00:00
Sql Severity            16
Sql Message ID            14421
Operator Emailed            
Operator Net sent            
Operator Paged            
Retries Attempted            0

Executed as user: PPG-REPORT\ZSQLService. The log shipping secondary database PPG-REPORT.kaizenpo has restore threshold of 45 minutes and is out of sync. No restore was performed for 968 minutes. Restored latency is 8 minutes. Check agent log and logshipping monitor information. [SQLSTATE 42000] (Error 14421).  The step failed
EugeneZ ZhitomirskySQL SERVER EXPERTCommented:
#1 it is "warning"

#2 "No restore was performed for 968 minutes. " 

Start from Check agent log and logshipping monitor information.

"No restore was performed for 968 minutes. " : it can be normal for your DB (e.g Weekend Reindex of a very large DB can make trans log too large..)
it can be an indicator of a very -very large Trans log with a very-very slow network:


Secondary Server restore job is disabled (please check  it is still "ON". etc)


Primary Sql Server has missed TransLog for this DB


The TransLog backup File was "MIA" or there is an another Translog Backup job additionally to the logship

After your investigation you may need to reinit this DB logship

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
zolfAuthor Commented:
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.