SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Log Shipping copy job fails intermittently


Log Shipping copy job fails intermittently

Author
Message
Mani-584606
Mani-584606
SSCrazy
SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)

Group: General Forum Members
Points: 2540 Visits: 1998
Hi,

We are using log shipping in SQL Server 2008 R2 and working fine for years.

But from last 2 weeks, We are getting 3 different kind of errors intermittently.

Some times error1, sometimes error2 and sometimes error3. It's not consistent.

Verified the paths and access and are good.


1. *** Error: Could not find file '\\INSVS\LogShipping_Backups\Umbrella_20120817184501.trn'.(mscorlib) ***

2. Message
2012-08-20 13:11:33.22 *** Error: The handle is invalid.
(mscorlib) ***
2012-08-20 13:11:33.27 ----- END OF TRANSACTION LOG COPY -----

Exit Status: 1 (Error)

3. The specified network name is no longer available

Please advise
chandan_jha18
chandan_jha18
SSCrazy
SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)

Group: General Forum Members
Points: 2287 Visits: 2134
1) The error could be due to early cleanup or purge of the log file before the restore could have processed. Increase the time duration for retaining the backups files

2) no idea about this.

3)Network hiccup: Occasional hiccup which led to the network being inaccessible. Whenever this happens, make sure that the subsequent schedule of the entire process was successful. If it was, no need to worry but do open a request with Infrastructure guys to let them know about the network issue.

Chandan
Brandie Tarvin
Brandie Tarvin
SSC-Dedicated
SSC-Dedicated (37K reputation)SSC-Dedicated (37K reputation)SSC-Dedicated (37K reputation)SSC-Dedicated (37K reputation)SSC-Dedicated (37K reputation)SSC-Dedicated (37K reputation)SSC-Dedicated (37K reputation)SSC-Dedicated (37K reputation)

Group: General Forum Members
Points: 37181 Visits: 9268
RE: error # 2. A handle is usually a SPID related to an internal process or the new system views. If you can predict an error # 2, set up a server-side trace to catch all the stuff going on when the error happens. That will give you more detail on what handle could have gone rogue.

Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.
Paresh Motiwala
Paresh Motiwala
SSC-Addicted
SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)SSC-Addicted (462 reputation)

Group: General Forum Members
Points: 462 Visits: 314
I have a similar case but the retention for the files is 14 days. The job once failed did not succeed at all.
I even copied one of the files for one of the databases manually, hoping that LogShipping would be smart to pick up from there on.



chandan_jha18
chandan_jha18
SSCrazy
SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)

Group: General Forum Members
Points: 2287 Visits: 2134
Paresh Motiwala (8/5/2015)
I have a similar case but the retention for the files is 14 days. The job once failed did not succeed at all.
I even copied one of the files for one of the databases manually, hoping that LogShipping would be smart to pick up from there on.


This is a pretty old thread. you should post a new thread instead.

When you say the job failed- Did you find out why it failed and which job actually failed. It could either be log backup job or copy-backup job or restore backup job.
Let us know where it is actually failing. First check the SQL log on secondary to see what was the last time the log backup got actually restored.

Also, I have to ask you to be a little extra careful. Relying on logshipping agent job alerts for issues is fine but for extra safety you can run a job at secondary server which scans the sql server log(information or error log) to see if a restore of log file has happened in the last 10 minutes or whatever. This way you will have a sureshot way of knowing if logs are actually being restored.

I had a one off case where we were using Redgate scripts for backups and even though the job was not sending any failure alerts but the logs were not being restored.

Cheers!!
Chandan Jha
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