November 27, 2007 at 6:11 pm
We are testing a clustered server set up to put into production early next year. I have been running backup scripts to as part of the test. The new cluster will transition us to SQL2005. I up backing up this new server to disk on the network SANS. Since the data base went over 1 Gig, I keep getting the error:
A nonrecoverable I/O error occurred on file "\\server1\DFS-Root\Folder\Folder\Folder\Dev5DailyFull.bak:" 64(The specified network name is no longer available.).
The data is transferred on our IntraNet.
I created a Backupdevice, Dev5DailyFull and a job in Sql Agent to run the scripts. I’ve verified my network path. After each run, the .bak file shows up in the proper folder with the current size of the data base. The Differential and Transaction log backups all write to the same location, using the same path and they excute with no errors.
Any ideas on what is happening? Below is the backup script and the results.
BACKUP DATABASE [Dev5] TO [Dev5DailyFull] WITH RETAINDAYS = 1, NOFORMAT, INIT, SKIP,
NAME = N'Dev5-Full Database Backup', NOREWIND, NOUNLOAD, STATS = 10
GO
declare @backupSetId as int
select @backupSetId = position from msdb..backupset
where database_name=N'Dev5'
and backup_set_id=(select max(backup_set_id) from msdb..backupset
where database_name=N'Dev5' )
if @backupSetId is null begin raiserror(N'Verify failed. Backup information for database ''Dev5'' not found.', 16, 1) end
RESTORE VERIFYONLY FROM [Dev5DailyFull]
WITH FILE = @backupSetId, NOUNLOAD, NOREWIND
----Results--------------
10 percent processed.
20 percent processed.
30 percent processed.
40 percent processed.
50 percent processed.
60 percent processed.
70 percent processed.
80 percent processed.
90 percent processed.
Processed 224784 pages for database 'Dev5', file 'Test5_Data' on file 1.
100 percent processed.
Processed 1 pages for database 'Dev5', file 'Test5_Log' on file 1.
Msg 3271, Level 16, State 1, Line 1 A nonrecoverable I/O error occurred on file "\\server1\DFS-Root\Folder\Folder\Folder\Dev5FullDaily.bak:" 64(The specified network name is no longer available.). [SQLSTATE 42000]
Msg 3013, Level 16, State 1, Line 1 BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000]
Greg
November 27, 2007 at 10:18 pm
The backup process is very intolerant of any delays or errors. It sounds like you either had a network (SAN network) hookup or the file is corrupt. I don't use the backup devices, only disk files so I get new blocks on disk every time.
November 28, 2007 at 12:29 pm
Steve,
That looks like a 914. 4 or 6? They are great cars to 'slide around the corner' specially in the snow.
You said, "I don't use the backup devices, only disk files so I get new blocks on disk every time"
By that I take it you are saying Backup Database [Dev5] to Disk = n'\\server\folder\file.
I only retain the .bak one day. The IT department backs to tape at night. Then I backup to the same path\file the next day. Will it write to new blocks? I thought it would be overwriting the current blocks.
Greg
November 29, 2007 at 5:01 am
Similar bug is there in SQL Server 2000 for SQLMaint.exe.
Check this link :
http://support.microsoft.com/kb/303292/en-us
"More Green More Oxygen !! Plant a tree today"
December 4, 2007 at 10:58 am
Just to follow up on this... I'm 99.9% sure this is a network/SANS issue. I've changed my backup scripts to write to multiple files. As long as I keep it under 1GB everything goes smoothly with no errors. I've asked the IT dept. to check into this but I'm not holding my breath they will resolve it soon. So for now mulitple files....
Greg
December 4, 2007 at 11:22 am
Be sure you document things well so others are aware they need multiple files to restore.
The 914 is great, and up for sale! First $3k or better gets it.
December 7, 2007 at 9:50 am
You mught want to try a drop'n'drag file copy of 1 Gb file(s) to see if you get the same error. We had a situation like this a while back and it turned out to be a bad network cable.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
December 13, 2007 at 6:32 pm
Are you able to backup the database locally? In my company's environment, we do a full backup of our datawarehouse to a network drive and it's around 260GB.
December 14, 2007 at 11:03 am
I am able to back up locally with no problem. I've consider backing up locally and copying to the network SANS but seems like unnecessary duplication not to mention the time needed to copying the file over. What make no sense to me is, this is comparatively, a small file compared to what some people are copying. (260G vs 2G). I was going to try Rudy's idea this weekend when I get a minute.
Greg
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply