KB labels


Ticket Product Version

Ticket Category

Ticket Assignee


Hot Fixes

Published Fixes
Your Arcserve Support User Profile
First Name:
Last Name:
email:
Phone:
Company:*
Customer Type:
Language:

Country:
Region:

Time zone:
Follow

arcserve-KB : Failed to write to virtual disk. System error=[The specified network name is no longer available. (64)].

Last Update: 2017-08-08 07:33:59 UTC

Error Message:

Failed to write to virtual disk. System error=[The specified network name is no longer available. (64)].

Description:

ARCserve D2D backup fails with the error 'Failed to write to virtual disk. System error=[The specified network name is no longer available. (64)].'

This is a network error. Error 64 means “The specified network name is no longer available. “.

Solution:

  1. Check if the latest version of ARCserve D2D and latest update is installed.
  2. Ensure that the Backup Destination (Windows Server or NAS device) is online and available during the backup window.
  3. Check if there are multiple ARCserve D2D or any other backup applications using the same device as the backup destination. If yes, schedule the backups to run at different times. Running more backups or merge at the same time might overload the Windows Server or NAS Device. 
  4. From ARCserve D2D r16.0 \ Update 7, merge can be scheduled to run during a specific window, so schedule them in such a way that multiple machines do not run merge at the same time.
  5. If the backup destination is on a windows share which is on a USB Disk, check the speed of the USB Device. Check if it is USB 2.0 or 3.0, performance also depends on the type of the USB Disk. If it is a USB 3.0 Disk, then make sure that it is connected to a USB 3.0 Controller otherwise there would a performance issue.
  6. Check if the backup destination (Windows Server or NAS device)  to see if there are any performance issues or system resource bottlenecks.
  7. Make sure that the network adapter drivers are up-to-date on the machine you are backing up and on the backup destination (Windows Server or NAS device).
  8. If the backup destination is on a Windows Share, make sure that it is up-to-date and is at the latest Service Pack Level.
  9. If the backup destination is on a NAS Device, make sure that the firmware is up-to-date. 
  10. Check the Windows Event Logs on the Source and the Destination(Windows Share) for any network or network adapter related errors.
  11. Stop the anti-virus scanning on the source and the backup destination server.
  12. To further isolate the problem, test the backups to a different network location on a different Windows Server or a NAS device. If the backups to a different backup destination works then, then it means that the problem is specific to a backup destination.
  13. Also run a ping test, run ping –t “IP Address of the Backup Destination” > c:\pingtest.txt. Check the output file to determine if there is any timeout and fix that.

More Information:

Tools that would help to determine the cause for the network problem:

Note:- Consult your Network Administrator or Microsoft Support for assistance in analyzing the network traces.

 -Use Microsoft Network Monitor or WireShark tool to capture network traces, analyzing the traces captured by these tools would help identifying the root cause.
Install it on the backup source and on the backup destination if it is a Windows Share. Start capturing the network traces  when the backups start and stop it once you get the Error 64.

WireShark

http://www.wireshark.org/download.html

Microsoft Network Monitor

http://www.microsoft.com/en-in/download/details.aspx?id=4865

Was this article helpful?
0 out of 1 found this helpful
Have more questions? Submit a request

Comments