Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Log Shipping 'skipping' all logs and not restoring


Log Shipping 'skipping' all logs and not restoring

Author
Message
neil.croft
neil.croft
Forum Newbie
Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)

Group: General Forum Members
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.
reuben.anderson
reuben.anderson
SSC Journeyman
SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)

Group: General Forum Members
Points: 85 Visits: 211
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
wsaharem
wsaharem
SSC Rookie
SSC Rookie (34 reputation)SSC Rookie (34 reputation)SSC Rookie (34 reputation)SSC Rookie (34 reputation)SSC Rookie (34 reputation)SSC Rookie (34 reputation)SSC Rookie (34 reputation)SSC Rookie (34 reputation)

Group: General Forum Members
Points: 34 Visits: 96
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.



Jinu43
Jinu43
Valued Member
Valued Member (65 reputation)Valued Member (65 reputation)Valued Member (65 reputation)Valued Member (65 reputation)Valued Member (65 reputation)Valued Member (65 reputation)Valued Member (65 reputation)Valued Member (65 reputation)

Group: General Forum Members
Points: 65 Visits: 211
I have same issue.
Where did you forced the restore option or which changes you made on primary server??

Thanks in advance.. Smile
SKYBVI
SKYBVI
Ten Centuries
Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)

Group: General Forum Members
Points: 1231 Visits: 3239
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.. Smile


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

Regards,
Skybvi
Perry Whittle
Perry Whittle
SSCrazy Eights
SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)

Group: General Forum Members
Points: 8780 Visits: 16554
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.. Smile

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" ;-)
Solon
Solon
Forum Newbie
Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)

Group: General Forum Members
Points: 4 Visits: 377
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?
lfernandesfotos
lfernandesfotos
Grasshopper
Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)

Group: General Forum Members
Points: 19 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.
Lynn Pettis
Lynn Pettis
SSC-Insane
SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)

Group: General Forum Members
Points: 24171 Visits: 37936
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?

Cool
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)
louislamour2673
louislamour2673
Grasshopper
Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)

Group: General Forum Members
Points: 10 Visits: 512
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'
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search