Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

Log Shipping 'skipping' all logs and not restoring Expand / Collapse
Author
Message
Posted Monday, January 7, 2008 10:55 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, May 18, 2009 11:23 PM
Points: 9, Visits: 29
Aaah Nathan, thankyou. If only I could find these replies before spending the day working it out for myself (OK, with Google then..) Yes, you are right, I will have to re-initialise the log-shipping process again, do another backup and restore, and re-start. This time I think it WILL work as I desire.





Post #439876
Posted Thursday, December 17, 2009 6:14 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, July 9, 2014 7:56 AM
Points: 44, Visits: 153
Hi,

I have this problem also. All the jobs execute successfully, but the restore job checks each transaction log and skips all of them. I can manually load the first valid one, and the next ... and then after the next backup, copy restore cycle... the restore job just carries on skipping all the logs.

Anyone know - how is it storing the LSN it's looking for?

Cheers,
R


Post #835619
Posted Tuesday, January 26, 2010 12:41 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, September 6, 2013 4:37 AM
Points: 33, Visits: 94
I was noticing the same thing, and what I discovered was that Primary was backing up and shipping to secondary just fine, and restores were being attempted. However, since there were zero changes, everything was being skipped. I forced a change on Primary, and it found the correct file and restored. No error, and alerts went away.

The bummer of all this is that it's not smart enough to log the attempt. So if you have a small database with zero changes say for 2 hours, and you set your alert for 45 minutes, it's going to scream at you often even though there is no issue.



Post #853431
Posted Friday, February 10, 2012 9:53 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, August 14, 2013 1:59 PM
Points: 63, Visits: 204
I have same issue.
Where did you forced the restore option or which changes you made on primary server??

Thanks in advance.. :)
Post #1250430
Posted Friday, February 10, 2012 10:03 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Tuesday, June 10, 2014 6:14 AM
Points: 1,200, Visits: 3,237
Jinu43 (2/10/2012)
I have same issue.
Where did you forced the restore option or which changes you made on primary server??

Thanks in advance.. :)


You can do the 1st restore log after full backup in SSMS manually
and see if it fixes now.

Regards,
Skybvi
Post #1250435
Posted Friday, February 10, 2012 10:27 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 4:09 PM
Points: 6,163, Visits: 13,306
Jinu43 (2/10/2012)
I have same issue.
Where did you forced the restore option or which changes you made on primary server??

Thanks in advance.. :)

If you're having the same issue experienced in this post it's highly likely that in between the database restore occurring and the jobs starting a log backup has been taken, either by an admin or by another running backup job, and not transferred to the secondary server.
Once log shipping has been implemented for a database all log backups must be done via the log shipping plan and not via any external jobs\processes.

Please create a new post in future, it helps you and others


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1250449
Posted Tuesday, February 21, 2012 1:03 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Yesterday @ 8:08 AM
Points: 4, Visits: 139
What about restores to the primary database? I implemented log shipping on our reporting database, mainly just for testing purposes. This database gets restored nightly from our production backup. I had initialized the secondary database with a backup and set the the logs to only ship once a day after the restore occurs on the primary. I encountered the same problem. The job says it succeeds but it skips all the log files. I confirmed that there are no jobs on the server that would backup the log other than the log shipping job. The log files are fairly large (5 GB). Any guesses?
Post #1255541
Posted Monday, March 26, 2012 1:28 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, May 22, 2012 1:59 PM
Points: 15, Visits: 45
I Have the same problem.

I made the following test:

- Created a Log Shipping into a database BILLING
- Inserted 4 rows in a table BILLING_REP
- The Log Shipping worked well
- Deleted the 4 rows from the same table
- The Log Shipping stops working

Already redid the job several times and got the same result.
Post #1272933
Posted Monday, March 26, 2012 1:42 PM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Today @ 4:59 PM
Points: 23,000, Visits: 31,482
Solon (2/21/2012)
What about restores to the primary database? I implemented log shipping on our reporting database, mainly just for testing purposes. This database gets restored nightly from our production backup. I had initialized the secondary database with a backup and set the the logs to only ship once a day after the restore occurs on the primary. I encountered the same problem. The job says it succeeds but it skips all the log files. I confirmed that there are no jobs on the server that would backup the log other than the log shipping job. The log files are fairly large (5 GB). Any guesses?


Let me get this right.

You do a full restore of the reporting database from production nightly.

You have transaction log backups taken during the day that you want transfered and loaded at night after the restore.

Am I correct so far?



Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
Post #1272949
Posted Wednesday, March 27, 2013 10:02 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Today @ 11:46 AM
Points: 6, Visits: 374
I found two solutions to this problem.

I am testing log shipping on our test server in SQL 2005. In this test environment, there are no active transactions happening. The log shipping restore job kept skipping the log shipping backups, UNTIL, I created a table in the primary DB...then when I ran the restore job it still skipped the previous backups but it restored the latest backup since there were changes to apply. So when I do this in my production environment, it probably won't be an issue, this is just an issue in the quiet testing environment. Makes sense, SQL doesn't need to restore a log backup initially until something changes.

One other work around is you can update log_shipping_monitor_secondary to a known good backup and after doing that the restore job started applying the backups:

UPDATE [msdb].[dbo].[log_shipping_monitor_secondary]
SET [last_restored_file] = 'X:\SomeLogshippingFolder\LogshippedDB_20130308222505.trn'

Post #1436010
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse