For a game backend, a private object-storage bucket with dated backup keys and a day-based lifecycle rule is a sensible default. Keep database dumps and player-file archives under separate prefixes, expire them after 30 days (or 90 when recovery needs justify it), and let your application own anything that must disappear sooner.
Short answer: object storage works well for backup retention when dated keys and lifecycle deletion are paired with an app-level restore record; it is not a compliance-grade immutable archive.
How should an app set private backup retention with object storage lifecycle rules?
Start with the key layout, because it becomes your operational index. A nightly job might write backups/prod/db/2026-09-08T020000Z.dump and backups/prod/files/2026-09-08T020000Z.tar.zst . A staging run uses backups/staging/ , so a cleanup job cannot accidentally mix environments.…