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
247 VOTE
Status Started
Categories Atlas Backups
Created by Guest
Created on Apr 30, 2020

RELATED FEEDBACK

Option to restore one or more db from snap to cluster. Right now, it involves manual dump and restore

Currently we can only restore full cluster from backup like snap using GUI interface. If we want to restore one or more specific db, it needs manual dump and restore from backup. if we have an option to restore specific db to cluster through GUI interface, it will be very useful.
  • ADMIN RESPONSE
    Oct 18, 2025
    Hi all – We are currently developing collection and database-level restores. We expect this feature to be released in CY2025, but will update here once it is launched.
  • Mallikarjun Kantu
    Apr 30, 2026

    Yes, even allowing the backup of single database using the snapshot feature would be highly useful. When we take mongodump from prod, it will significantly put load on the source database.


    Reply
  • Guest
    Mar 26, 2025
    This is very critical for us. Are there any updates about the roadmap?
    Reply
  • Guest
    Mar 26, 2025
    The only way to restore an individual collection is restore the whole backup from a snapshot to a new cluster. Then use mongodump tool to get the collection information and restore it in the production cluster. Deploy a new feature to restore individual collections from a MongoDB Atlas snapshot will be worthy.
    Reply
  • Matthew Haught
    Oct 7, 2024
    This is absolutely crucial.
    Reply
  • Guest
    Sep 27, 2024
    This is very very critical for us.. PITR is mainly concerned with granular level ( db level, collection level).
    Reply
  • Guest
    Sep 5, 2024
    This is also crucial for us. The option to restore just one collection - or even just a limited amount of data from a collection is crucial. The current option to just restore and replace everything is not feasible for many scenarios.
    Reply
  • Guest
    Aug 27, 2024
    It's a key core feature for us, bumping as well.
    Reply
  • Geoffrey Céré
    Aug 26, 2024
    I vote for this feature again. This feature is very useful in the context that we need to recover or revalidate the contents of a database at a specific time without having to recover the entire cluster. Saves time and money. Hoping that this time will be the right one.
    Reply
  • Guest
    Aug 20, 2024
    I'm bumping this, as perhaps after 4 years, someone will check this out.
    Reply
  • RuthvikReddy Anumasu
    Aug 20, 2024
    Hi all, There used to be a queryable backup option back in the day, Would love to see if it can be brought back! This is a key feature that is required !!!
    Reply
  • Guest
    Feb 14, 2024
    Upvoting, because a large health insurance client is specifically requesting this feature.
    Reply
  • Guest
    Oct 13, 2023
    agree, feature (specify specific database or collection) it was requested by our customer to optimize cost and time to take/restore backup.
    Reply
  • Guest
    Jul 21, 2023
    Current process of restoring a full cluster snapshot requires a lot of time (which is critical during DRP) and resources. It also very brittle due to a number of manual steps required. Having a possibility to restore specific collections would simplify the process significantly.
    Reply
  • Guest
    Apr 21, 2023
    This would be a very useful capability to have.
    Reply
  • Guest
    Apr 21, 2023
    This feature would really help smoothen out DRP procedures. Upvoted!
    Reply
  • Guest
    Apr 20, 2023
    This would be a great feature to have.
    Reply
  • Guest
    Apr 20, 2023
    This would be a very useful feature for us.
    Reply
  • Guest
    Feb 27, 2023
    Upvoting the request, received the feedback from Customer that this feature would be very useful
    Reply
  • Sanket Gandhi
    Dec 23, 2022
    This is important feature request to have backup at collection level. Everybody does not need snapshot of the entire database which could be of very large size and If I want to restore specific collection then there is a long process of getting rid of all non-required collections.
    Reply
  • Guest
    Oct 18, 2022
    I second this request. Due to the backup being a full cluster snapshot, including oplog and other internals, its size is much larger than our actual data. Being able to just backup the contents of one or more databases would lead to smaller backups that are likely also faster to restore.
    Reply
  • Load older comments
  • +147
32 MERGED

Feature Request - MongoDB Atlas Restore individual collections

Merged
The only way to restore an individual collection is restore the whole backup from a snapshot to a new cluster. Then use mongodump tool to get the collection information and restore it in the production cluster. Deploy a new feature to restore ind...
Guest over 1 year ago in Atlas Backups Started
1 MERGED

Add functionality to restore only a specific collection

Merged
At this time the Cloud Backup snapshot restore completely wipes the destination. I would like to have a function to restore only a specific collection.
Guest almost 4 years ago in Atlas Backups Started
18 MERGED

Ability to restore a single database on a cluster

Merged
Hello, The Atlas portal/API offers the ability to restore a complete database instance from snapshot or restore point. However the scope of this restoration covers the entire instance. It would be a great asset to be able to restore a simple dat...
Geoffrey Céré almost 4 years ago in Atlas Backups Started