Operating system error 64(指定的网络名不再可用。)

这两天数据库异地备份遇到如下错误消息：
BackupDiskFile::RequestDurableMedia:  failure on backup device '\\116.25.1403.4\F7ASRSBackup\F7ASRS_backup_201402251506.bak'. Operating system error 64(指定的网络名不再可用。).

环境：Windows Server 2003 Enterprise Edition SP1  +    SQL  Server  2005

注意：虽然报错，但是成功地创建了备份。网上看了很多帖子或博客，都没有真正解决问题，比较典型的介绍如下：

1、http://www.sqlservercentral.com/Forums/Topic356923-5-1.aspx

I have called Microsoft on this issue and found that the following does work

open regedit
navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\parameters
Create a New DWORD value with the name SessTimeout
the value to 360 keep it Hexadecimal
(This value might not work for your backup but it was high enough for mine. If this doesn't work increase the value and try again.)

I hope this helps.

Thanks,
kgerde

Edited: 8/28/2009 9:49:39 PM by kgerde

 

2、 http://social.technet.microsoft.com/Forums/windowsserver/en-US/8878da36-19af-410a-ae48-db1a87af741e/system-error-64-the-specified-network-name-is-no-longer-available?forum=windowsserver2008r2networking

I agree with Sainath,  Perform test that he had recommended.  The earlier version of Legacy OS such as Win XP or Server 2003 uses SMB1.  I had experienced in issue very similar recently.  Disabling SMB2 unfortunately didnt resolve the issue for me.  I am not saying you shouldnt attempt it, because it could be a valid resolution.  I had to "Maximize the throughput for File Sharing and Network Applications.  Pleas be sure the backup/export you registry keys prior to proceeding with any modifications. 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters\size

Your choices for this registry key are 1,2 and 3.

1 = Minimize Memory Used
2 = Balance
3 = Maximize Throughput for File Sharing and Maximize Throughput for Network Applications

Be sure to set this to (3). By default it is configured to 1.

I hope this helps,

Thank you,

Aaron Griffin

 

3、 服务（Computer Browser、server和workstation都要是启动状态）

诸如以上，我都尝试并验证过，但没能解决我的问题，后来只好采取本地备份+Copy备份到异地的策略。或许是旧版本固有的一些顽疾吧，我在SQL  Server 2008、 2008 R2及SQL Server 2012上都没遇过这个问题。因此，后面会升级到最新版本。