| Author |
Topic |
|
JohnDeere
Posting Yak Master
191 Posts |
 Posted - 2003-05-21 : 07:48:12
|
| We backup our database (backup command) to local storage on the SQL Server via a scheduled SQL job. Another scheduled job copies the backup file to a another server(Tape Server) where the files are written to tape. As of yesterday the copy job started erroring on files that are > 2GB. The jobs will run about 4 minnutes and then return "The specified network device is no longer available". The transaction log backups and other small backup jobs copy to the tape server just fine. This is only happening on our SQL CLuster and only on large files. We have other SQL Servers that can copy large files to the tape server without any problems. In testing I have discovered that any type of large file copy from the cluster to the tape server fails (DOS Command line, Windows explorer). If I log on the the tape server and copy files from the cluster it works fine. I can also copy large files from the cluster to other servers. Just copying large files from the cluster to the tape server fails.All servers are Win2K SP2 and SQL2K SP3.I have reseaerched the error message but I found no articles that have pointed me to a fix.ThanksLance Harra |
|
|
franco
Constraint Violating Yak Guru
255 Posts |
Posted - 2003-05-21 : 08:24:18
|
| Have you checked event log for errors?It could be something related to SCSI or Fiber Channel device not be able to write.Franco |
 |
|
|
JohnDeere
Posting Yak Master
191 Posts |
Posted - 2003-05-21 : 08:53:42
|
| I have not found any errors in the application or system logs on either server. I have also checked the sql logs and I can not find an error in those logs either.Correction to 1st post. The servers are on Win2k SP3As of this morning another sql server is having trouble copying large files to the tape server.ThanksLance Harra |
|
|
|
franco
Constraint Violating Yak Guru
255 Posts |
|
|
izaltsman
A custom title
1139 Posts |
Posted - 2003-05-21 : 11:03:00
|
| When was the last time your tape server was rebooted? I've been having a similar problem here for some time now... Sometimes rebooting my target server appears to help. I might have other issues on the network though (like maxed out bandwidth for example...)Anyhow, if you find out the cause of you problems, please post here... I'll be sure to do the same if I think of something. |
|
|
|
JohnDeere
Posting Yak Master
191 Posts |
Posted - 2003-05-21 : 13:13:33
|
| We rebooted the tape server after yesterday after the discovery of the problem.When /if I get it resolved I will post the solutionLance Harra |
|
|
|
JohnDeere
Posting Yak Master
191 Posts |
Posted - 2003-05-21 : 13:16:58
|
| I think it is network related as well, I am not having much luck with the network guys though.I will try the suggections in the Q article and see what they tell me.ThanksLance Harra |
|
|
|
srf
Starting Member
42 Posts |
Posted - 2003-05-21 : 18:19:05
|
| Also see if you're using NTFS compression at either end. With any file over a gig this is a great way to get that error. |
|
|
|
JohnDeere
Posting Yak Master
191 Posts |
Posted - 2003-05-23 : 08:45:16
|
| We are not using any NTFS compresssion.I did find the following Qarticle the describe flaws in the buffered IO system Q259837 You may not be able to Copy Large Files on Computers That are Running Windows NT 4.0 or Windows 2000Supposedly it is fixed in SP3.Lance Harra |
|
|
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
Posted - 2003-05-23 : 10:22:30
|
| We have had a "similar" problem in our environment, although with significantly bigger files ( 70 gb +), where the copy fails and specifies "insufficient resources available". A SOURCE SERVER re-boot has always resolved issue, which fortunately occur's only on weekends, when we copy the full backup. We hence use this to get a weekly reboot, just for server health . Supposed to have been solved by Win 2K SP3, but to no avail...*#&#* *#&#* *#&#* *#&#* Chaos, Disorder and Panic ... my work is done here! |
|
|
|
srf
Starting Member
42 Posts |
Posted - 2003-05-23 : 10:52:09
|
| I've gotten the resources error too when working with 70 gig backup files. But that too was because of NTFS compression, going uncompressed made the problem go away... but that was a tight fit.BTW, the latter error was on Windows 2003.Edited by - srf on 05/23/2003 10:53:13 |
|
|
|
JohnDeere
Posting Yak Master
191 Posts |
Posted - 2003-05-27 : 08:55:08
|
| The problem we are experiencing does not seem to be related to the source. I have tried several source servers and the problem still occurs when copying to the tape server. We are going to reapply SP3 to the tape server and see if that solves the problem.Lance Harra |
|
|
|
JohnDeere
Posting Yak Master
191 Posts |
Posted - 2003-05-28 : 09:41:11
|
| Reapplied the service pack and that made no difference.Rebuilt the entire machine and that made no difference.In desperation changed the ip address from static to DHCP problem seems to be solved. Now we are investigating what is set different between DHCP and Static ip addresses.Lance Harra |
|
|
|
|
Copy ing Backup Files Fails