June 25, 2012 at 9:24 am
Hi,
Background: SQL Server 2008 R2 64-bit Enterprise on Windows Server 2008 R2. I have a Maintenance Plan taking log backups every 10 minutes. It is a custom SQL statement task that contains the backup script and restore verifyonly.
I executed the sp_Blitz report and the report checks on the backups. It says that my database "is in Full recovery mode but has not had a log backup in the last week." I know this is inaccurate since I see log backup files on my backup drive as well as my backup scripts executing successfully. Does the script have to have "USE master" at the top or something? Can someone please tell me how to fix this so that the information is accurate?
Thank you!
June 25, 2012 at 9:42 am
Unfortunately, we can't see what from here what you see there. The sp_Blitz report must be a customer routine as I have no idea what it does or where it is pulling its data. I also have no idea how you custom procedure accomplishes the backups. If you are using native backups, I would start by looking at the table in msdb to see if I can find the information regarding the t-log backups.
June 25, 2012 at 10:04 am
I just looked at the stored procedure for the report and it looks at msdb.dbo.backupset where backup_finish_date <= dateadd(dd, -7, getdate()). When I queried the table, backupset only has three days of historic data for logs. Is there an automatic delete job that's occurring behinds the scenes that deletes backupset data? (I have tried searching for the stored procedure, sp_delete_backuphistory, but wasn't able to find any objects that contains that line) Or is there a threshold of x amount of rows before it deletes records?
Thank you!
June 25, 2012 at 10:18 am
Are you using the maintenance plans to manage you backup history?
June 25, 2012 at 10:06 pm
We told Brent about that bug in the script last week. He said he'd look at it as soon as he could. that line you mentioned should be <- instead of <-.
June 26, 2012 at 2:07 am
Robert Davis (6/25/2012)
We told Brent about that bug in the script last week. He said he'd look at it as soon as he could. that line you mentioned should be <- instead of <-.
Think that should of been, > instead of <
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply