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.1 |
| Last Updated | November 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.
To see every BDR at once, open the Windmill backup console → Veeam → Status (https://windmill.dtctoday.com/apps/get/f/rmm/backup_console; in production since 2026-11-05, promotion DTC-Inc/windmill#376). How to read it: Backup Console (Windmill).
- What it does: it reads these same fields every 6 hours, ranks the BDRs that need attention, and groups them by cause, each with the page that fixes it.
- Which BDRs it counts: each client's expected BDRs (its agreement includes a BDR, and the BDR reports). Any other BDR is on the Overview's Cleanup review.
- A BDR's detail shows what is wrong, its jobs and machines against DTC's RPO, and its history, with the error text NinjaOne recorded.
- It is a step behind the BDR itself. Use it to find the BDR and the error, then work the alert from this page.
Know what the fields can and can't tell you
- The
veeam*failure and last-success fields are written by the NinjaOneveeam-inventoryscript. They're as current as its last run on that BDR. - No field carries the error text.
veeamServerLocalBackupsFailedis a checkbox.veeamInventorylists 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. The backup console keeps every Veeam MP event NinjaOne still holds and shows it on the BDR's detail (event log); about a fifth of them carry the text.
- 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, or find the BDR under Veeam → Versions in the backup console. The pin moves as vulnerabilities are patched. 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?
- BDR offline in NinjaOne → BDR Offline & Connectivity.
- Veeam service down alert, or
VeeamBackupSvcstuck in StopPending → VeeamBackupSvc Stuck Stopping or Won't Start.
3. Are all the site's jobs off?
If nothing at the site has a recent restore point, it isn't backing up at all → Veeam Jobs All Disabled — Site Not Backing Up.
- In the backup console: this shows as Unprotected: every local scope missed its RPO, or the BDR's report proves no restore point ("Protection not verified"). It shows as Failing when only the servers have stopped.
- "Protection not verified": re-run the veeam-inventory report, and upgrade to the pinned build where behind.
- Why the fields can't show it on their own: each last-success field holds the oldest machine in its scope, so one stale machine holds it back while the rest back up normally.
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 |
The oldest server's last local restore point: every server has a backup at least this recent, and one stale machine holds it back. The newest is in veeamConfigJson (lastSuccessByBucket). The S3 and workstation last-success fields below work the same way. |
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. The backup console counts orphaned restore points as housekeeping: a count with its own list on the Overview, never a status (a BDR with orphans keeps the status its backups earn). An orphan with no restore point in 30 days, and that no running job names, is left out of the BDR's protection counts and listed on the BDR. | 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 |
Retired. The Veeam v13 Upgrade script wrote it until v4.50. The field was never provisioned in NinjaOne and the write was removed, so upgrade state has no data source. | Version Standard |
Other NinjaOne alerts
| Alert | Go to |
|---|---|
| Veeam service down | Step 2 |
| Veeam MP event | Read the event's text (also on the BDR's detail in the backup console; the same error is grouped across the fleet under Veeam → Status and Failures), then step 4. An event-log condition stays active until it is reset: if the BDR has a good restore point newer than the alert, reset the condition in NinjaOne. |
| Backup job last success 168 hours ago | Step 3 first — a week without success is the signature of disabled jobs |
Related
- Veeam BDR Script Toolkit — every script, and which problem it fixes
- Veeam & BDR Troubleshooting Guide
- NinjaOne — Custom Fields Reference
- Backup Console (Windmill) — the fleet view of every BDR, and how to read it
- Backup Coverage, Veeam and Backblaze B2 (Windmill) — the collectors behind the console
| Version | Date | Author | Change |
|---|---|---|---|
| 1.0 | October 2026 | Z. Boogher | Initial release. NinjaOne entry point for Veeam alerts after the v13 upgrade (HALO 1179664). |
| 1.1 | November 2026 | Z. Boogher | Changes for backup console 1.17.0 (in production with promotion #376, which superseded #357): • pointed to the console's Veeam tab for the fleet view, the BDR detail and the Veeam MP event history; • corrected step 3 and the last-success field (each holds its scope's oldest machine); • added "Protection not verified"; • the pin moves as vulnerabilities are patched; • stale Veeam MP conditions are reset; • retired the veeamUpgradeState row (no data source);• linked pages 4549 and 3965. HALO 1173928. |
| 1.2 | November 2026 | Z. Boogher | The console's final rules (HALO 1173928): orphaned restore points are housekeeping, not Warning; a server scope is judged by its bucket's newest point (one server past its RPO is shown as information); a BDR with no scope inside its RPO is Unprotected. |