Short answer: Inventory backup folders, then let the backup system decide how retention should change.
By DiskAnalyzer editorial resource · Published 2026-10-05 · Documentation reviewed 2026-10-05
When this guide is useful
Keep at least one verified restore path before reducing retention. The largest set may be a required full backup on which several smaller incremental backups depend.
Recommended workflow
- Identify the backup software.
- Compare backup-set directories.
- Check the configured retention policy.
- Run its supported pruning operation.
Limits and precautions
Deleting arbitrary backup files can make a chain unrestorable.
Keep a useful record
Record the drive or folder, scan time, application version and the measurement you used. Keep observations separate from proposed changes. If a result leads to a cleanup, record the file owner, backup status and actual free-space change. This makes the result easier to review and helps explain differences in a later scan.
Quick review checklist
| Question | What to record |
|---|---|
| What did you inspect? | The exact volume or folder, not just the PC name. |
| What action is justified? | Run its supported pruning operation. |
| What could go wrong? | Deleting arbitrary backup files can make a chain unrestorable. |
Next steps
If the result is unclear, preserve the current report and narrow the investigation to one folder or application. Make one approved change at a time, then repeat the relevant measurement. Avoid presenting a predicted saving as a measured outcome.
Related guides
- Investigate WSL Storage from the Windows Side
- Investigate Large Mail Archives on Windows
- Review Photo Library Storage Without Losing Originals
- Plan a Useful WizTree CSV Inventory
Download information · How we verify guidance
Sources and verification
- WizTree developer documentation
- WizTree developer FAQ
- WizTree developer download notes
- Microsoft Windows storage guidance
Prepared from public documentation and practical storage-audit reasoning. No hands-on Windows test or independent binary inspection was performed for this publication. Menu names and package requirements can change; check the developer documentation for your installed version.