Backup and snapshot costs explained: retention, growth, and transfer

Start with a calculator if you need a first-pass estimate, then use this guide to validate the assumptions and catch the billing traps.

Use this page as an internal support guide for backup retention and restore economics. The stronger public-facing parent pages are storage costs and database costs, which usually own the broader search intent. This page stays useful when you specifically need to think through retention ladders, restore testing, DR copies, and backup growth.

1) Retention ladder: operational vs compliance

• Write the policy down explicitly: daily, weekly, monthly, and annual retention.
• Separate operational recovery backups from long-term compliance copies.
• Do not keep everything forever by default just because snapshots feel cheap.

The most common governance mistake is one flat retention policy for every environment and every dataset. Recovery needs, compliance needs, and experiment leftovers should not all share the same retention curve.

2) Backup footprint grows from churn, not just size

• Estimate protected data size and daily change rate separately.
• Convert churn x retention into a steady-state backup footprint.
• Model growth over time instead of assuming the current footprint is stable.
• Tool: snapshot cost calculator

Backup cost surprises usually come from retention windows filling up on fast-changing datasets, not from the existence of one backup copy. Churn is the multiplier people miss.

3) DR copies, restores, and transfer

• Cross-region or cross-account copies duplicate stored footprint and can add transfer charges.
• Restore testing and DR drills add read, restore, or transfer costs depending on provider.
• Manual snapshots created during incidents or migrations can stay behind and become permanent cost leaks.
• Tools: cross-region transfer, egress

4) Review checklist before changing policy

1. List which backups are for short-term recovery and which are for compliance.
2. Find manual snapshots or long-lived copies without an owner.
3. Confirm how often restores are tested and what those tests cost.
4. Check whether cross-region DR copies are priced separately from the primary backup pool.
5. Only then shorten retention or cleanup snapshots.

When this page is useful

• As a focused backup-retention checklist inside a broader storage or database review.
• As an internal handoff page for teams discussing snapshot growth and DR copies.
• As a reminder that restore economics matter, not just stored backup GB.

Related tools

Related guides

Related calculators

FAQ