Check both full and differential backups for the overdue alert
As it is, the backup overdue alert will not check if a differential backup has been run.
Example: We have a database with simple recovery model that is set up to make a FULL backup every week, and a differential backup every day. If the alert level is set to "more than one day" then it will be triggered even though the diff backup has been run, indicating that it is not overdue.
We could set (and do that) the alert level to check only for "more than 7 days", but then we will not be notified if a diff backup has not been made.
Thank you for this suggestion, and apologies for not updating sooner.
We believe this was solved when the Differential Backup Overdue alert was added in Version 8.0.7 (May 2018) . This alert is raised when entries for a differential or full backup in the [msdb].[dbo].[backupset] system table are older than the time you specify.
We will mark this as completed but please do let us know if you have any further feedback.
The SQL Monitor Development Team
Apologies Bryan, the previous status update was a bit of a mixup
Bryan Eargle commented
The statement that "differential backups aren't a requirement of healthy backup processes" is highly misleading. A healthy backup strategy is developed based on RPO (how much data can we lose?) and RTO (how long will it take to restore?) requirements.
Differential backups are an essential tool in reducing RTO, regardless of the environment.