March 10, 2010 at 9:27 pm
SQL Server 2008,
Drives : Normal Drives
TITLE: Microsoft SQL Server Management Studio
------------------------------
Backup failed for Server 'DEV01'. (Microsoft.SqlServer.SmoExtended)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.0.2531.0+((Katmai_PCU_Main).090329-1045+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Backup+Server&LinkId=20476
------------------------------
ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: A nonrecoverable I/O error occurred on file "C:\PROCES.bak:" 112(failed to retrieve text for this error. Reason: 1815). (Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.0.2531.0+((Katmai_PCU_Main).090329-1045+)&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
Unable to perform a backup. Please help me to sort this.
Cheers,
- Win.
" Have a great day "
March 11, 2010 at 8:38 am
Is this Just a single Database or several databases.
Are any of the databases in read_only mode or something.
Are all databases in single compatibility mode and none in 70 or 80.
Are all database accessible.
Maninder
www.dbanation.com
March 11, 2010 at 8:49 am
Adding to Mani's questions....
If backup is failing on only one database, run checkDB on that database. Get in touch with server team and see if disk went offline at that time. When was the last time you had rebooted this server? Check event logs for any disk error messages.
March 11, 2010 at 9:12 pm
Database is never backedup till date. Its a DEV server. So planned to perform a backup
Database compatibility - 80 (all the dbs - simple).
Disk is fine, as the database files are on the same disk where i tried backing up.
Database size is 86GB and space available is 51GB. I guess its a space issue.
But still its showing different error as I/O, am worried if the disk is in danger. Could not able to figure out.
Any more suggestion.
Cheers,
- Win.
" Have a great day "
March 12, 2010 at 7:16 am
If you are worried about the back Up size, try compressing the back up. Also it is better practice not to put DB or its back up on the OS Drive.
Also try to back it up to a different location.
-Roy
March 15, 2010 at 5:47 am
Change the database compatability level to 100 and make recovery model to full for point in time recovery of database.
March 15, 2010 at 6:07 am
Ratheesh.K.Nair (3/15/2010)
Change the database compatability level to 100 and make recovery model to full for point in time recovery of database.
Ratheesh, Could you explain how setting the compatibility mode to 100 and recovery model to full help solve the error the OP is getting?
-Roy
March 15, 2010 at 11:34 pm
Hi Roy,
So u mean that they need to keep the compatability level in 80 for a sql server 2008 server?
Is it possible for u to do a point in time recovery in simple recovery model?
March 16, 2010 at 3:17 am
Hi,
Just a quick trick to pinpoint such problems, when windows error numbers cannot be resolved:
System.Data.SqlClient.SqlError: A nonrecoverable I/O error occurred on file "C:\PROCES.bak:" 112(failed to retrieve text for this error. Reason: 1815). (Microsoft.SqlServer.Smo)
The error number (112) reported by windows is the key here. Use net helpmsg <errornumber> for a more comprehensive output:
[font="Courier New"]$ net helpmsg 112
There is not enough space on the disk.[/font]
HTH
David B.
David B.
March 16, 2010 at 3:21 am
thanks for the tip David
March 16, 2010 at 3:58 am
Ratheesh.K.Nair (3/15/2010)
So u mean that they need to keep the compatability level in 80 for a sql server 2008 server?
No, but changing the compat mode is not going to fix an IO error when doing a backup
Is it possible for u to do a point in time recovery in simple recovery model?
It's not, but then no one's trying to do point-in-time recovery here. The backup is failing, and that's not going to be affected by recovery model.
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 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply