Veeam Backup SNMP trap bug

Today I got confirmation that the baffling behaviour I was seeing in the onBackupJobCompleted SNMP trap payload is in fact an actual bug. Result!

For the benefit of others who may find this, the onBackupJobCompleted trap is sent with a payload of four objects:

• backupJobId
• backupJobName
• backupJobResult
• backupJobComment

Despite the name, the backupJobId field contains the GUID of the backup session, such as you'd get back from a Get-VBRBackupSession call.

backupJobName is exactly what you'd expect, and even backupJobComments is reasonably self-explanatory.

The bug is with the backupJobResult field, which at the moment contains the string "None" regardless of the actual job outcome.

As I said earlier, Veeam have confirmed this is a real bug that effects the initial release version of Veeam Backup and Replication v5, and will be fixed in the next release; but they haven't been forthcoming with a release date yet. So that makes this particular trap just about useless right now.