Re: SQL Server Backup to UNC Path Failing
- From: "Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx>
- Date: Wed, 28 Nov 2007 13:39:55 -0500
Well I wouldn't say that is an official MS recommendation. While backing up to a local drive certainly is preferred for speed and performance reasons going to a UNC is necessary in many cases. There is nothing inherent in a stable network to prevent this from being reliable and happens every day. But I do agree that it is most likely due to network related issues. That may be the networks cards or anything in between. But from your error I would suspect the file server itself. It sounds like there is either a hardware issue or it simply can't keep up with the load.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Nick Padron" <NickPadron@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:6CBF498A-425E-4F80-8895-6766C034EC6F@xxxxxxxxxxxxxxxx
We looked at the packets and didn't see any errors or loss. At this time
Microsoft suggested that we increase the TCP delay timeout within the
registry of the affected servers. It seems that it is not reccommended by
Microsoft to perform UNC path backups but rather to the local drives of each
server. Silly but we are going to follow their reccomendation for now and see
what happens.
"Sean McCown" wrote:
Man, it sounds initially to me like you're having periodic network failure.
Litespeed can't recover from that. Can your guys guarantee you that the
network isn't burping while this is happening?
"Nick Padron" wrote:
> I am currently using LiteSpeed version 4.8.3.00025 to backup my sql > servers.
> Currently they are all setup to backup via unc to a central backup > server but
> over the past 3 to 5 months the backups have been failing.
>
> In the application log we see this:
> Operating system error 995(The I/O operation has been aborted because > of
> either a thread exit or an application request.).
>
> In the system log we see this:
> {Delayed Write Failed} Windows was unable to save all the data for the > file
> \Device\LanmanRedirector. The data has been lost. This error may be > caused by
> a failure of your computer hardware or network connection. Please try > to save
> this file elsewhere.
>
> We also have a call open to Microsoft and Quest (LiteSpeed) and > Microsoft
> and took one of the problematic servers and changed the backups to > point to
> local drives instead of the unc path. This seems to be working great > but is
> merely a work around and I still have 20 other servers that are still > using
> the unc method and experiencing intermittent failures. We also applied > the
> mrxsmb hot fix to address the delayed write failed error in the system > log
> and that didn’t help. I started looking around on message boards and > figured
> I would shout out for some help because I feel as though Microsoft and > Quest
> aren’t going to find a solution anytime soon. Has anyone else had this
> problem? Thanks.
>
.
- References:
- SQL Server Backup to UNC Path Failing
- From: Nick Padron
- SQL Server Backup to UNC Path Failing
- Prev by Date: Re: Will I be able to connect?
- Next by Date: problem to connect sql server 2005 from localhost (W2k3)
- Previous by thread: SQL Server Backup to UNC Path Failing
- Next by thread: How to tell sql server the maximum size my temptable will grow so that it does at most 1 memory allocation?
- Index(es):
Relevant Pages
|
Loading
