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 |
ddavis66
Starting Member
2 Posts |
Posted - 2011-04-26 : 13:38:32
|
I have a SQL 2008 R2 backup question. When I open my Microsoft SQL Server Management Studio and navigate to the SQL Server Logs, I see nightly that my databases are getting backed up at 7:00 PM every evening. I did not setup a schedule for this. I am assuming this info came across when a backup from our old sql 2000 server and restore to our new sql server happened. I do not see anyway to disable this, edit this ?? When I expand Databases and right click on a database and then properties > I see under the Backup selection when the last backup occurred with a time and date, and also under Last Database Log Backup this has None after it. There are also no jobs under the Maintenance Plans to edit. I am very new to SQL and pretty much inherited this problem. I also see errors being generated in the event viewer at the same time, with event id 57 and event id 137. 57 > The system failed to flush data to the transaction log. Corruption may occur. 137 > The default transaction resource manager on volume \Device\000000142 encountered a non-retryable error and could not start. I have bee looking into the event id's online but so far have not found anything relating to SQL and these events along with my backups.Any help is greatly appreciatedddavi66 |
|
nigelrivett
Master Smack Fu Yak Hacker
3385 Posts |
Posted - 2011-04-26 : 13:48:44
|
Have a look at the agent and see if there is a job set up - if you restored msdb it could be there from the old system.If not it could be that you have a backup application somewhere that is trying to execute backups.==========================================Cursors are useful if you don't know sql.SSIS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
ddavis66
Starting Member
2 Posts |
Posted - 2011-04-26 : 13:59:11
|
The only job there is syspolicy_purge_history. We do have a backup storage device which takes a snapshot of this server every 15 minutes. But the errors in event viewer are not occurring throughout the day, only at 7:00 pm nightly. I reset this "snapshot" task to not occur at 7:00 pm, I was thinking this was due to a snapshot happening the same time as these backups for each database and that is why the errors were being written to the event viewer. |
 |
|
|
|
|