# Continuous backup enabled on non-production MongoDB Atlas clusters Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/continuous-backup-enabled-on-non-production-mongodb-atlas-clusters MongoDB Atlas offers two backup mechanisms for dedicated clusters: Cloud Backups (scheduled snapshots using the underlying cloud provider's native... By: Hierony Manurung Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Continuous Backup Enabled on Non-Production MongoDB Atlas Clusters The short version MongoDB Atlas offers two backup mechanisms for dedicated clusters: Cloud Backups (scheduled snapshots using the underlying cloud provider's native snapshot functionality) and Continuous Cloud Backup, which adds point-in-time recovery by continuously capturing the cluster's oplog - a log of all write operations. [Hierony Manurung](https://www.linkedin.com/in/hierony-manurung-53598168) Cloud FinOps @ Dkatalis MongoDB Atlas service [MongoDB Atlas](https://www.pointfive.co/efficiency-hub/cloud-services/mongodb-atlas) Category [Databases](https://www.pointfive.co/efficiency-hub/service-category/databases) Reference CER-0326 Type Inefficient Configuration ## Explanation Why the waste happens and who it affects. Continuous Cloud Backup is an optional add-on for M10+ dedicated clusters that stores both snapshots and oplog data, enabling restoration to any specific second within a configurable restore window. While this capability is critical for production workloads with strict Recovery Point Objectives (RPOs), it provides limited value on development, testing, or staging clusters where data is typically transient, synthetic, or easily reproducible. This inefficiency commonly arises when organizations apply infrastructure-as-code templates or centralized backup policies uniformly across all environments without differentiating between production and non-production recovery requirements. Because Continuous Cloud Backup continuously captures and stores oplog data in object storage, storage charges accumulate based on both the configured restore window and the volume of write activity on the cluster. Clusters with moderate to high write throughput generate proportionally larger oplogs, amplifying the cost impact. MongoDB's own architecture guidance explicitly recommends against enabling backup for development and test environments, recognizing that the cost of continuous oplog storage rarely justifies the recovery benefit for non-critical workloads. ## Billing model The pricing dimensions that drive this cost. MongoDB Atlas backup storage is billed separately from cluster compute costs. The key billing dimensions are: - Backup storage is charged per GB-month based on the total size of retained snapshots and oplog data, with rates varying by cloud provider and region - Continuous Cloud Backup adds incremental costs on top of standard Cloud Backup by storing oplog data in addition to snapshots - billing is based on the combined size of snapshots plus oplog storage - Backup charges appear as daily line items (GB-days) but represent monthly storage charges - longer restore windows result in larger oplog retention and higher costs - Write-heavy clusters generate more oplog data, directly increasing continuous backup storage costs regardless of whether point-in-time recovery is ever used Backup costs can approach or equal the total storage capacity of the cluster volume depending on how the underlying cloud provider stores snapshots and the configured retention policies. For Continuous Cloud Backup specifically, Atlas calculates costs based on the combined total of snapshot and oplog size, with tiered pricing that applies after an initial free allowance (see [Cluster Configuration Costs](https://www.mongodb.com/docs/atlas/billing/cluster-configuration-costs/) for current rates and examples). ## How to detect 6 checks to find it in your estate. - Identify all MongoDB Atlas clusters designated as development, testing, staging, or other non-production environments - Review whether Continuous Cloud Backup (point-in-time recovery) is enabled on any non-production clusters - Assess whether the data stored in non-production clusters is transient, synthetic, or reproducible from other sources, reducing the need for granular recovery - Evaluate the write activity levels on non-production clusters to understand the relative oplog storage cost being incurred - Confirm whether backup configurations align with documented environment criticality and recovery requirements for each cluster tier - Review whether a Backup Compliance Policy is enforcing Continuous Cloud Backup across all clusters, including non-production environments where it may not be warranted ## How to fix 6 ways to remove the waste. - Disable Continuous Cloud Backup on non-production clusters where point-in-time recovery is unnecessary - note that disabling this feature permanently deletes all existing oplog data, though snapshots remain intact - Retain standard Cloud Backup (scheduled snapshots) on non-production clusters where basic disaster recovery is still required, adjusting snapshot frequency and retention to match the environment's actual recovery needs - For truly ephemeral development environments where data recovery is not critical, consider disabling backups entirely on M10+ dedicated clusters to eliminate backup storage costs altogether - Differentiate infrastructure-as-code templates and backup policies by environment tier, ensuring that Continuous Cloud Backup is reserved for production or compliance-critical workloads - If a Backup Compliance Policy is enforcing point-in-time recovery across all clusters, note that the policy applies to every cluster in the project and individual clusters cannot be excluded - move non-production clusters to a separate project without the policy, or have the policy's designated security or legal representative request a change through MongoDB Support - Establish periodic reviews of backup configurations across all clusters to detect and correct policy drift as new environments are provisioned ## Documentation Vendor references for pricing and configuration. - [Guidance for Atlas Backups - Atlas Architecture Center mongodb.com](https://www.mongodb.com/docs/atlas/architecture/current/backups/) - [Recover a Point In Time with Continuous Cloud Backup mongodb.com](https://www.mongodb.com/docs/atlas/recover-pit-continuous-cloud-backup/) - [Dedicated Cluster Backups mongodb.com](https://www.mongodb.com/docs/atlas/backup/cloud-backup/dedicated-cluster-backup/) - [Manage Backup Policies mongodb.com](https://www.mongodb.com/docs/atlas/backup/cloud-backup/configure-backup-policy/) - [Configure a Backup Compliance Policy - Atlas mongodb.com](https://www.mongodb.com/docs/atlas/backup/cloud-backup/backup-compliance-policy/) - [Cluster Configuration Costs mongodb.com](https://www.mongodb.com/docs/atlas/billing/cluster-configuration-costs/) - [Configure Additional Settings (Backup Options) mongodb.com](https://www.mongodb.com/docs/atlas/cluster-additional-settings/) - [MongoDB Atlas Pricing mongodb.com](https://www.mongodb.com/pricing) - [Atlas Cluster Sizing and Tier Selection mongodb.com](https://www.mongodb.com/docs/atlas/sizing-tier-selection/) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - MongoDB Atlas CER-0532 ### [Compute Auto-Scaling Disabled or Bounded at Launch Tier on MongoDB Atlas Clusters](https://www.pointfive.co/efficiency-hub/inefficiencies/compute-auto-scaling-disabled-or-bounded-at-launch-tier-on-mongodb-atlas-clusters) Atlas compute auto-scaling moves a dedicated cluster between a minimum and maximum tier based on sustained CPU and memory usage, so clusters with daily or weekly load cycles can run on a smaller tier outside their peaks. In the Atlas UI,... Databases - MongoDB Atlas CER-0531 ### [Overprovisioned MongoDB Atlas Cluster Tier](https://www.pointfive.co/efficiency-hub/inefficiencies/overprovisioned-mongodb-atlas-cluster-tier) A dedicated MongoDB Atlas cluster is billed per hour for each data-bearing node at the rate of its cluster tier (M10, M30, M50 and so on), and the tier fixes the node's RAM, CPU, default storage and storage speed. A replica set pays for... Databases - MongoDB Atlas CER-0534 ### [Non-Production MongoDB Atlas Clusters Running When Not in Use](https://www.pointfive.co/efficiency-hub/inefficiencies/non-production-mongodb-atlas-clusters-running-when-not-in-use) Dedicated Atlas clusters are billed per hour for every data-bearing node whether or not any application is connected. Development, test, QA and demo clusters are typically used during working hours or for the length of a project, yet they... Databases --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.