"The specified network name is no longer available" – SQL Backup problem solved!

A few of you may (or may not) know that my colleagues and I are using Ola Hallengren’s famous Maintenance Solution. If you never heard of it before then please take a look: http://ola.hallengren.com/

For native SQL backups we have no dedicated disk space on our database servers. Instead we´re running native backups over the network and place them on a UNC path. I know that it is probably not best practice but it fits for our environment (or to quote André Kamman (blog | twitter): “It works for me!”) very well.

It is Murphy´s law that sometimes things can go wrong. So it happened on a few machines that the backup was created but finished with an error:

The operating system returned the error ’64(The specified network name is no longer available.)‘ while attempting ‚FlushFileBuffers‘ on ‚\\OurBackupServer\ourshare$\OurServer\OurDatabase\FULL\ OurServer_OurDatabase_FULL_20111021_041523.bak‘

So we did a little bit of research and even talked to Ola Hallengren when we visited SQLBits 9. His assumption was some kind of timeout.

Since this error only occurred on some test machines we didn´t spent too much time investigating / solving the issue (we could live with it) until it happened also in a productive environment.

Then we came across a msdn forum entry (take a look here) and tried the mentioned solution to create a DWORD with name ‘Sesstimeout’ and value 360 in  HKLM\SYSTEM\CurrentControlSet\Services\lanmanworkstation\parameters.

And that was the solution. Since we´ve modified the registry on the  involved SQL Servers the backups running fine without any issues.

Advertisements

Über Dirk Hondong

A MS server and ms sql server admin guy from germany. want to improve my skills a little bit, sharing my daily experience
Dieser Beitrag wurde unter Maintenance, SQL Server, SQL Server Administration abgelegt und mit , , verschlagwortet. Setze ein Lesezeichen auf den Permalink.

10 Antworten zu "The specified network name is no longer available" – SQL Backup problem solved!

  1. Peter schreibt:

    Hi, You helped me a lot with your article. I had backup issue and this timeout changement solved it. Thanks a lot, Peter

  2. Ole Mejdell schreibt:

    Hi Peter,
    Is a restart of the server necessary? Because it didn’t solve the problem for me after the regedit change.

    regards Ole

  3. Girish schreibt:

    I too was facing the same issue. And the above fix resolved the issue. Just to note, no reboot of server or SQL service was needed.

    Thank you very much.

    Girish

  4. Glen Boonzaier schreibt:

    Would that be a DWORD (32-bit) or DWORD (64-bit)?
    When setting the value, should it be Base Hexidecimal or Decimal?

    • Dirk Hondong schreibt:

      Hi Glen,

      good question. I can’t remember and have to double check on the machine where I have made the change.
      But I think it was just a 32bit Dword and decimal value

  5. tommgunn schreibt:

    Hi,
    Should this change be made on the source machine or the destination server?

Kommentar verfassen

Trage deine Daten unten ein oder klicke ein Icon um dich einzuloggen:

WordPress.com-Logo

Du kommentierst mit Deinem WordPress.com-Konto. Abmelden / Ändern )

Twitter-Bild

Du kommentierst mit Deinem Twitter-Konto. Abmelden / Ändern )

Facebook-Foto

Du kommentierst mit Deinem Facebook-Konto. Abmelden / Ändern )

Google+ Foto

Du kommentierst mit Deinem Google+-Konto. Abmelden / Ändern )

Verbinde mit %s