Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

Log Shipping copy job fails intermittently Expand / Collapse
Posted Monday, August 20, 2012 4:29 PM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Friday, July 25, 2014 2:47 PM
Points: 587, Visits: 1,998

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
Posted Monday, August 27, 2012 4:08 AM


Group: General Forum Members
Last Login: Monday, July 27, 2015 12:36 PM
Points: 470, Visits: 1,980
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.

Post #1350298
Posted Monday, August 27, 2012 7:35 AM



Group: General Forum Members
Last Login: Today @ 1:01 PM
Points: 6,283, Visits: 7,206
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

LiveJournal Blog:
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 »

Add to briefcase

Permissions Expand / Collapse