Nonrecoverable I/O error occured on file - sql server 2000 backup error

Question

Nonrecoverable I/O error occured on file - sql server 2000 backup error

solomon.jernas

Hall of Fame

Points: 3680
More actions
July 14, 2011 at 4:23 am

#145789

Hi,
Someone help for me..
I faced the problem in production server , because the full backup has been faild. so i ran manulally
and gettting error:
"Nonrecoverable I/O error occured on file 'D:\mssql\data\custmom.mdf' backup database terminating abnormally "
Please help me..
Thaks
Jerry
July 15, 2011 at 3:49 am

This was removed by the editor as SPAM

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

muthukkumaran Kaliyamoorthy SSCoach Points: 19026 More actions · Answer 1

solomon.jernas (7/14/2011)
Hi,
Someone help for me..
I faced the problem in production server , because the full backup has been faild. so i ran manulally
and gettting error:
"Nonrecoverable I/O error occured on file 'D:\mssql\data\custmom.mdf' backup database terminating abnormally "
Please help me..
Thaks
Jerry

Run a checkDB and post the results.

What version is it?

Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/

GSquared SSC Guru Points: 260824 More actions · Answer 2

Is the drive the backup is being written to full?

- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

solomon.jernas Hall of Fame Points: 3680 More actions · Answer 3

I ran the Dbcc chekcdb .. getting no errors..

sql server 2000 version

Jim Murphy SSCertifiable Points: 6263 More actions · Answer 4

solomon.jernas (7/14/2011)
I ran the Dbcc chekcdb .. getting no errors..
sql server 2000 version

SQL 2000 questions should have been posted in a SQL 2000 forum, not 2005. Also, this sounds more like a data corruption problem than an Administration problem and so should have been posted in the SQL 2000 Data Corruption forum here: http://www.sqlservercentral.com/Forums/Forum265-1.aspx

As for the error: hmmm. Checkdb reads all data pages for non-disabled indexes, and the active data pages are reported as ok. Checkdb does not check the log file, but the error is reported in the data file, not the log. Therefore, I'm thinking like GSquared and you should check your backup destination, disk space or bad sectors. Perhaps backup to a different drive than you are now to see if that works, or you have a disk error under a disabled index.

Is this a native SQL server backup or a 3rd party tool? Also, backing up to tape or disk? Also, do a checkdb on the master database too, and use WITH NO_INFOMSGS with checkdb.

Assuming the above is normal, it looks to me like one of 4 possible issues:

1) The IO problem in intermittent. The drive or controller may be about to completely fail.

2) The problem is in the destination location and is being falsely reported to the data file. Backup to another place.

3) The problem is in the data file where a disabled index is sitting. Disabled indexes are not checked. Enable all disabled indexes after saving off their names so you can disable them again afterward.

4) The problem is in the transaction log, which is sort-of/partially backed up with a full backup, and the error is being falsely attributed to the data file. Don't want to quickly recommend anything for this unless it is the likely culprit due to the risk of causing more problems than fixing.

Jim Murphy
http://www.sqlwatchmen.com
@SQLMurph

solomon.jernas Hall of Fame Points: 3680 More actions · Answer 5

Thank you.. not enough memory to run the backup..

i wil change to os memory settings.