February 16, 2009 at 10:43 pm
Hello,
We are using Sql server 2000 standard edition. Our production back of one database is failing every week.Iam getting below error in the error log. But we have enough space....I attached the stored procedure Iam using for Backups...Please advice me do I need to change any logic in the Backup Script??
Internal I/O request 0x6AEB1E38: Op: Write, pBuffer: 0x086B0000, Size: 983040, Position: 32173464064, UMS: Internal: 0x0, InternalHigh: 0xF0000, Offset: 0x7DB01A00, OffsetHigh: 0x7, m_buf: 0x086B0000, m_len: 983040, m_actualBytes: 0, m_errcode: 112, BackupFile: \\ServerA\d$\Backup\ABC\ABC_02-16-2009.bak
2009-02-15 04:10:56.32 backup BACKUP failed to complete the command
Exec BACKUP_PRODDB 'ABC'
Thanks
February 17, 2009 at 12:22 am
Hello,
How big do you expect the Backup File to be, and how much free space do you have on the Target Drive? Is the Target Drive formatted for NTFS or FAT?
Regards,
John Marsh
www.sql.lu
SQL Server Luxembourg User Group
February 17, 2009 at 12:25 am
Looks like a IO failure. Any drive problems?
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
February 17, 2009 at 12:59 am
What is the meaning of IO failure? where can I check for the drive issues?
Its production box..plz help me...
and I checked in the disk management all the drives are NTFS and the status for all drives is healthy....
Running DBCC CHECKDB for all databases has no errors..
February 17, 2009 at 8:57 pm
Could you give me some more information on this backup faild issue..
what are the things I need to look for drive issues
thanks
February 17, 2009 at 9:09 pm
I believe Gail's response was based on the error and I would agree. The error for space issues is pretty well known and a simple google would have pulled that up. You appear to be having write related issues which would be concerning to me. Glad to hear that you are not seeing any corruption in the databases.
Is this drive just used for backups or are there other database files there? Can you attempt to write the backup to another drive to see how that goes?
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
February 17, 2009 at 9:38 pm
thank you..This drive also has data files along with bakups. Iam seeing this error only on Weekend. Every weekend we scheduled the INTIGRITY and OPTIMIZATIONS jobs which are scheduled to ran at 9:00PM. After that there are no log backups running.(We ran log backups up to 8:0PM).Now I changed the schedule of these jobs to run at early hrs on weekend.
Could you suggest me is there anything wrong with the stored procedure I attached. It is deleting the 2 days back backup after the current backup is done. At this time it may going out of space or something? plz correct me if I misunderstood
February 17, 2009 at 9:48 pm
Actually, after looking at the error a bit more I do wonder if you don't have a space issue during your optimizations. The m_error = 112 may be indicating a space issue. Sorry, didn't notice that at first.
Check out THIS POST for a similar scenario.
One note, when you are doing your reindexing you may incur space constraints not normally noted especially if you are rebuilding them online.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply