Another Log Shipping question

[wbodger]

So, I have setup log shipping a few times on my primary server because it keeps giving me problems. Now I think I have finally identified the problem and was wondering if you all could give me some input. It seems that if I am running a process (like creating large numbers of serial numbers) through the span of time when a log is to be shipped, that there is a problem with that log. Now, when I had set-up the log shipping I thought SQL Server 2k sp4 was smart enough to handle the issue, but it would appear that I am wrong. So, any thoughts on this? Should SQL server be able to handle this? The problem is that the secondary server is unable to load the transaction log files, it gets stuck in (Loading).

Willie

 

[ptheriault]

I'm not sure what you mean by "creating large numbers of serial numbers" but if you have created a large number of transactions then it will take longer for that sequence of the log to backup, copy and restore.

for example on Sundays I run re-indexing jobs. This creates huge trn files of over 2gb for about 5 hours. My threshold is every 15 min. So log shipping will fall behind by about 3 hours while these logs are applied.

Have you taken a look at the trn files that are coppied during this period.
And if you could answer these questions.
Are the trn files larger than the others?
Does the restore ever complete?
Is there an error?

- Paul

- If at first you don't succeed, find out if the loser gets anything.

 

[wbodger]

Yes, the log files are considerably larger (from perhaps 3 mb to 63 mb).
No, the restore does not ever complete.
Yes, there is an error. Unfortunately I rebuilt the log shipping and lost that history, but it was along the lines of the file not being properly ended/finished/closed. If it would help I can probably re-create the issue within the next week and then bring the issue back up then.

Willie

 

[ptheriault]

yes it would help to see the error.

- Paul

- If at first you don't succeed, find out if the loser gets anything.