Skip to main content

Veeam & BDR Troubleshooting Guide

Audience: T1 / T2 / T3
Purpose: Quick triage and routing to detailed troubleshooting procedures

How to Use This Guide

This is a decision tree to quickly identify the issue category and route to the appropriate detailed troubleshooting page. Start with the symptom you're observing, follow the diagnostic path, then jump to the linked child page for full resolution steps.

Starting from a NinjaOne alert or a veeam* custom field? Begin at NinjaOne Veeam Alerts & Custom Fields — Where to Start instead. The fields carry no error text, and that page shows where to find it.

For comprehensive scenario-based troubleshooting covering 10+ common Veeam issues, see Veeam Troubleshooting Playbook.

Quick Decision Tree

Is the BDR on the pinned build?

Is the alert about storage/disk space?

Is the BDR offline or unreachable?

Has the site stopped backing up with no failures?

  • Nothing at the site has a recent restore point → Veeam Jobs All Disabled — Site Not Backing Up
    • Don't judge it from the *LastSuccess custom fields alone. Each holds its scope's oldest machine, so one stale machine holds the field back while the rest back up normally.
    • The Windmill backup console (in production since 2026-11-05, promotion #376) shows this site as Unprotected under Veeam → Status, and as Failing when only the servers have stopped. See Backup Console (Windmill).
    • "Protection not verified" (also Unprotected): the BDR's report proves no restore point. Re-run the veeam-inventory report, and upgrade to the pinned build where behind.

Are backup jobs failing?

Is an agent or endpoint offline?

Are backups slow or timing out?

DNS or name resolution issues?

When to Escalate to Veeam Support

If T3 troubleshooting cannot resolve the issue:

  1. Collect Veeam logs: Main Menu → Help → Support Information → Export
  2. Note the exact error message and job session ID
  3. Open a case with Veeam Support
  4. Document the Veeam case number in the HALO ticket

Last Updated: November 2026
Version: 1.2

Version Date Author Change
1.0 April 2026 Scott Leister Initial decision tree.
1.1 October 2026 Z. Boogher Added the NinjaOne entry point, the version-pin check, and branches for the v13 failure pages (4322–4332). Converted every link to a permanent /link/<id> URL — the slug-relative links rendered as invalid URLs.
1.2 November 2026 Z. Boogher Corrected "stopped backing up": each last-success field holds its scope's oldest machine, so the test is whether anything at the site has a recent restore point. Pointed to the backup console's Unprotected status and "Protection not verified" (1.17.0), and linked page 4549. HALO 1173928.