October 22, 2013 at 10:17 am
Hi There,
I have a log shipping setup between two 2008 SQL servers with no monitor server. Logs are recieved into the secondary shared folder and the logs state shipping is successful. On viewing the logs i see it skipps all trans logs. Checked permissions, the primary DB is updated so there should be data in the logs, Secondary server has access to its logship folder. The secondary DB is in a restoring state and was created through the LogShip GUI and not an archive backup. Any ideas would be greatly appreciated as my next step is to trash and start again which will cause me big problems. The Primary server is clustered but do not see why this should be causing a problem as the secondary server logshipping folder has all trans logs and everything reports as being fine except for the fact it is skipping them!
Thanks Again.
October 22, 2013 at 10:50 am
Are the LSCopy_ and LSRestore_ jobs on the secondary active? What does the job history say for those jobs?
----------------------------------------------------------------------------
Sacramento SQL Server users group - http://sac.sqlpass.org
Follow me on Twitter - @SQLDCH
----------------------------------------------------------------------------
October 23, 2013 at 2:45 am
Thanks for replying.
Yes both are active and report 'Job Succeded'. An expanded view of the history shows processing of each trans log but with 'Skipped log backup file Secondary DB' and 'Could not find a backup file to be applied'. So it can see all the trans logs but just skipps them...
October 24, 2013 at 2:06 am
check backup history on Primary. (Check for LSN numbers)
check Restore history on Secondary. From this you can come to know about if there is any latency between Backup & Restore.
Why the secondary is kept on Restoring mode ? was that preferred for your environment ?
Instead we can go with Standby / ReadOnly mode.
If the database is in Standby mode, users can access data – except when a log backup is being restored.
2 Options - restore job will disconnect users, or if the restore is delayed until after the users are disconnected.
Monitoring please refer :
Reports - Transaction Log Shipping Status.
http://technet.microsoft.com/en-us/library/ms190224.aspx
Cheers,
- Win
"Dont Judge a Book by its Cover"
October 24, 2013 at 6:01 am
Thanks for your response. Standby wasnt thought of as an option as we are shiiping logs every 15 mins and didnt want booted sessions or trans logs queueing. The Jobs are conistent and upto date from the primary servers folder and the secondary 'shipped to' folder so i do not believe this is the case and i would expect a different error (or at least an error!).
Thanks
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply