October 21, 2009 at 8:23 am
Hi,
I am backing up several databases from my MS SQL 2005 SP3 Ent Server to a network share. Some of the databases backup to success, but others (seems like the larger ones) fail with the following:
*****
Failed:(-1073548784) Executing the query "BACKUP DATABASE [Database] TO DISK = N'\\\\192.168.1.100\\DB_Backups\\Database_backup.bak' WITH NOFORMAT, NOINIT, NAME = N'Database_backup_20091020131441', SKIP, REWIND, NOUNLOAD, STATS = 10
" failed with the following error: "A nonrecoverable I/O error occurred on file "\\\\192.168.1.100\\DB_Backups\\Database_backup.bak" 64(The specified network name is no longer available.).
BACKUP DATABASE is terminating abnormally.
*****
Any suggestions as to why this is occuring? If I backup using the same maintenance plan, but change to a local disk, it works fine.
The sql server is on Windows Server 2003 SP2 Ent 64bit on a passive-passive cluster, and the backup is on a Windows Server 2003 SP2 Ent 32bit.
October 21, 2009 at 8:31 am
Network glitch. Since you're restoring from a network drive, all you need is a moment where the backup isn't accessible and the restore will fail. Copy the file locally, then restore. It'll ba faster and there's less chance of problems.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 21, 2009 at 9:26 am
Hi Gail,
thank you for your suggestion. It's a backup I'm doing by the way. Yes, we are thinking of network problems, and are exploring ways to prove this, however, other databases are backing up fine to teh same network share at around the same time of the day!
Thanks,
Tim
October 21, 2009 at 9:36 am
The problem with SQL and networks is that it doesn't handle any delays well. A file copy will retry and work through small glitches. SQL doesn't because the delays can impact server performance.
You're much better off running backups locally and then copying them across the network.
October 21, 2009 at 9:46 am
Timothy Patihk (10/21/2009)
Yes, we are thinking of network problems, and are exploring ways to prove this
The proof is in the error message - "The specified network name is no longer available."
however, other databases are backing up fine to teh same network share at around the same time of the day!
Random network glitches. The bigger the database, the more the chance that it will be affected.
Backup local, copy remote.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply