Windows Delayed write error when backing up to network share



  • 1. MS06-061 Update
    Do I need to apply MS06-061 update to our SQL Servers ?. Our SQL Servers have no internet access and are behind a firewall. Is this an immediate threat to any SQL Servers ? Thanks.
  • 2. Question on Connectivity tools for SQL 2000 and SQL 2005
    Question on just connectivity tools for SQL 2000 and SQL 2005 We are in the process of doing a inplace-upgrade of our SQL Server 2000 to SQL Server 2005. Currently all of the client computers have only the connectivity tools from SQL 2000 installed in them. Is it necessary to upgrade all the client machines with new SQL 2005 connectivity tools? Any advice in this regard will be greatly appreciated. Question on Client tools for SQL 2000 and SQL 2005 The other question I have is I have a unique client that has SQL 2000 Client tools installed, I am planning to also install the SQL 2005 Client tools, in this scenario when the Client connects to the Server which client setting does it take. So for instance if in the SQL Serever 2000 Network Client utility if I have only tcp_ip enabled as the network protocol and on SQL 2005 if I have only Namedpipes enabled, how does SQL Server figure out which setting should it look at? Do I need to keep them consistent for both? Thanks
  • 3. Monitor CPU Usage by Query?
    We are currently running MS SQL 8.0 on Windows 2003. I've been tasked setting up a monitor that can identify queries that are causing CPU spikes. Does anyone have any suggestions about going about this? I'm at a complete loss.

Windows Delayed write error when backing up to network share

Postby a21rcmF1c2Uy » Sat, 12 Feb 2005 04:41:11 GMT

I'm running SQLServer2000 SP4 on two separate servers. The problem I'm 
running into is that when I schedule a database backup either through 
Maintenance Plans or manually through Enterprise Manager the backup fails 
with the error:
 "Windows-Delayed Write Error. Windows was unable to save all the data for 
the file \Device\LanmanRedirector\<unc path>. 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". 

I'm backing up to a NAS and using a UNC path to get there. I can copy a file 
of the same size through explorer with no problem, it's only when SQL tries 
to backup to the network that the error comes up.

In researching this, I've found several articles pointing to various causes. 
What I've checked so far includes turning off the write cache setting for the 
drives in Device Manager|Disks and changing the registry entry 
from 1 to 0 to shut off SMB signing. Nothing has resolved the issue as yet.

This problem us also accompanied by System event log error MrxSmb 50 and 
several MSSQLServer errors in the application log that all point to write 
errors on the destination drive or losing connection with the destination, 
but the network connection is fine.

Any ideas would be appreciated.


Re: Windows Delayed write error when backing up to network share

Postby pdxJaxon » Sat, 12 Feb 2005 07:37:08 GMT

Not recommended backing up to a network drive or share.

can you backup locally and then copy the file up ?

This is what I had to do at a previous job in Orlando.

Greg Jackson
Portland, OR 

Re: Windows Delayed write error when backing up to network share

Postby a21rcmF1c2Uy » Sat, 12 Feb 2005 07:59:03 GMT

I need to be able to backup to a network device as the local disks that are 
of enough size are clustered and inaccessible to anything except the active 
node. Backing up to a network share cuts the entire time it takes to restore 
from tape out of the loop. This is critical for DR purposes. 

Besides the issue isn't whether it's recommended, but what is causing the 

Re: Windows Delayed write error when backing up to network share

Postby Mike Epprecht (SQL MVP) » Sat, 12 Feb 2005 08:08:36 GMT


In good hardware, with good available bandwidth, I have never had any
As an exercise, copy a big (10Gb+) file over the network from your server to
the destination server. Use Explorer or XCOPY. See it this works. now try
copying 2 versions of the file at the same time to the destination. If both
are successful, you should not have a problem.

Networks are un-reliable.

If it is so critical to DR, any reason you are running in a configuration
that is not fully supported?

Have a look at
 http://www.**--****.com/ ;en-us;304261 to see what
MS thinks how you need to do it.

Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland


MVP Program:  http://www.**--****.com/ 

Blog:  http://www.**--****.com/ 


Similar Threads:

1.Potential issues with backing up to a network share


What potential issues can you think of or have run into when making 
transaction log backups into a single file on a network share. The 
MSSQLSERVER service is running under a domain user account, which has 
apropriate permissions on the shared folder. The backup is made from a 
database in an MS SQL Server 2000 SP3 on an MS Windows Server 2003 SP1 and 
the file is stored on an MS Windows 2000 Server SP4.

2.Backing up to a network share from SQL Server 2005


I'm trying to back my database up to a network share. Using the same account 
that I'm logged into SQL Server Management Studio with, I'm able to add and 
delete files on the network share just fine. When I try to do a backup to the 
same location, I get this message:

System.Data.SqlClient.SqlError: Cannot open backup device 
'\\dc01\Backup\Database\fogbugz.bak'. Operating system error 5(Access is 
denied.). (Microsoft.SqlServer.Smo)

Does anyone know why this might be or how best to troubleshoot it?


3.Simulating of network delays and limited network bandwidth

I want to try to simulate transaction replication with limited network 
bandwidth and network delays conditions. I have program which do it for 
specified ports. Is it possible to configure replication to use proxy to be 
able to use the program.? Which ports are used by repliation?

4.write ups / class notes on sql server 2000?

Hi.  I'm starting to teach SQL Server at a community college -- does 
anyone have any content, that they're willing to share???

Thanks in advance.

Alex Ivascu

5.Enabling Transaction Log Back Ups

if the recovery option is SIMPLE then you can't do a trans log backup.

"ann" < XXXX@XXXXX.COM > wrote in message
news:0bda01c37e0a$9c83ec50$ XXXX@XXXXX.COM ...
> I have set up maintenance plan on sql server 2000.  The
> dbs back up fine, but the transaction logs error out.  I
> tried manually to to evoke a backup in the dialog box, but
> the option to check Transaction Logs is greyed out.
> I am in as "sa" account.  I thuought this might be the
> problem, so I created a new account enabling all
> permissions.  However I cannot find a way to "log in" to
> the sql server as the new account.  The server
> automaticall starts up every morning under the sa account
> as it feeds an automated dialer.
> mAYBE iM GOING DOWN THE wrong path.
> Help
> thanks
> Ann

6. Question about Back ups

7. Full back ups and transaction logs

8. Shared Memory Protocol and Gerenal Network Errors for local jobs



Who is online

Users browsing this forum: No registered users and 63 guest