Originally published on kuryzhev.cloud
A team keeps 40 TB of database dumps and file snapshots in S3, and the monthly bill looks fine until someone schedules a nightly restore into a staging environment on another cloud. Suddenly the line item that never mattered, data transfer out, is larger than storage. That is the situation where R2 vs S3 backups stops being a matter of taste and becomes arithmetic.
Short answer: if your backups are mostly write-once and rarely restored, and the data already lives on AWS, stay on S3 and tier it down with lifecycle rules. If you restore often, restore outside AWS, or serve backup data to several clouds or sites, R2's zero-egress model usually wins. Check three things before you move: where the data is written from, how many full restores you do per year, and whether you need S3-only features such as versioning or a specific compliance lock.
When the R2 vs S3 backups choice matters
Backup storage has an unusual cost shape.…