MS SQL database backup failed for "nonrecoverable I/O error occurred on file

I have a MS database server hosting over ten databases. We have setup database backup for all the databases to a remote share drive. For some reason, two of the backups fails with the following error message:

"TITLE: Microsoft SQL Server Management Studio

Backup failed for Server 'SUMMERLAND'.  (Microsoft.SqlServer.Smo)

For help, click:


System.Data.SqlClient.SqlError: A nonrecoverable I/O error occurred on file "\\LACSQLREPPRD1\backup\SUMMERLAND\Full\WSS_Search_SUMMERLAND_New\SUMMERLAND_NEW.bak:" 64(The specified network name is no longer available.). (Microsoft.SqlServer.Smo)

For help, click:



I did some test as below:

1. the database is running correctly without any error.

2. If we choose to backup to the local drive, it finishes successfully without any error.

3. If we choose to save the backup on the remote server, it fails with the error message aboe.

4. We checked the permission setup on the share drive server, all permissions look fine to me.

Please give me some help for resolving it.

Jason YuAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Anoo S PillaiSenior ConsultantCommented:
Windows Error 64 is normally related to network unavailability at the time. It can happen because of network congestion too.

Try the following three options -  
1) Try a rerun, If the error was because of any network congestion at the time of backup rerun could succeed.
2) If you are a sysadmin, try accessing the folder from within SQL server using xp_cmdshell , a simple dir command or a copy command would be enough. In this way we can ensure that the folder is accessible
3) Check under which credential your backup job is running. Double check the privilege of that account.
Vitor MontalvãoMSSQL Senior EngineerCommented:
This path exists: "\\LACSQLREPPRD1\backup\SUMMERLAND\Full\WSS_Search_SUMMERLAND_New" ?
If affirmative, the SQL Server or SQL Server Agent accounts has read and write permissions on it?
Jason YuAuthor Commented:
yes, it has. In fact, everytime the backup archive file was recreated and is valid. We even tested restore the database from the archive and it was succssful.

My coworker said it is caused by network latency, I was wondering if there is a way to check it?

Active Protection takes the fight to cryptojacking

While there were several headline-grabbing ransomware attacks during in 2017, another big threat started appearing at the same time that didn’t get the same coverage – illicit cryptomining.

Jason YuAuthor Commented:
I added another disk from a new san, it still does the same. it still gives the same error prompt. Is it because my storage device is slow or my network?

Please advise.
Vitor MontalvãoMSSQL Senior EngineerCommented:
There's a known issue with Symantec product that can throw that error.
Can you confirm if is your case?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jason YuAuthor Commented:
got it, it's the cause, thank you very much.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.