Today I’d like to talk about two topics that get overlooked quite often, the “backups” to the backup, so to speak. First up: proper backup alerting. And second, missing backup recovery.
When I saw the topic for T-SQL Tuesday this time I just had to get in. Maybe I’ve never mentioned it, butÂ backups is one of my big things. Â Today I’d like to talk about twoÂ topics that get overlooked quite often, the “backups” to the backup, so to speak. FirstÂ up: proper backup alerting. Â And second, missing backup recovery.
Traditional alerting falls short
Well, let’s begin with a story from my days as senior DBA. Years ago, one of the application groups messed something up in their database, and they needed a restore. Â “Sure thing,” I said. Â No problem. Â So I went to the backup drive, and there wasn’t anything that could even be vaguely considered a fresh backup. The last backup file on the drive was from about threeÂ months ago.
OOPS. Â Oh crap…so what do I tell the app team?
First, a little investigation. Â I had to find out why the backup alert didn’t kick off. Every box was set up to alert us when a backup job failed. Â I found the problem right away. Â The SQL Agent was turned off. Â And from the looks of things, it had been turned off for quite some time. Â And as you may realize, there’s just no way to alert on missing backups if the Agent is off and can’t fire the alert.
But that was just the first part of the problem. Â The SQL Agent couldn’t send the email, of course. But the job never actually failed, because it didn’t start in the first place.
This is the crux of the issue: jobs that don’t start, can’t fail. Â Alerting on failed backup jobs isn’t the way to go.
“But it’s okay, we have…”
Hold on, I know what you’re thinking. You have service alerts through some other monitoring tool, so that could never happen to you! To Â degree,Â you’re right. But let’s see what else can go wrong along those same lines:
- The database in question isn’t included in the backup job.
- The network monitor agent was turned off, or not deployed to that server.
- SMTP on the server has stopped working.
- The backup job has the actual backup step commented out.
- Someone deleted that backup job.
- Someone disabled the backup job, or just disabled the job’sÂ schedule.
Service alerts won’t help you in any of these circumstances.
Proper backup alerting
I’ve run into every one of those scenarios, many times. Â And there are only two ways to mitigate every one of them (and any other situation you come across) with proper backup alerting.
Number one: Move to a centralized alerting system. Â You can’t put alerts on each of your servers. When you do that, you’re at the mercy of the conditions on that box, and those conditions can be whimsical at best.
Move the backup alerts from the server level to the enterprise level. Â Then, when there’s an issue with SMTP or something, you only have one place to check. It’s much easier to keep track of whether Â an enterprise level alerting system isn’t working than to keep track of dozens, hundreds, or even thousands of servers. Â After all, if you haven’t heard from a server in a long time, how do you know whetherÂ it’s because there’s nothing to hear, or if the alerting mechanism is down?
Number two: Stop alerting on failed backups. Â Alert on missing backups. Â When you alert on missing backups, it doesn’t matter if the job didn’t kick off, if the database wasn’t part of the job, or if the job was deleted. Â The only thing that matters is that it’s been 24Â hours since your the backup. Then when you get the alert, you can look into what the problem is.
The important point is that the backup may or may not have failed, but your enterprise alert will fire no matter what. Â This is a very effective method for alerting on backups, because it’s incredibly resilient to all types of issues…not only in the backups, but also in the alerting process. Â If you do it right, it’s just about foolproof.
Part 2: Missing Backups
Handling missed backups is not the same as alerting on missing backup (like we talked about above). What we want to do is avoid the need for the alert to begin with.
Minion Backup (which is free, so we get to talk about it all we want, ha!) includes a feature called “Missing Backups”, which allows you to run any backups that failed during the last run. Â
Here’s what this looks like: Â You set your backups to run at midnight, and they’re usually done by around 2:00 AM. Â However, occasionally they fail for one reason or another. Then you get an alert in the middle of the night, and you have to get up to deal with it.
Missing Backups lets you set Minion Backup to run again at, say, 2:30 or 3:00 AM with the @Include = ‘Missing’ parameter. Â This will look at the last run and see if there were any backups that failed;Â if there were, then MB will retry them. Â This will prevent the need for alerts in the first place.
We use this feature in many shops we consult in because we see databases that fail from time to time for weird reasons, but they always pass the second time. Â So Minion Backup helps improve your backups simply by giving you a second chance at your backups.
Now we mention Minion Enterprise
We’ve got you covered for enterprise-level alerting, too. Â Our flagship product, Minion Enterprise, was made for just that purpose and it comes with many enterprise-level features; not just backup alerting. Â I invite you to take a look at it if you like.
But if you don’t then by all means, write yourself an enterprise-level alerting system and stop relying on alerts that only fire on missing backups.
And, improve your situation in general by switching to the free Minion Backup.