Backup Cost Optimization

Parent: MongoDB Atlas Cost Optimization · Published reference · snapshot 2026-10-15

Depth-first rabbithole dossier for Backup Cost Optimization; source-anchored research pack.

These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.

How it works

[low] Point-in-Time (PIT) backups are billed based on disk space occupied by the internal oplog plus the cloud backup snapshot size, and longer backup windows result in larger oplogs and higher costs. Sources: https://www.mongodb.com/docs/atlas/billing/cluster-configuration-costs.md [source]
[high] Deleting a snapshot does not remove data referenced by other snapshots; unique data is only deleted when all snapshots referencing it are deleted, so deleting a snapshot may not reduce storage costs if data is still referenced. Sources: https://www.mongodb.com/docs/atlas/billing/cluster-configuration-costs.md, https://docs.aws.amazon.com/ebs/latest/userguide/ebs-deleting-snapshot.html [source]
[low] Backup-related alerts are raised when a restore fails, a fallback snapshot fails, a regular backup fails but a fallback snapshot succeeds, too much time has passed since the last successful snapshot, or a snapshot hasn't been taken over the configured period. Sources: https://www.mongodb.com/docs/atlas/reference/alert-conditions.md [source]

Measurements and reference values

[low] Atlas can bill backup storage up to the total volume capacity (e.g., 4 TB) even if backups occupy less space (e.g., 500 GB) because cloud providers may report snapshots as occupying full volume capacity. Sources: https://www.mongodb.com/docs/atlas/billing/cluster-configuration-costs.md [source]
[low] For Continuous Cloud Backup on an AWS US_EAST_1 cluster with a combined snapshot and oplog size of 115 GB, the first 5 GB are free, 95 GB are billed at $1.00/GB and 15 GB at $0.75/GB, giving $106.25 per month. (verified as of 2026-10-15) Sources: https://www.mongodb.com/docs/atlas/billing/cluster-configuration-costs.md [source]

Problems, failure modes and limitations

[low] You cannot delete snapshots of the root device of an EBS volume used by a registered AMI, even if the AMI is deprecated or disabled, nor can you delete snapshots managed by AWS Backup using Amazon EC2. Sources: https://docs.aws.amazon.com/ebs/latest/userguide/ebs-deleting-snapshot.html [source]

Comparisons and alternatives

[low] Extending backup retention beyond the default 24-hour window in Atlas Infinite results in billing for additional backup storage consumed by retained snapshots or incremental changes, billed as backup rather than cluster storage. Sources: https://www.mongodb.com/docs/atlas/billing/atlas-infinite-costs.md [source]

Facts and statements

[medium] To reduce costs, disable continuous backups for non-critical clusters or lower backup frequency for clusters storing less critical data, as continuous backups are recommended only for production applications at the most critical data tier. Sources: https://www.mongodb.com/docs/atlas/billing/billing-breakdown-optimization.md, https://www.mongodb.com/docs/atlas/architecture/current/cost-saving-config.md [source]
[low] Enabling Additional Backup Copies in other regions incurs costs for approximately twice the storage if copying all backups to one additional region, plus cross-region data transfer fees. Sources: https://www.mongodb.com/docs/atlas/billing/cluster-configuration-costs.md [source]
[low] Atlas might retain more than one full snapshot per replica set or shard (raising backup storage use and cost) after a node or region failover, a cluster configuration change (tier, storage volume, IOPS), a region priority change in a multi-region cluster, cloud provider maintenance, or a topology change such as adding a shard. Sources: https://www.mongodb.com/docs/atlas/billing/cluster-configuration-costs.md [source]
[low] Atlas Infinite includes 24 hours of continuous cloud backup at no additional cost, meters backup hourly in GB-hours, and bills backup storage as a separate dimension independent of compute and primary storage. Sources: https://www.mongodb.com/docs/atlas/billing/atlas-infinite-costs.md [source]
[high] Atlas Cloud Backup bills retained snapshot storage per GB-month, with rates varying by cloud provider and region, while displaying charges as GB days without duplicating daily line items. Sources: https://www.mongodb.com/docs/atlas/billing/cluster-configuration-costs.md, https://www.pointfive.co/efficiency-hub/cloud-services/mongodb-atlas [source]
[low] Atlas charges $0.125 per GB for data exported to AWS S3, Azure Blob Storage, or Google Cloud Storage buckets, plus data transfer costs, and charges $0.01 per hour to maintain AWS PrivateLink connections for exports. Sources: https://www.mongodb.com/docs/atlas/billing/cluster-configuration-costs.md [source]
[high] Atlas applies a default backup policy to Cloud Backup-enabled clusters on creation, which is generous: snapshots every 6 hours (every 12 on NVMe clusters) kept for 7 days, plus daily snapshots. Sources: https://www.mongodb.com/docs/atlas/billing/cluster-configuration-costs.md, https://www.pointfive.co/efficiency-hub/cloud-services/mongodb-atlas [source]

Related concepts

Backup — is a part of Backup Cost Optimization
Cost — is a part of Backup Cost Optimization

Children

No children recorded.

← the whole tree · 3D view· how to read this page