SQL Server Performance Forum – Threads Archive

Backup failing

We SQL server 2005 server, Our database size is around 180 gb. We backup this database on Local drive, however sometime out of blue this backup job fails with below mentioned error message TCP Provider: The specified network name is no longer available. [SQLSTATE 08S01] (Error 64) Communication link failure [SQLSTATE 08S01] (Error 64). The step failed. Now, this is backed up on local drive, and we have done monitorning on this disc and as such there are no errors, we have checked for evenviewer and windows log and there are no errors relating to disk errors or link faliure. Does anybody has clues why the backup fail, even when they are copied on to local drive.

---

I know you said drive is local…can you make sure once again the drive is not mapped drive…
Is it SAN drive or SCSI drive?
Run the check disk…
MohammedU.
Moderator
SQL-Server-Performance.com All postings are provided “AS IS” with no warranties for accuracy.

---

Thanks Mohammed, its definately local drive and Its a SAN drive. We have executed check disk and no errors were found.

---

Check with SAN egineers…it could be SAN issue, you may not see in through windows… MohammedU.
Moderator
SQL-Server-Performance.com All postings are provided “AS IS” with no warranties for accuracy.

---

I have checked and confirmed with SAN engineers and they confirmed that its not SAN issue

---

Hi,
Could you look more into the Activity if their is a Network Latency during the Period or some other activities that won’t let it backup!!!
Hemantgiri S. Goswami
MS SQL Server MVP
————————-
"Humans don’t have Caliber to PASS TIME , Time it self Pass or Fail Humans" – by Hemantgiri S. Goswami http://hemantgirisgoswami.blogspot.com

---

Its active disc and we have monitored the network on this in night and couldn’t fnd anything suspicious which could point to network issue on this server.

---

If this is failing on day to day basis then you have to monitor the event using profiler & performance monitor for system resource usage. If intermittent then ensure there are no other jobs clashing at the same time. Are there any recent changes to the infrastructure or SQL server?
Any changes to the database recovery models?
Any changes to the hardware or any firmware update?
Check permissions for SQL server services too. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.

---

]]>