Operating System error 64 - workaround needed!

[icemel]

Hi,

We've been getting this error more and more:

"Operating system error 64(The specified network name is no longer available.)."

My preliminarly research on this problem indicated 2 possible causes:

1.) lack of SQL Server SP4 (yeah, yeah I know!)

2.) Writing to a network drive (we write to a backup device defined as: "\\ip.address\backup_directory")

But until we can get the service pack on, I need to find a workaround to this error.

I read somewhere that you can back up the file locally, then use XCOPY to copy the file to the standby server.

So my question is, will using XCOPY prevent the Operating System error 64 problem, and why?

THANKS

 

[icemel]

I forgot to mention, we get the error when doing a backup to a backup device on another server. The servers are on the same network, however.

 

[yelworcm]

First things I would check are if the share is there, and if the SQL Service (SQL Agent service, really) has permissions to write to it.

If you are really hard up for diskspace, you might be able to sleaze a demo copy of LiteSpeed from Imceda software. Or use WinZip via the command line to zip up backups.

 

[mrdenny]

If memory serves that error is that the server couldn't find the remote machine you are trying to backup to.

I'd recommend backing up locally then using robocopy (instead of xcopy) to copy/move the files to the remote server. Robocopy has the nice feature of auto-retrying if there is a problem with the file copy. It's also got a bunch of switches that can be used to do all sorts of cool stuff.

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com