Log Shipping copy job fails intermittently

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2008 » SQL Server 2008 High Availability » Log Shipping copy job fails intermittently

Log Shipping copy job fails intermittently

Rate Topic

Display Mode

Topic Options

Author

Message

Mani-584606

Posted Monday, August 20, 2012 4:29 PM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Wednesday, April 24, 2013 1:28 PM
Points: 535, Visits: 1,797

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

Post #1347503

chandan_jha18

Posted Monday, August 27, 2012 4:08 AM

SSC-Addicted

Group: General Forum Members
Last Login: Today @ 3:04 AM
Points: 412, Visits: 1,672

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

Post #1350298

Brandie Tarvin

Posted Monday, August 27, 2012 7:35 AM

SSCertifiable

Group: General Forum Members
Last Login: Today @ 6:45 AM
Points: 6,664, Visits: 5,689

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 Administrator, MCDBA, MCSA

Webpage: http://www.BrandieTarvin.net
LiveJournal Blog: http://brandietarvin.livejournal.com/
On LinkedIn!, Google+, and Twitter.

Freelance Writer: Shadowrun
Latchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

Post #1350382

« Prev Topic | Next Topic »

Permissions