Backups & Storage
Backup failed overnight
Triage failed home backups before deleting jobs, drives, or old versions — the device slept, the destination vanished, the disk filled, or login changed.
Problem summary
An overnight backup often fails because the device slept, the destination disappeared, the disk filled, or credentials changed. If the immediate error is capacity, use backup drive full before deleting files by hand.
Record the exact backup app error and failure stage.
Event Viewer > Windows Logs > Application and System
You know whether it failed during scan, transfer, verify, cleanup, or retention.
Stop if this is the only current backup or source storage is failing.
Layer path
Step-by-step runbook
Start here. Do each check in order, compare it to the expected result, and stop when the evidence explains the failure or the safe stop point applies.
Capture the failure before changing anything
Check: Record the job name, last success, error code, destination path, and stage.
Expected result: The failure has enough evidence to isolate the layer.
If not: Do not delete or recreate the job yet; inspect logs first.
Prove the destination is reachable
Check: Open the external drive, NAS share, or cloud app and test access with the same account.
Expected result: The destination is reachable and has enough space.
If not: Reconnect, reauthorize, or repair that one destination path first.
Run one awake manual backup
Check: Keep the computer powered, awake, and on the trusted network while running one manual job.
Expected result: The manual run either succeeds or fails with clearer layer evidence.
If not: Compare backup app logs with OS events at the same time.
Verify recovery, not just backup status
Check: Restore one harmless file to a temporary folder.
Expected result: The restored file opens and matches the expected content.
If not: Stop cleanup and preserve backup history.
Safe stop: Stop if this is the only current backup or source storage is failing.
Clean up only through documented retention controls
Check: Use backup-app retention or compact controls if space caused the failure.
Expected result: Backup history remains readable and the next job has enough room.
If not: Add capacity or create a new backup destination before deleting history by hand.
Decision tree
If: The destination is unreachable now.
Then: Network, drive, credentials, or cloud account reachability is the active layer.
Action: Reconnect destination and test access before rerunning the job.
If: The destination is reachable but restore fails.
Then: Recovery confidence is broken.
Action: Stop cleanup, protect existing backup sets, and create a second copy if possible.
Safe stop: Stop before deleting old backups or reinitializing backup history.
If: The job fails during cleanup or retention.
Then: Space or backup-chain maintenance is the active layer.
Action: Use the backup app's documented cleanup controls; do not delete internals manually.
If: The job fails after sleep or battery saver.
Then: Power state interrupted the schedule.
Action: Adjust backup window, power settings, and manual test conditions before changing destinations.
If: SMART warnings, clicking, disconnects, or corruption appear.
Then: Storage health may be failing.
Action: Preserve evidence and avoid more writes.
Safe stop: Stop for data recovery help if this is the only copy.
Evidence table
| Symptom | Evidence to collect | Likely layer | Next action |
|---|---|---|---|
| Backup failed overnight, manual run works. | Manual run succeeds while powered/awake; schedule time overlaps sleep or network drop. | Power state or scheduler | Adjust backup window and power settings before changing destination. |
| Destination not found. | Drive missing, NAS share inaccessible, cloud account signed out, or path changed. | Destination reachability | Reconnect and test destination with the same account. |
| Destination full. | Backup app reports quota/retention failure or disk free space is low. | Capacity or retention | Use documented retention cleanup and add capacity only after restore point is identified. |
| Verification or corruption warning. | Backup app verification error, Event Viewer errors, or restore spot-check failure. | Backup integrity | Preserve backup set and create independent copy before cleanup. |
| Permission error on network target. | Same account cannot create a harmless temporary file on the backup share. | Credentials or share permissions | Fix narrow backup account permissions and retest. |
Commands and settings paths
Windows event comparison
Event Viewer > Windows Logs > Application and System
Where: On the backed-up Windows PC around the backup failure time.
Expected: Events line up with backup app error, sleep, disk, network, or permission failure.
Failure means: The backup app may be hiding the lower layer.
Safe next step: Use the event category to pick one next check, not a broad reset.
Power state check
Settings > System > Power & battery > Screen and sleep
Where: On the backed-up PC.
Expected: The machine stays awake long enough for the scheduled backup or wakes reliably.
Failure means: The schedule may be interrupted before transfer or verify.
Safe next step: Run a manual backup while plugged in and awake before editing backup history.
Network destination write test
\\NAS-or-PC\BackupShare > create and delete one harmless temporary file
Where: From the same Windows account used by the backup job.
Expected: The account can write and delete a harmless test file.
Failure means: The destination is reachable but the job account cannot write.
Safe next step: Fix permissions narrowly; do not grant Everyone full control.
Restore spot check
Backup app > Restore > one harmless file > temporary folder
Where: Inside the backup application.
Expected: A small file restores and opens from a temporary location.
Failure means: Backup integrity is unproven.
Safe next step: Preserve history and add an independent backup before cleanup.
Hardware and platform boundary
Change only when
- Buy more storage only after retention cleanup, source growth, and restore requirements prove current capacity is too small.
- Add a NAS or second destination when one backup target creates a single point of recovery failure.
Evidence that matters
- Usable capacity after retention, supported backup app, restore speed, offsite copy support, UPS protection, and alerting.
- For external drives, reliability and independent copy strategy matter more than headline speed.
Evidence that does not matter
- A faster drive does not fix expired credentials or sleep interruptions.
- A bigger target is not safer if restores are never tested.
Avoid
- Avoid deleting backup internals manually to make room.
- Avoid migrating backup history while the source disk reports health warnings.
Related tool/checklist
Use the linked tool when you need a guided plan from your exact symptoms instead of a static checklist.
Backup plan builderRelated problems
Last reviewed
2026-05-07 · Reviewed by HomeTechOps. Reviewed for backup logs, restore verification, destination permissions, retention safety, and recovery-first escalation.
Sources/assumptions
- Assumes home backup software, external drives, NAS shares, or cloud backup tools.
- Recovery value matters more than a green scheduled-task status.
Source-backed checks
HomeTechOps turns official docs and conservative safety rules into a shorter runbook. These links are the source trail for the page direction.