May 2, 2008 at 3:02 am
Morning all,
I am running into a few issues which are really frustrating on two of my servers. Both the servers have maintenance plans set up that do a full backup each night, the backup works one night and then not the next, works again the next night and then fails the next. This is always the case, it never works or fails two nights in a row.
The error messages are shown below for one of the servers (they are the same on both)
SQL Server Logs
Full Backup (sqltransfer)
Backup Database on Local server connection
Databases: ADV,FactFind,ProductX,Tenants,Virgin,WebApplications,XMLParser
Type: Full
Append existing
Task start: 2008-05-02T00:30:05.
Task end: 2008-05-02T00:56:08.
Failed:(-1073548784) Executing the query "BACKUP DATABASE [ProductX] TO DISK = N'D:\\MSSQL.1\\MSSQL\\Backup\\ProductX\\ProductX_backup_200805020030.bak' WITH NOFORMAT, NOINIT, NAME = N'ProductX_backup_20080502003005', SKIP, REWIND, NOUNLOAD, STATS = 10
" failed with the following error: "Write on "D:\\MSSQL.1\\MSSQL\\Backup\\ProductX\\ProductX_backup_200805020030.bak" failed: 112(error not found)
Application Log
Message
BackupMedium::ReportIoError: write failure on backup device 'D:\MSSQL.1\MSSQL\Backup\ProductX\ProductX_backup_200805020030.bak'. Operating system error 112(error not found).
And…
Message
BackupDiskFile::OpenMedia: Backup device 'D:\MSSQL.1\MSSQL\Backup\ProductX\ProductX_backup_200805020030.bak' failed to open. Operating system error 2(error not found).
Also an extract from the log file generated by the Maint Plan
BACKUP DATABASE is terminating abnormally.
10 percent processed.
20 percent processed.
30 percent processed.
40 percent processed.
50 percent processed.
60 percent processed.
70 percent processed.
80 percent processed.
90 percent processed.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Can anyone shed any light on this?? I would be eternally grateful 🙂 its driving me mad.
May 2, 2008 at 5:57 am
Can you provide us the following details -
1> r u using a network drive or a tape drive to save?
2> have you saved it as your backup device?
3> does the backups on the servers occur complementarily, i.e., one fails when the other occurs?
4> what are the schedules for the jobs?
5> how frequent do you restart your instances or servers, including critical updates?
If you provide some more details, I am sure there are people out here who can help you out.
Chandrachurh Ghosh
DBA – MS SQL Server
Ericsson India Global Services Limited
Quality is not an act, it is a habit.
May 2, 2008 at 6:05 am
Error 112 can indicate insufficient disk space - do you have enough disk space when the plan is run?
Piotr
...and your only reply is slàinte mhath
May 2, 2008 at 6:46 am
Piotr Rodak (5/2/2008)
Error 112 can indicate insufficient disk space - do you have enough disk space when the plan is run?Piotr
In this case it is not disk space, that was the first thing i checked after getting the error.
May 2, 2008 at 6:55 am
Chandrachurh Ghosh (5/2/2008)
Can you provide us the following details -1> r u using a network drive or a tape drive to save?
2> have you saved it as your backup device?
3> does the backups on the servers occur complementarily, i.e., one fails when the other occurs?
4> what are the schedules for the jobs?
5> how frequent do you restart your instances or servers, including critical updates?
If you provide some more details, I am sure there are people out here who can help you out.
1. Local drives only are used.
2. Its not a backup device. Its simple a MP that uses a folder and creates a file on the fly
3. All the backups are in the same job, so when one fails the job step fails and the other backups do not occur
4. The schedules are as follows...
Full backup daily at 00:30
Diff backup daily 14:30
T-Log backup hourly between 08:00 and 22:00
Maintenance cleanup at 01:00 internal and external. cleans up any files older than 1hr
5. The server is fairly new (1 month old) and no critical updates have been added since it was put live (all updates were put on as part of the build). Server are restarted roughly every 2 weeks, although no fixed schedule is in place.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply