No health check mails in V13?

[xmzmc]

Version: Veeam Backup and Replication 13.0.1.1071 on Windows Server 2019

Hi in Veeam Backup and Replication 12, i received separate mail notifications about health checks (beside the regular job notification mails). In Veeam Backup and Replication 13, I only receive mail about the backups jobs but not about the health checks anymore. I have verified that the health check did in fact ran and that the mail connector is ok (otherwise i wouldn't receive mail about backup jobs). Any idea why i don't receive these mails about health checks anymore? Or did it got removed in V13?

Thanks in advance

[HannesK]

Hello,
my suggestion would be to upgrade to the latest version 13.0.1.2067 because it contains many bugfixes.

I cannot remember that we removed that and if updating doesn't help, then I would check two things:
1. is it maybe in the daily summary? It should not, according to the "help text", but just in case.
2. open a support case and argue "it worked in V12". If you already opened a support case, can you please post the case number?

Best regards
Hannes

[xmzmc]

Hi HannesK,

Thanks for your response. I've got some new findings: i noticed the reports are being sent but only when a next scheduled backup job starts. For example:

- Health check starts at 05:00AM, finishes at 05:35AM. No mail sent.
- Scheduled backup job starts at 22:00PM. Mail of the earlier, morning health check is immediately being sent and received on my end at 22:00PM.
The mail i receive on 22:00 mentions the health check started at 05:00AM, finishes at 05:35AM. Mind you, this is NOT a case of mail(server) delay.

It might already worked this way in Veeam12 but not 100% sure. Either way, is this expected behaviour or a bug? I will also try updating to 13.0.1.2067 but i'm very interested to know if this is expected behaviour.

[HannesK]

Hello,
no, the mail should be sent after it finished.

Best regards
Hannes

[FrancWest]

This has always been the case since v12. Health check reports are always sent at 22:00 hours, even if the health check ran earlier that day. Also, when a health check fails, you'll only know this at 22:00 hours, because you don't get a notification right after the failure. See also here: post505728.html?hilit=health#p505728

[HannesK]

oh, thank you Franc!

[xmzmc]

Mmm that changes things. Seems not so desirable behaviour in my opinion. Either way, thanks for the info @FrancWest.

[FrancWest]

Agreed, this should be changed. Why not the same notification flow as with backup jobs. When a health check fails you want to know it immediately and not 24 hours later in a worst case scenario.

[HannesK]

we will discuss again internally and I will come back on this (it can take a while)

[kevlahau]

I had a similar issue with vos and found that the reports had exceeded the email limit so would just fail. Just a thought.

[HannesK]

yes, the idea back in the time was to reduce the amount of emails. If one has for example 100 backup jobs and does health checks, then in worst case one could get 200 emails if one subscribed to "successful" and not only "failed" and "warning" emails. As mentioned before, we will discuss alternatives.

[FrancWest]

Well, that’s where outlook rules are for I have a rule that moves succes e-mails to a health check folder and only warning and failure mails arrive in the inbox.

But in your example, why is a failed health check less important than a failed backup job? Failed health checks require immediate action because that may mean your backups are corrupt. That’s an even more critical situation than a failed backup job, which is being reported immediately.

[JPMS]

This all goes back to when they changed health checks in v12 - veeam-backup-replication-f2/confused-by ... 86604.html and veeam-backup-replication-f2/health-chec ... 92741.html

Veeam 'decoupled' health checks from the backups (they used to take place immediately afterwards). If they had done a complete job of it then it would have made sense but they decided to only do half a job.

Namely:
They actually forgot notification emails at all - they put them in in one of the patches but, even then, we want them when the health check is run.
They didn't provide any way to manually run a health check or schedule it flexibly, so we can't ensure it doesn't overlap with other jobs.
There are no PowerShell commands to run health checks.

There were various noises about fixing some of this but we are a major revision later and nothing has changed.