NinjaOne Backup — Error 313 & 314: File Not Found / Inconsistent File
Audience: T2 Use when: Backup fails during integrity check with "Error 313: File not found" or "Error 314: Inconsistent file."
These errors both fire during NinjaOne's integrity verification of the backup repository. They indicate that files in the backup index don't match what's actually stored on the NAS.
313 vs. 314 — The Difference
| Error | What It Means |
|---|---|
| 313 | A file that the backup index says should exist on the NAS is missing entirely |
| 314 | A file exists on the NAS but its content or checksum doesn't match what the index expects |
Both indicate a discrepancy between Lockhart's internal backup database (metadata) and the actual files on the NAS. The result is the same: the backup repository is partially unreliable.
Why These Errors Occur
| Cause | 313 or 314? |
|---|---|
| Files manually deleted from the NAS backup folder | 313 |
| NAS drive failure causing data corruption mid-write | 314 |
| File system errors on the NAS | Either |
| Abrupt disconnection during a backup write | 314 (partial write = inconsistent) |
| NAS volume was snapshotted/restored to a prior state | Either |
| Bit rot on older NAS drives without error correction | 314 |
Step 1 — Check NAS Drive Health First
Before attempting repository repair, confirm the NAS is healthy:
- Log into NAS admin panel
- Synology: Storage Manager → HDD/SSD → check SMART for all drives; check storage pool status
- QNAP: Storage & Snapshots → check drive health and RAID
- Confirm no drives show degraded health, reallocated sectors, or failed RAID members
If the NAS hardware is unhealthy: replace or repair the drive first. Fixing the repository on a failing NAS will just re-corrupt.
Step 2 — Isolated vs. Widespread Errors
A few 313/314 errors: The repository has minor inconsistencies. NinjaOne can often recover autonomously on subsequent runs as it rebuilds the affected blocks.
# Trigger a manual backup run and watch the outcome
# NinjaOne may repair minor inconsistencies automatically during the next full cycle
Many 313/314 errors (Error 311 also firing): The repository has widespread inconsistencies. See Error 311 — the next step is repository deletion and rebuild.
Step 3 — Delete and Rebuild the Repository (For Widespread Errors)
⚠ Discuss with T3 before doing this on a server — this loses all local revisions.
- NinjaOne → device → Backup → Manage → Image Backup Plan → Delete Local Backup Data
- Confirm deletion
- Trigger a new backup run — NinjaOne will perform a fresh full backup to the NAS
- Cloud revisions are unaffected
Step 4 — Run NAS Filesystem Check
After resolving the repository issue, run a filesystem check on the NAS to catch any underlying volume errors:
Synology: Storage Manager → Storage Pool → select the volume → Check File System QNAP: Storage & Snapshots → Storage → select the volume → Check File System