Lost data on network write

During retrospect backup to a network drive I get the following

{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.

I'm running an updated version of 2003. Th LAN adapters are intel proset,
and show zero bad packets in either direction. The managed switch also shows
no problems. This is a sporadic error that occurs when storing large amounts
of data. No errors are generated on the target server (also 2003). All
dirvers are up to date.

Not even sure how to troubleshoot this one.

"Greydude" <(E-Mail Removed)> wrote in message
news:59D0317A-E9FF-4345-B79B-(E-Mail Removed)...
> During retrospect backup to a network drive I get the following
>
> {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.
>
> I'm running an updated version of 2003. Th LAN adapters are intel proset,
> and show zero bad packets in either direction. The managed switch also
> shows
> no problems. This is a sporadic error that occurs when storing large
> amounts
> of data. No errors are generated on the target server (also 2003). All
> dirvers are up to date.
>
> Not even sure how to troubleshoot this one.

Does Retrospect support backups to non-local media?

Are you using autosense or are your PC and server NICs using
specific/matching speed & duplex settings?

"Lanwench [MVP - Exchange]" wrote:

>
> "Greydude" <(E-Mail Removed)> wrote in message
> news:59D0317A-E9FF-4345-B79B-(E-Mail Removed)...
> > During retrospect backup to a network drive I get the following
> >
> > {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.
> >
> > I'm running an updated version of 2003. Th LAN adapters are intel proset,
> > and show zero bad packets in either direction. The managed switch also
> > shows
> > no problems. This is a sporadic error that occurs when storing large
> > amounts
> > of data. No errors are generated on the target server (also 2003). All
> > dirvers are up to date.
> >
> > Not even sure how to troubleshoot this one.
>
> Does Retrospect support backups to non-local media?
>
> Are you using autosense or are your PC and server NICs using
> specific/matching speed & duplex settings?
>
>
> Yes it does. It stores data in 614MB files. The problem seems to occur when it stores huge files.

Yes, I'm using autosensing. The Intel monitor shows a gigabit connection
which is correct.

In news:0BB2B46C-1D1D-4205-92D5-(E-Mail Removed),
Greydude <(E-Mail Removed)> typed:
> "Lanwench [MVP - Exchange]" wrote:
>
>>
>> "Greydude" <(E-Mail Removed)> wrote in message
>> news:59D0317A-E9FF-4345-B79B-(E-Mail Removed)...
>>> During retrospect backup to a network drive I get the following
>>>
>>> {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.
>>>
>>> I'm running an updated version of 2003. Th LAN adapters are intel
>>> proset, and show zero bad packets in either direction. The managed
>>> switch also shows
>>> no problems. This is a sporadic error that occurs when storing
>>> large amounts
>>> of data. No errors are generated on the target server (also 2003).
>>> All dirvers are up to date.
>>>
>>> Not even sure how to troubleshoot this one.
>>
>> Does Retrospect support backups to non-local media?


>>
>> Are you using autosense or are your PC and server NICs using
>> specific/matching speed & duplex settings?
>>
>>
>> Yes it does. It stores data in 614MB files. The problem seems to
>> occur when it stores huge files.

Can you reproduce the problem with, say, a similarly huge NTBackup job to a
file on a remote computer? I'd be amazed if this worked reliably and would
not care to try it myself....I suppose you could do a backup job to a local
file and try a robocopy job to the remote server.

>
> Yes, I'm using autosensing. The Intel monitor shows a gigabit
> connection which is correct.

I don't recommend autosense - I like to lock down all NICs, and even switch
ports, at a specific speed/duplex setting wherever possible.