February 5, 2010 at 7:38 pm
I have just taken over as the systems admin at a new place
and there is log shipping in place for SQL1 -> SQL2
3 of the Db's are sending their TRN files to the location on SQL2,
but 1 Db (the most important) has started poping up error 14420 in the event log.
Details of the message is.
--
DATE/TIME:6/02/2010 9:46:00 AM
DESCRIPTION:The log shipping primary database ***DB NAME*** has backup threshold of 60 minutes and has not performed a backup log operation for 907 minutes. Check agent log and logshipping monitor information.
COMMENT:(None)
JOB RUN:(None)
--
I had not made any changes in SQL and have noticed (going through old emails) that this occured bout a month ago.
Im not really an SQL guy, so not sure what to be looking for
but i was able to setup a TEST Db with log shipping to the other server and it looked ok.
i have rebooted the SQL2 but not the SQL1 yet.
Any thoughts please?
February 6, 2010 at 5:00 pm
Hi ,
Check your backup job on primary server...If it is not running then try to run the job manually it will solve your problem.
February 6, 2010 at 7:05 pm
Review the transaction log backup job and identify why that job is failing. The error you are getting is fairly specific and is telling you that the transaction log has not been backed up.
If you have any issues with identify why that job is failing, post back and we'll help you out.
Jeffrey Williams
Problems are opportunities brilliantly disguised as insurmountable obstacles.
How to post questions to get better answers faster
Managing Transaction Logs
February 7, 2010 at 5:19 pm
Strange thing is, this started working again by itself later in the night.
Very odd, and it looks like it might have been a problem a month ago for a while.
Odd how its was only occuring on 1x Db out of the many.
I will be replacing the SQL server in a few months, and although i created a test log shipping off a test Db. It put the .BAK and then the TRN files on the remote location.
The other Db's just have the trn files there and the Db's are fully in the SQL manager of the seccond server.
Any walkthroughs on setting up log shipping and having the logs "replay" into the remote Db ?
so its a proper DR solution ?
February 7, 2010 at 5:49 pm
You really need to identify why the transaction log backup job is failing. If you do not identify and correct that issue it is going to occur again.
Here is what I think is probably happening: at some point the log chain is getting broken. From that point forward the transaction log backup is failing. After the next full backup completes successfully, the log chain is re-established allowing the transaction log backups to run and complete successfully.
The log chain will be broken like that if someone issues a backup log ... with truncate_only (deprecated in 2005, no longer functional in 2008), or the system is being changed to simple recovery model and back to full. Either of which I have seen done to 'fix' log files that grow too large during index rebuild operations.
Again, identify why your transaction log backups are failing or this issue will just happen again.
Jeffrey Williams
Problems are opportunities brilliantly disguised as insurmountable obstacles.
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply