Object storage backup costs hinge on retention and deletion controls, not storage rates

A backup alert often reveals a retention design flaw that predates the incident, such as a tenant's stated retention period not matching what the object inventory actually holds. The article argues that comparing scalable object storage for app backups should account for the full lifecycle of data, including recovery points, storage-class transitions, restore reads, and verified deletion, rather than only the headline per-gigabyte price. It recommends tracking logical bytes, changed bytes, recovery-point counts, export reads, and deletion backlog, and alerting on forecast capacity breaches or approaching deletion deadlights instead of simple size thresholds. The author stresses building a workload sheet with consistent units before evaluating vendors such as AWS S3, Azure Blob Storage, and Google Cloud Storage.