Thanks, Bob. Sound advice.
I did find the cause of the problem I was having. It was mostly
between my ears. Somewhere along the line a restore point was
established on the local D-drive. I cleared that, and I'm now
able to make good backups.
Flatus
On Sun, 05 Aug 2007 01:10:12 GMT, Bob Wilcox wrote in
news:OF4go1v1HHA.3640@TK2MSFTNGP06.phx.gbl:
> I had a similar error that went away if I disabled Symantec
> Antivirus and Firewall before running the backup.
>
> "Flatus Ohlfahrt" <Flatus@community.nospam> wrote in
> message
> news:Xns9982B2C5242D4FlatusOhlfahrtsNet@207.46.248.16...
>> Here is the error message from the Vista event log:
>>
>>
>>> The specified network name is no longer available.
>> (0x80070040)
>>>
>> 40000780E0040000EC06000008070000420ED1665C2BEE174B64529CB14
>> 610EA 71000000
>>>
>>> Binary data:
>>> In Words
>>> 0000: 80070040 000004E0 000006EC 00000708
>>> 0008: 66D10E42 17EE2B5C 9C52644B EA1046B1
>>> 0010: 00000071
>>>
>>> In Bytes
>>> 0000: 40 00 07 80 E0 04 00 00 @..?à...
>>> 0008: EC 06 00 00 08 07 00 00 ì.......
>>> 0010: 42 0E D1 66 5C 2B EE 17 B.Ñf\+î.
>>> 0018: 4B 64 52 9C B1 46 10 EA KdR?±F.ê
>>> 0020: 71 00 00 00 q...
>>
>>
>> System is a 4GB Ultimate x64 on a Gbit lan backing-up to
>> an SBS03 R2 Premium software-Raid5 volume. All shares
>> appear to be valid as do the permissions. There is much
>> free space on the backup volume.
>>
>> The x64 is behind two cascaded gigabit switches.
>>
>> There is no concurrent error in the server logs.
>>
>> Much of the data is backed-up before the failure occurs.
>>
>> The problem is consistently repeatable even when all other
>> load is removed from the backbone.
>>
>> Any help from those who have overcome this problem in the
>> past would be appreciated.
>>
>> Flatus
>>
>>
>
>
--
We fought hard for what we earned.
Tricare for Life is at:
http://www.tricareforlife.org
Tricare is at:
http://www.tricare.org