The company I currently work for backups its SQL databases by
dumping them into a shared folder on nearby sysem. Once in a blue moon
the following error appears on the screen of the SQL server:
Windows - Delayed Write Failed
Windows was unable to save all the data for the file
\Device\LanmanRedirector\10.100.20.7\backup\logs\DB backup 4 hour cycle to remotesrv
storage4_200608150615.txt. 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.
There are other processes that talk to other shares (on the same drive
on the same remote system) and none of them gives me the above
error. What more both systems are on the same LAN and IP subnet that is
very lightly used. The network cables are all high grade CAT6
cable (machine cripmed). I'm not a windows/SQL
Administrator (Unix is my background), so if I'm asking the wrong
questions in the wrong forum please kindly redirect me to the right
forum.
Why does this error popup?
TIA
Paolo
One place you might try is to take a look at the Array Controller Read/Write Cache ratio on the target server. If the controller is set to 100% Read, this type of error could happen. You could also take a look at the array controller on the server initiating the backups. The controller should never be set to 100% Read, although even though it may be, it doesn't allow no Write caching. However, if there is too much data being written to the array and there isn't enough Write cache, you could experience the type of failures you are seeing. Also make sure there are no failed disks in the array. You may also want to make sure that all of the storage drivers are up to date as well.
No comments:
Post a Comment