Ready to prevent the next vendor outage? Learn more
OPERATIONAL DEFECT DATABASE
...
...
When accessing backup files on a CIFS (SMB) repository, Veeam Backup & Replication reports either of the following errors: The specified network name is no longer available. (code 59, 0x8007003B) An unexpected network error occurred. (code 64, 0x80070040) Veeam Backup & Replication uses SMB connections for backup repositories, guest processing, and when first adding a Windows server to the Backup Infrastructure. This KB only addresses error messages that occur in the context of a backup file path, such as: The specified network name is no longer available. Failed to read data from the file [\\10.0.0.81\backups\SQL VM New\SQL VM New2015-09-23T200441.vbk]. Note: If the failure is occurring in a tape job and no UNC path is specified in the error message, please contact Veeam Support.
These error messages are passed directly from Microsoft Windows and indicate that the OS has detected a failure of the connection between the repository gateway (acting as Server Message Block client) and the SMB server (typically a NAS appliance).
Common Workarounds If the SMB share is located on a Windows machine, try creating a Windows repository using that machine instead of a CIFS (SMB) repository. Reboot both the SMB client machine (repository gateway) and the SMB server (NAS). If other storage is available, try writing the backup to the other storage to verify the problem and as a temporary workaround. If a NAS provides the SMB share, consider configuring NFS and connecting to the storage as an NFS repository. Writing backup files to SMB shares over a slow or unreliable network, such as a WAN connection, is not recommended. Deploy a gateway server with a fast (Ethernet 100Mbps+) connection to the share. To rule out interference from a firewall, temporarily disable any software firewalls (including certain antivirus products) on the SMB client or server and any hardware firewalls between them. Some firewalls having intrusion protection or deep packet inspection may interfere with connections due to errant detections of data blocks that match heuristic policies within the backup data stream.