Micro survey #19: Extending Veeam monitoring

Announcements
1

Greetings community!

Micro survey number 19 is here, and this time we are looking at Veeam!

We are building out our Veeam monitoring, and rather than guess at what matters, we would rather hear it from the people running it. Repositories, proxies, replicas, restore points: which of these would actually change your day? That is the question, and the survey takes about two minutes to answer.

Every response feeds directly into what we build first, so this is a genuinely good moment to make your case for the check you have been missing.

Click here to start the survey

Thanks for helping us point our effort in the right direction!

Cheers
David

2

Thank you for the survey, one questions was missing when I selected why I don’t monitor it with checkmk right now (or a general ask for commentary): We only use it as a backup destination for unmanaged clients, and these jobs currently don’t show up in the current checks.

So it would be great if that could be added in the future

3

Thank you for your feedback, Christian.

I’d love to deep dive on your use case. I’ll send you a DM.

4

That can be easily achieved with current version. Only a small patch inside the Powershell script is needed to get also data for file backup clients.
It’s the same problem as the not visible Nutanix and Proxmox backups.

5

Thanks @andreas-doehler, that is useful. Which part are you thinking of? The IsScheduleEnabled filter on the Get-VBRJob call, or does Get-VBRJob simply not return these job families, so a different cmdlet is needed?

6

First you need to modify the line

    $myBackupJobs = Get-VBRJob -WarningAction SilentlyContinue | where { $_.IsScheduleEnabled -eq $true }

to

    $myBackupJobs = [Veeam.Backup.Core.CBackupJob]::GetAll()

And i commented this line

if ($myJob.IsBackup -eq $false -and $myJob.IsEndpointJob -eq $false) { continue }

As these other jobs don’t have “IsEndpointJob” as true.

I let the user then decide what he wants to monitor or not.

7

We have a custom script that also checks the status of backup encryption, remembering the state on first discovery & comparing the current state against that base line on each check interval. The logic behind that is to detect potential ransomware infestation. There are several cases out there where ransomware turned on encryption without the admins noticing, then lying dormant for a month or so (until all the unencrypted restoration points have been replaced by encrypted ones), and only then infesting the rest of the local ecosystem. This makes it much harder for an affected company to recover without paying for decryption.

This might be useful to have for others, too. I’m currently way to busy to package that as a plugin for the Exchange myself, unfortunately.