August 17, 2021 at 2:56 pm
I'm trying to get rid of all backup messages in my SQL logs and I was able to successfully suppress completed notifications by enabling trace flag 3266. However, I'm still dealing with "backup passed" and "backup skipped" entries which quickly clutters the log when performing log backups every 10 minutes on dozens of databases. The messages look like this
Backup passed. BACKUP DATABASE [TestDB] level [LOG]
Backup skipped. BACKUP DATABASE [master] level [LOG]
Is there a way to suppress these as well?
August 17, 2021 at 5:40 pm
I'm trying to get rid of all backup messages in my SQL logs and I was able to successfully suppress completed notifications by enabling trace flag 3266. However, I'm still dealing with "backup passed" and "backup skipped" entries which quickly clutters the log when performing log backups every 10 minutes on dozens of databases. The messages look like this
Backup passed. BACKUP DATABASE [TestDB] level [LOG]
Backup skipped. BACKUP DATABASE [master] level [LOG]Is there a way to suppress these as well?
Did you mean 3226?
I have never seen that message in a SQL log. Are you using a third party backup?
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
August 17, 2021 at 5:47 pm
Yes, 3226. My bad on the typo.
It is a third party backup which I've looked at their documentation to see if there is a setting to prevent writing to the SQL logs and that does not appear to be the case. I was trying to keep this from turning into troubleshooting the third party software which I why I didn't bring it up. I was hoping that since 3226 suppressed the completion messages that there was something similar for the other two. If not, then no big deal.
August 17, 2021 at 9:11 pm
Yes, 3226. My bad on the typo.
It is a third party backup which I've looked at their documentation to see if there is a setting to prevent writing to the SQL logs and that does not appear to be the case. I was trying to keep this from turning into troubleshooting the third party software which I why I didn't bring it up. I was hoping that since 3226 suppressed the completion messages that there was something similar for the other two. If not, then no big deal.
I agree with Michael... the messages being produced don't appear to be from SQL Server. I totally understand why you'd like to avoid 3rd party support but this one is going to need it unless you can find some setting/configuration in the 3rd party app.
Out of basic curiosity, what is the 3rd party app?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2021 at 2:33 pm
It is Dell Data Domain Boost
August 18, 2021 at 2:43 pm
It is Dell Data Domain Boost
Thanks, Ron.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2021 at 2:55 pm
It is Dell Data Domain Boost
Have you done test restores from this? We looked into this a while back, and they could not prove to me that their backup solution would have no data loss.
They may have added an agent, and Dell partnered with Ola Hallengren to add the Dell Domain Boost as an option to his backup solution.
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
August 18, 2021 at 2:58 pm
We've done quite a bit of testing and so far so good with no data loss. Let's hope that continues to be the case.
July 17, 2023 at 4:49 pm
Hi Ron, do you have any updates on this issue? We just implement DDBoost in our SQL environment and the SQL logs are flooded with this type of message. We contact DELL support and they point finger to Microsoft.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply