Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
johncurl
Starting Member
3 Posts |
Posted - 2010-01-20 : 02:41:52
|
We have in place 4 maintenance plans (MP) 2 databse backups,transaction log backup and a weekly compression all work according to settings except one MP database backup failing daily.Manually backed up works ok. See errors below. Unable to find a solution, any one seen this before and can point us in the right direction to rectify? from sql logs:BACKUP failed to complete the command BACKUP DATABASE [ArchiveManager] TO DISK = N'H:\Program Files\Microsoft SQL Server\MSSQL\Backup\ArchiveManager_db_201001192301.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT Internal I/O request 0x5D36DC70: Op: Write, pBuffer: 0x07420000, Size: 262144, Position: 25959602688, UMS: Internal: 0x103, InternalHigh: 0x0, Offset: 0xB501A00, OffsetHigh: 0x6, m_buf: 0x07420000, m_len: 262144, m_actualBytes: 0, m_errcode: 112, BackupFile: H:\Program Files\Microsoft SQL Server\MSSQL\Backup\ArchiveManager_db_201001192301.BAK from server event viewer:Event Type: ErrorEvent Source: MSSQLSERVEREvent Category: (2)Event ID: 17055Date: 19/01/2010Time: 23:18:46User: NT AUTHORITY\SYSTEMComputer: ARCHIVEDescription:18210 :BackupMedium::ReportIoError: write failure on backup device 'H:\Program Files\Microsoft SQL Server\MSSQL\Backup\ArchiveManager_db_201001192301.BAK'. Operating system error 112(error not found). |
|
Kristen
Test
22859 Posts |
Posted - 2010-01-20 : 03:29:20
|
"Operating system error 112(error not found)."I'm going to put that error message in all my errors for now on, it will save a shed load of time in development Barstewards ...I reckon you either have a fault on your disk system (possibly disk full, but hopefully you would have got a more intelligent message for that)Backup seems to be going to H:\Program Files\... - which I have to say isn't really an ideal place (but it did use to be the default under SQL 2000, and possibly SQL 2005 - same people decided that who wrote the error message I expect!)So I recommend you point it at a different location.Or alternatively there is a corruption in your database itself (although the error message doesn't imply that).Check the database integrity with:DBCC CHECKDB('MyDatabaseName')(Don't use the "Repair" options that comes with that command, if you find problems, without checking back with us first. The Errors guy wrote that bit too and you will suffer "data-loss", rather than "repair" ) |
|
|
johncurl
Starting Member
3 Posts |
Posted - 2010-01-20 : 04:03:22
|
Kirsten thanks for quick reply.we did suspect it could be drive capacity issue but resolved that by doing the manually back up to different locations.The MP still failing even with new locations? Also recreated MP.will try the command supply.. |
|
|
Kristen
Test
22859 Posts |
Posted - 2010-01-20 : 05:29:01
|
The Wizard's Maintenance plans are notorious for lacking robustness, and in particular error messages that don't give much clue as to what the problem is.These look like disk I/O errors, or corrupt database, but based on past experience the error could be elsewhere.What version of SQL are you on? |
|
|
johncurl
Starting Member
3 Posts |
Posted - 2010-01-20 : 05:40:15
|
running sql 2000 -no local dba so investigating this has been slow. |
|
|
|
|
|
|
|