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?
- Not on 13.1.1.18 → open a Halo ticket to update it: Veeam Version Standard — Pinned Build 13.1.1.18
- An upgrade or patch run failed → Veeam Setup Failure Reference (13.1.1.18)
Is the alert about storage/disk space?
- BDR repository full or insufficient disk space → BDR Storage Alerts & Capacity Issues
- Source server C: drive full → Veeam Troubleshooting Playbook - Scenario 10
Is the BDR offline or unreachable?
- Can't ping/RDP to BDR → BDR Offline & Connectivity
- BDR online but Veeam console won't open → Check services, Event Viewer
- VeeamBackupSvc stuck in StopPending, or won't start → VeeamBackupSvc Stuck Stopping or Won't Start
Has the site stopped backing up with no failures?
- Every job's last success has stopped moving → Veeam Jobs All Disabled — Site Not Backing Up
Are backup jobs failing?
- Job dies in 8–16 seconds — "host rescan is required" or "outdated Data Mover service version" → Veeam Server Jobs Fail in Seconds
- Guest processing failed on a Hyper-V VM → Veeam Guest Processing Fails on Hyper-V VMs After Upgrade
- VSS errors → Veeam Troubleshooting Playbook - Scenario 1
- SQL consistency errors → Veeam Troubleshooting Playbook - Scenario 5
- Network timeout/connection failed → Veeam Troubleshooting Playbook - Scenario 3
- Agent deployment failed → Veeam Troubleshooting Playbook - Scenario 4
- Chain integrity broken → Veeam Troubleshooting Playbook - Scenario 6
- Many
.avhdxlayers, merge pending, provisioned size far too large → Orphaned Checkpoint (AVHDX) Chain on a Hyper-V Guest
Is an agent or endpoint offline?
- Veeam Agent showing offline in console → Agent & Endpoint Offline
- Outdated agent blocks the BDR upgrade, or MSI Error 1714 → Veeam Endpoint Agent Blocks the BDR Upgrade
- Agent installed but not communicating → Check Windows Firewall, Veeam services
Are backups slow or timing out?
- Job runs but throughput is very low → Performance & Slow Backups
- Cross-subnet transport issues → Veeam Troubleshooting Playbook - Scenario 3
- Dual-NIC causing network issues → Veeam Troubleshooting Playbook - Scenario 7
DNS or name resolution issues?
- "Failed to resolve host name" → Veeam Troubleshooting Playbook - Scenario 8
When to Escalate to Veeam Support
If T3 troubleshooting cannot resolve the issue:
- Collect Veeam logs: Main Menu → Help → Support Information → Export
- Note the exact error message and job session ID
- Open a case with Veeam Support
- Document the Veeam case number in the HALO ticket
Related Resources
- NinjaOne Veeam Alerts & Custom Fields — Where to Start - Entry point from a NinjaOne alert or custom field
- Veeam BDR Script Toolkit - Every Veeam script and the problem each one fixes
- Veeam Troubleshooting Playbook - Comprehensive 10-scenario guide with T1/T2/T3 tiered responses
- Veeam BDR Deployment SOP - Initial setup and configuration
- Veeam Backup Daily Operations & Verification SOP - Day-to-day monitoring
Last Updated: October 2026
Version: 1.1
| 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. |