A Nonrecoverable I/o Error Occurred On File Reason 15105
Contents |
from being out
A Nonrecoverable I/o Error Occurred On File 1117
on-site. © Blackforce February 23, 2014 15105 Database Error 15105 nonrecoverable Space sql SQL
Operating System Error 112(failed To Retrieve Text For This Error. Reason 15105)
Backup Failed - Error 15105 - A nonrecoverable I/O error occurred When trying to do a backup of a SQL Database in SQL Server Management Studio you might get the nonrecoverable i/o error occurred on file mdf error :- Backup failed for Server 'SERVERNAME\INSTANCE' (Microsoft.SQLServer.SmoExtended) System.Data.SQLClient.SqlError: A nonrecoverable I/O error occurred on file "LOCATION\DATABASE:" 112(failed to retrieve text for this error. Reason: 15105). (Microsoft.SQLServer.Smo) This error is normally disk space related. Check if you have enough free space on the destination for a backup of the database you are trying to backup to fit. In my instance the backup of the database was normally 12GB in size I had 10GB free. Share this:Tweet Please enable JavaScript to view the comments powered by Disqus.
Reason: 15105 Search Search for: Categories failed with the following error a nonrecoverable i/o error occurred on file Advanced Edition (215) Advanced Edition Backup (38) Advanced a nonrecoverable i o error occurred on file 112 there is not enough space on the disk Edition Errors (77) Advanced Edition Recovery (7) Microsoft Exchange (28) Exchange Backup (4) sql server error 15105 Exchange Errors (22) Exchange Recovery (2) Microsoft SQL Server (20) MS-SQL Backup (1) MS-SQL Errors (11) MySQL (2) MySQL Errors (1) https://www.blackforce.co.uk/2014/02/23/sql-backup-failed-error-15105-a-nonrecoverable-io-error-occurred ShadowProtect BMR (2) ShadowProtect Backup (2) Downloads (1) Enterprise Edition (25) Enterprise edition errors (6) Restore (4) Restore issues (2) Standard Edition (87) Recovery (3) Standard Edition Backup (18) Standard Edition Errors (34) Uncategorized (21) A nonrecoverable I/O error occurred on file "XXXX" https://www.cybersecure.com.au/support/?p=1056 112(failed to retrieve text for this error. Reason: 15105 Error [Microsoft][ODBC SQL Server Driver][SQL Server]A nonrecoverable I/O error occurred on file "C:\cybersecure-spool\1312939129295\SQL-SERVE\(local)\DB\DATABASE.bak.2012-01-04-21-00-00-000.ADD:" 112(failed to retrieve text for this error. Reason: 15105 Cause Generally this means there's not enough space on the disk to spool the SQL backup. Here's how to find/change the spooling location. It can also be from the volume on which the spooling location resides is heavily fragmented. Resolution Free up some space Run a defragmentation tool and assess the fragmentation level on all volumes, defrag if fragmentation level is > 15% Online Backup Australia Buy now Learn more Standard edition Advanced edition Enterprise edition Backup partners Signup as a partner Why become an official partner? Company About CyberSecure Privacy Policy Acceptable Use Policy
This morning I had a failed database backup: Executing the query "BACKUP DATABASE [thedatabase] TO DISK = N'T:\\Backup\\th..." failed with the following error: "A nonrecoverable I/O error occurred http://sqladm.blogspot.com/2011/01/backup-failed-nonrecoverable-io.html on file "T:\\Backup\\thedatabase_backup_2011_01_18_221400_5137140.bak:" 112(failed to retrieve text for this error. Reason: 15105). No nice :-( When I looked in the log file generated by the Maintenance Plan, the error message was: Task start: 2011-01-18T22:14:00.
Task end: 2011-01-18T22:14:01.
Failed:(-1073548784) Executing the query "BACKUP DATABASE [thedatabase] TO DISK = N'T:\\Backup\\th..." failed with the following error: "A nonrecoverable I/O error occurred on error occurred file "T:\\Backup\\thedatabase_backup_2011_01_18_221400_5137140.bak:" 112(failed to retrieve text for this error. Reason: 15105).
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. When I looked in the Windows System Log, there was no relevant entries. But looking at the drive and the free space I saw error occurred on that there was not space enough for the next backup file. After a cleanup and manual execution of the Maintenance Plan everything was green. The amount of free space can be looked up with PowerShell like this: Get-WmiObject -Query "SELECT FreeSpace, Size FROM Win32_LogicalDisk WHERE DeviceID = 'T:'" -ComputerName SANDY.sqladmin.lan |
Format-Table @{Name='Freespace (GB)';Expression={"{0:N1}" -f($_.FreeSpace/1gb)}}, @{Name='Size (GB)';Expression={"{0:N1}" -f($_.Size/1gb)}} -AutoSize The value of the parameter ComputerName should be changed to the actual databaseserver, also value in the WQL WHERE clause should be changed to the drive indicated in the error message. The follow up is to order some additional storage. I find the error message somewhat misleading. It looks like the ResultSet part is from the connectivity and not from the root error. History2011-01-19 : This is postede for the first time. 2013-08-22 : The PowerShell script is added. Posted by Niels Grove-Rasmussen at 08:58 Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: backup, SQL Server, storage 1 comment: Jason Clark said... Many thanks for sharing this, it has solved the problem with backing up our database, without having to change the serv