A nonrecoverable I/O error occurred on file

  • Hi All

    Please assist me regarding this problem.One database does not want to backup it shows a strange error.please assist A.S.A.P im in trouble,

    Executing the query "BACKUP DATABASE [DBName] TO DISK = N'C:\\Prog..." failed with the following error: "A nonrecoverable I/O error occurred on file "C:\\Program Files\\Microsoft SQL Server\\MSSQL10.MSSQLSERVER\\MSSQL\\Backup\\DBName\\DBName_backup_2010_12_12_202529_5620562.bak:" 112(failed to retrieve text for this error. Reason: 15100).

    BACKUP DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly

  • Hi!

    Have you tried DBCC CHECKDB? If so, any errors?

    __________________________
    Allzu viel ist ungesund...

  • Hi

    I have tried DBCC Check DB and there are no errors,im running out of ideas ,Any help please.

  • Hi!

    A few things you could try then: check disk space on drive, try to change the path to another drive (if possible). Also check logs to find out more details and post it if you find something else.

    __________________________
    Allzu viel ist ungesund...

  • i checked the Disk space and it has a lot of free space,the database that im trying to backup is 69GB and the free space on disk is 560GB.But below are some of the details i got from event viewer.

    Extend Disk Backup: failure on backup device 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Backup\DBNAME\DBnamebakup_2010_12_12_202529_5620562.bak'. Operating system error 112(failed to retrieve text for this error. Reason: 15100).

  • Is this error occuring during a job or maintenance plan? Have you attempted to run the command via query?

    Chris Powell

    George: You're kidding.
    Elroy: Nope.
    George: Then lie to me and say you're kidding.

  • Have you checked the Windows server logs for anything odd during the backup?

    - 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

  • Just a thought.....are you backing up to an NTFS 'compressed' directory? If so, you'll have problems with files larger than ~30GB

    Cheers

  • If you are using Maintenance Plan to take the backups, then the combination of the Maintenance Plan logs and Application log should help you to find the root cause of the problem.

    Thank You,

    Best Regards,

    SQLBuddy

  • Hi Guys

    Thanx for your responce.yes iam using maintanance plans to backup and i tried to use a query to backup but also it failed with the same error,i also tried using stored proc to backup but it also failed with the same error,i will check the disk if they are compressed.

  • Hi Guys

    i have found the root cause of the problem,apparently the size of tables grew from 39GB to 380GB in one day and im busy trying to find the out how to sort this mess out,any suggestion will appreciate it ,thanks.

  • Hi Guys

    The problem was caused by the table in the database that grew in one day from 39GB to 380GB,this was preventing the backup to go through and making it to fail,Please assist guys as i fail to understnad why this table grew like this and where to start in solving this issue.i will appritiate your help,thanks.

  • We can't really help you with this. The table grew because somebody put a lot of data in it. Do you know how many rows it had before? If so, you can look at whether this is because lots of rows were added, or existing rows were updated with data that takes up more space. What are the data types of the column in the table?

    John

  • As stated, we can't advise why your database (When you say 'tables' I presume you mean 'database'?).

    This is something you need to look into. Look for date columns that may give you some pointers as to when a COLLOSSAL amount of data was put into your DB.

    Take it you don't have monitoring on DB growth/drive space? Now may be the time to look into that.

    Carlton

  • Yes it used to work and now its no longer working,it used to backup,but because the tables have grown too high,the also the backup file grew.so the database now its at the size of 600GB and our Backup disk is 500GB.before this table grew exponatially like this we used to backup easily on it.so now it cant.you are absolutely correct its SQL SERVER 2008

Viewing 15 posts - 1 through 15 (of 22 total)

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