Verifying Daily Backup Retention on S3-Compatible Object Storage With Four Metrics
A plugin marketplace keeps product images for every vendor and runs nightly backups plus on-demand tenant exports, with 30-day daily and 90-day monthly retention. The author argues that a retention rule failing silently is more dangerous than a backup job failing loudly, since teams often only notice through invoices or vendor complaints. Instead of having the application delete old objects, the bucket's lifecycle rules handle expiry while the app runs one daily check comparing bucket contents against those rules. That check relies on four metrics: objects past retention, newest object age per prefix, total bytes per prefix, and denied export requests. The author recommends keeping deletion and verification in separate code paths and adding a one-day grace period before alerting on expired objects, because expiry is asynchronous.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in