Skip to main content

NinjaOne Veeam Alerts & Custom Fields — Where to Start

Field Detail
Audience T2 / T3 — Veeam alerts display on the NOC board and are worked by T2 and above
Version 1.0
Last Updated October 2026
Applies To DTC BDRs on Veeam B&R 13.1.1.18
Source HALO 1179664

Start here when a NinjaOne Veeam alert fires or a veeam* custom field looks wrong. This page tells you what the signal means, what it can't tell you, and which page fixes it.

Know what the fields can and can't tell you

  • The veeam* failure and last-success fields are written by the NinjaOne veeam-inventory script. They're as current as its last run on that BDR.
  • No field carries the error text. veeamServerLocalBackupsFailed is a checkbox. veeamInventory lists each job with its last result, but not the message.
  • The error text lives in two places: the NinjaOne Veeam MP event alert, and the job session in the Veeam console on the BDR. Get it before choosing a fix.
  • If a field disagrees with the console, trust the console session. A failure field has been seen checked on a BDR whose backup had succeeded (task T-091).

Triage, in order

1. Is the BDR on the pinned build?

Check against the Veeam Version Standard — Pinned Build 13.1.1.18. If it isn't, open a Halo ticket to update it — many failures are side effects of a half-finished upgrade, and the upgrade script fixes several on its own.

2. Is the BDR up, with its services running?

3. Are all the site's jobs off?

If the last-success fields have stopped moving on every job, the site isn't backing up at all → Veeam Jobs All Disabled — Site Not Backing Up. Check this before anything else on the list below: a disabled job never fails, so nothing alerts.

4. Match the error text

The error says Go to
"host rescan is required", "outdated Data Mover service version", "Unknown invoker method", or the job dies in 8–16 s Server Jobs Fail in Seconds
Guest processing or application-aware processing failed on a Hyper-V VM Guest Processing Fails on Hyper-V VMs
VSS writer failed Playbook — Scenario 1
SQL writer or consistency error Playbook — Scenario 5
Insufficient space on the repository, or the BDR's C: is full BDR Storage Alerts & Capacity Issues
Chain broken, restore point missing Playbook — Scenario 6
Merge pending, many .avhdx layers, provisioned size far too large Orphaned Checkpoint (AVHDX) Chain
Agent offline, outdated agent, MSI Error 1714 Endpoint Agent Blocks the BDR Upgrade
MSI Error 1605, agent install corrupt Veeam Agent — Corrupt Install
Timeout, connection failed, failed to resolve host name Playbook — Scenarios 3, 7 and 8
Only the cloud (S3) copy is failing Veeam S3 Remediation Project
An upgrade or patch run failed Veeam Setup Failure Reference

Nothing matches? Use the Veeam & BDR Troubleshooting Guide, then escalate to T3.

The fields

Field What it indicates Start with
veeamServerLocalBackupsFailed (checkbox) and …FailedLastChanged (date/time) A server job to the local BDR repository failed, and when that last changed. Drives the Veeam Local Server Backups Failed condition. Step 2, then the error text
veeamServerLocalBackupsWarning A server job ended with warnings. Error text
veeamServerLocalLastSuccess Last successful server backup to the BDR. Step 3 if it's stale
veeamServerCloudBackupsFailed, veeamServerCloudLastSuccess The same for the server S3 copy. S3 Remediation Project
veeamWorkstationLocalBackupsFailed, veeamWorkstationLocalLastSuccess The same for workstation agent backups. Workstations that are off at backup time show here. Agent & Endpoint Offline
veeamWorkstationCloudBackupsFailed, veeamWorkstationCloudLastSuccess The same for the workstation S3 copy. S3 Remediation Project
veeamFailedBackupsFound, veeamWarningBackupsFound Any job on the BDR failed, or warned. Error text
veeamLastSuccess The most recent success of any job. Step 3 if it's stale
veeamInventory (text) Each job and its last result — no error message. Read alongside the console
veeamBackupOrphansFound Backups no longer tied to a job. BDR Storage Alerts & Capacity Issues
veeamProtectedMachines, veeamAutomationDisabled Protected machines; automation state. Full definitions to be added to the custom fields reference. —
veeamS3ConfigStatus Whether the Backblaze S3 offsite repository is configured. S3 Remediation Project
veeamUpgradeState The last result of the Veeam v13 Upgrade script — written by that script, not veeam-inventory. Version Standard

Other NinjaOne alerts

Alert Go to
Veeam service down Step 2
Veeam MP event Read the event's text, then step 4
Backup job last success 168 hours ago Step 3 first — a week without success is the signature of disabled jobs
Version Date Author Change
1.0 October 2026 Z. Boogher Initial release. NinjaOne entry point for Veeam alerts after the v13 upgrade (HALO 1179664).
Back to top