MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

Add new feedback Subscribe
Status Submitted
Categories Billing & Account Management
Created by Guest
Created on Sep 11, 2024

RELATED FEEDBACK

More information about snapshots and oplog sizes for backup optimization

Backup optimizations always involve costs. However, currently, we only have access to the number of GB we are consuming. I'm not able to tell which snapshots are full or incremental. Also, when Continuous Backup is enabled, I can't see how much I'm spending on oplogs and snapshots. Without that information, I can't figure out if it would be better to reduce the Point-in-Time window, delete old snapshots, or change the snapshot policy. I went through these documentation, but I still miss the actual sizes of snapshots and logs to make the correct decision. - https://support.mongodb.com/article/000021504 - https://support.mongodb.com/article/000021099
  • Steve Hand
    Jan 28, 2026

    I have attempted to replicate the storage cost calculation using MongoDB's documentation. I can get close but I cannot replicate the cost calculation. MongoDB Support has confirmed that they do not expose the data used in the storage calculation; therefore, we cannot replicate that calculation. Why would we want to you ask? I was looking to determine that cost of each backup frequency so that I could inform the internal consumer of the consequences of retaining yearly backups for a year for example.

    It's seems like a bug / defect to have a cost calculation (for storage) that does not work, and will never work. Why not just reveal the underlying numbers so that we can do our what-if calculations.

    Reply