August 20, 2012 at 4:29 pm
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
August 27, 2012 at 4:08 am
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
August 27, 2012 at 7:35 am
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.
August 5, 2015 at 12:34 pm
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.
Paresh Motiwala Manager of Data Team, Big Data Enthusiast, ex DBA
August 5, 2015 at 9:54 pm
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
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply