Backup owners struggle to balance retention with storage limits
Self-hosters and operations teams need old files and backups removed to control storage use, but they also need enough history to recover from problems they notice late. Current behavior can be hard to tune: deleted OneDrive backups may still occupy quota in the recycle bin, while a fixed 30-day backup retention window may be too short for some users. A related concern is that generated Terraform configuration can unintentionally remove important resources.
For self-hosters and operations teams managing backups and shared storage. Mentioned from Feb 2019 to Apr 2026 on product forums, GitHub, Hacker News and Stack Exchange.
5 different people described this problem in 5 separate discussions.
- Indie fit
- 6.0/10
- Pain
- 6.8/10
- Frequency
- 6.5/10
- Willingness to pay
- 4.5/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
A big difference here is that Backblaze only keeps deleted/changed files for 30 days. Deleted files can go unnoticed for some time, especially if done by a malicious app or ignorant AI. I'd pay that extra few dollars for peace of mind
It would be nice to include an option to not only move the older backups on onedrive to the trashfolder but permanently delete them directly as all deleted backups else first go into the Trash-Folder for at least 30 more days and “eat up” my disc-quota and brings the cloudspace very soon to the limit
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 5 places to find your first customers
- 3 more quotes from people who have this problem
- Current workarounds, existing solutions and risks