Backup fails - Network name no longer available

Thread needs solution
supercooper
Beginner
Posts: 3
Comments: 2

Backup fails to RDX (over network) from one server on LAN - others appear to backup without issue.
The jobs aren't overlapping, as is the cause of many issues with RDX backups due to throughput, but the following error is consistently logged (being an excerpt, given this seems most relevant):

Write error. Error code: 0x70004 Tag: 0x9D2DE1F088CBC4EC Error occurred while writing the file. Error code: 0x40003 function = "FlushFileBuffers" Tag: 0x7CEB2CDC9FB12065 The specified network name is no longer available Error code: 0xFFF0 code = 2,147,942,464 (0x80070040) Tag: 0xBD28FDBD64EDB8BC" line_tag="0xA164035B3FF39281" />

The product has been uninstalled and reinstalled (with cleanup and reboots, etc in between) but the issue remains.

Any help would be appreciated.

Mon, 02/06/2012 - 12:01
0 Users found this helpful
Yana
Forum Star
Posts: 24
Comments: 3268

Hello Supercooper,

Thank you for reporting about the issue.

Normally this error means that the connection to the backup location is not stable, or the credentials are incorrect. I would strongly recommend to run network tests first of all.

If the problem remains please gather and send us the output of Wireshark logs and Acronis info. These logs might show us the cause of the problem.

Let us know if you have any questions or concern, we will be glad to help.

Thank you.

Tue, 02/07/2012 - 00:48