Log shipping error

Question

Post reply

Log shipping error

arooj300

Hall of Fame

Points: 3433
More actions
June 13, 2014 at 1:26 am

#287445

Hi All,
I have scheduled job for log shipping every 24 hours at midnight. First day it was running successfully but from 2nd day file is not restoring in the Secondary database.
can we schedule job every 24 hours or I need to schedule job every 15 minutes or 30 minutes.
Please clarify my doubt because my requirement that job should run everyday 12 Am at midnight.
Or is there any best solution which has alternate option of Log shipping.
Thanks,
Arooj

Viewing 15 posts - 1 through 15 (of 27 total)

You must be logged in to reply to this topic. Login to reply

Beatrix Kiddo SSC-Dedicated Points: 32407 More actions · Answer 1

Beatrix Kiddo

SSC-Dedicated

Points: 32407

June 13, 2014 at 2:20 am

#1721351

[dup]

Beatrix Kiddo SSC-Dedicated Points: 32407 More actions · Answer 2

Can you tell us what the exact error message you're getting is?

When you say you're running it every 24 hours do you mean the backup job, the copy job and the restore job, or are you backing up much more frequently but only copying and restoring every 24 hours (which sounds risky to me)?

arooj300 Hall of Fame Points: 3433 More actions · Answer 3

Hi,

Thanks for the reply. i am getting error like " Could not find a log backup file that could be applied to secondary database'"

I have scheduled job for taking backup, copy, restore backup file at the same time.

free_mascot One Orange Chip Points: 27169 More actions · Answer 4

It looks like before Log shipping restore the backup file it is deleting. Hence this is having issue. You can increase the backup retention time to 48 or 36 and problem will be solved.

---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."

Beatrix Kiddo SSC-Dedicated Points: 32407 More actions · Answer 5

Ok, that's helpful but we need to go through it step by step as there are so many variables.

Are you taking transaction log backups outside the log-shipping environment? If so, which folder are the log backups going to? The copy job on your secondary will only look in the log shipping folder specified in your log shipping configuration. (I've marked this path with an arrow in the screenshot I've attached.) If you take log backups that aren't stored in that folder, it will break log shipping because the copy and restore jobs won't have an unbroken chain of transaction log backups to work with.

Does that make sense? Can you check if that is happening first of all?

arooj300 Hall of Fame Points: 3433 More actions · Answer 6

I am not taking logbackup outside the log shipping environment. i have configured log shipping again. i need to monitor again today night.

Beatrix Kiddo SSC-Dedicated Points: 32407 More actions · Answer 7

Why not just set it to run every minute for now, and then you can monitor it over the 30 minutes, rather than having to wait until later?

arooj300 Hall of Fame Points: 3433 More actions · Answer 8

Actually for 30 minute its working fine but when i set it for 24 hours . first day it is restored but from 2nd day it start giving error

Beatrix Kiddo SSC-Dedicated Points: 32407 More actions · Answer 9

Ok, then something else may well be backing up your database and breaking your log chain (as far as log-shipping is concerned). I'd check that with your sysadmins.

It sounds like they're doing this overnight.

arooj300 Hall of Fame Points: 3433 More actions · Answer 10

Hi All,

while restoring database in secondary server I am getting below error

"row index must be greater than or equal to zero and less than the number of rows. ParameterName: nRowIndex. Actual value was 4(microsoft.sqlserver.Gridcontrol)"

I have searched in so many and they are saying restart the seconadry server instance. I have restarted sql services, but still the error is remain same.

Thanks

Beatrix Kiddo SSC-Dedicated Points: 32407 More actions · Answer 11

You need to give a bit more information with your questions. Are you doing this manually or as part of the LSRestore job?

arooj300 Hall of Fame Points: 3433 More actions · Answer 12

i am getting error while configuring log shipping in the secondary server. backup has been taken while restoring error is coming

arooj300 Hall of Fame Points: 3433 More actions · Answer 13

Hi All,

I am getting below error while restoring log backup in secondary server.

"Message

2014-06-20 06:04:01.25Skipped log backup file. Secondary DB: 'OS_Test', File: 'M:\Secondary DB\OS_Test_20140619073534.trn'

2014-06-20 06:04:01.25Could not find a log backup file that could be applied to secondary database 'OS_Test'.

2014-06-20 06:04:01.26The restore operation was successful. Secondary Database: 'OS_Test', Number of log backup files restored: 0

2014-06-20 06:04:01.26Deleting old log backup files. Primary Database: 'OS_Test'."

Everytime Log shipping job is failing. I schedcule job every 24 hours. First day it was running fine but from second day it start giving error. Is there any permanent solution to resolve this issue.

----Thanks in advance----

Beatrix Kiddo SSC-Dedicated Points: 32407 More actions · Answer 14

Beatrix Kiddo (6/13/2014)
Ok, then something else may well be backing up your database and breaking your log chain (as far as log-shipping is concerned). I'd check that with your sysadmins.
It sounds like they're doing this overnight.

Have you checked this?