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.
Agreed, this should receive priority consideration and is a basic function for multi-tenancy; not only for Atlas, but on-prem as well. The queryable backup functionality has limitations, and even then requires a dump / restore to pull a specific database. More in-line with enterprise functionality would be to perform a direct restore for just a specific database
this feature is also important for my company.
Indeed, we have several databases on each our clusters.
We can't use your procedure idea because we want to keep other databases on destination cluster.
We want to restore databases separately because other databases (on the same cluster) are used. Thus we can't delete them.
Another idea is the "deprecated" feature about "queryable backup" (here : https://docs.atlas.mongodb.com/backup/legacy-backup/restore-by-query/ ).
Why this feature is deprecated ?
Is possible to ask for its come back ?
Have you any other idea ?
This is a key feature for us.
We currently use the restore snapshot job to copy our data to our analytics cluster daily through the Atlas API. We want other databases in our analytics cluster to persist throughout these daily copies (hence why copying and deleting the data afterwards is not sufficient).
A manual dump and restore is currently our only option however it's significantly more expensive (cost and implementation time) as we must use a VM as a middleman for the dump and restore commands.
I'd add that if/when this feature gets implemented, the API should be extended so that this feature can be used in a automated pipeline.
Agree that it should be possible to restore single DBs from a snapshot. Multiple DBs in a cluster are not unlikely (otherwise MongoDB Atlas get very expensive).
My understanding is that this was possible in the past and changed with Cloud Provider Backup (snapshots). I am investigating the possibility to use MongoDB Atlas for a big insurance company and consider this as a "Must have Feature".
Are there plans to make this very important feature available again?
We have some guidelines in the green box on this docs page that describe how to speed up a backup restore:
I am going to get this updated to be even more precise: For the fastest possible restore, restore to a cluster in the same Atlas Project, in the same region, with the exact same storage size as that of the cluster the Cloud Backup snapshot was taken from.
If you do this, you will have the fastest possible restore (irrespective of data size) -- from there you can very easily remove any collections/databases you don't need.
we can do that. However, it will take more time to restore and grammatically syncing data may need process to get back to old state.
Hence, restoring a single db should be possibly restored from snap like restoring a cluster. This will give us
- faster restoring of db and applications accessing database will be back quicker
- Reduction in manual effort and faster recovery
- Possibility of easy of maintenance of cluster environment
One option is to simply restore the full backup and then cull everything you don't need -- this can all be driven programmatically. Can you share whether this would work for you?