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.