At an MSP, most backup incidents announce themselves. A Veeam job fails, a red email arrives, someone reads it and reruns the job. The more serious problem lies elsewhere: the day no email arrives at all. No failure, no warning, nothing. And in a busy inbox, nothing looks a lot like “all good”.

Why a report stops arriving

A report that no longer arrives is rarely a backup problem in the strict sense. It is a problem somewhere along the chain:

  • The job didn’t start. Schedule disabled after an update, server powered off during the backup window, service stopped.
  • The job ran but no longer sends notifications. Expired SMTP password, mail relay changed, certificate rejected.
  • The notification goes out, but somewhere else. Recipient address changed during a migration, forwarding rule deleted, shared mailbox renamed.
  • The notification arrives, but nobody sees it. Spam filter, automatic folder, an Outlook rule that is too broad.

In all four cases the outcome is the same: the last good news is several days old, and nobody noticed.

Why nobody notices

The human brain is very good at spotting what arrives and very bad at noticing what is missing. When you skim fifty reports in the morning, you look for “Failed” or “Warning”. You don’t count the messages to check there is one per job per day.

A failure is a visible incident. An absence is a silent one, and it is often discovered on the day you need to restore.

Mail filters make it worse: success reports get moved into a folder so they stop cluttering the inbox. That makes sense, but that folder is exactly where the absence would have shown.

The only reliable method: expect something

To detect silence, you need to know what you are expecting. In practice, every backup job needs:

  1. An expected schedule: every day at 2 a.m., every 6 hours, Monday to Friday…
  2. A grace period: a 2 a.m. backup that finishes at 3:40 is not late; at 9 a.m., it is.
  3. A checked deadline: once the schedule and the grace period have passed, a missing report becomes an incident in its own right.

This is the principle of a dead man’s switch: you don’t watch for the alarm, you watch for the heartbeat.

What to do when a report is missing

When a report is missing, the order of checks matters. Start with what is most likely and quickest to verify:

  1. Open the backup software’s console: did the job run?
  2. If it did, check the notification settings: SMTP server, credentials, recipients.
  3. If it didn’t, check the schedule and the state of the server during the planned window.
  4. Send a test email from the software to validate the whole chain.

How Soluax handles silence

Soluax gives every backup task its own receiving address and an expected schedule. When the deadline passes without a report, the task switches to “Report missing”, a ticket opens and an alert goes out. Silence is never turned into a success, and the day in question stays visible on the calendar even after things are back to normal.

You can already check what your current reports say with the free analyzer, without creating an account.