David
My feedback
23 results found
-
27 votes
David supported this idea ·
-
237 votes
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.
David supported this idea ·
An error occurred while saving the comment -
2 votes
David shared this idea ·
-
15 votes
Admin mistake! Long Numbers are also still unavailable. Reopening this and I am sorry for the confusion.
David supported this idea ·
-
41 votes
David supported this idea ·
-
3 votes
An error occurred while saving the comment David commented
I would also like to shut off client acces per database in order to give other databases accesibles.
And this option managable with MongoDBAtlas API and terraform client.
David supported this idea ·
-
11 votes
David shared this idea ·
-
5 votes
David shared this idea ·
-
10 votes
David supported this idea ·
-
7 votes
David supported this idea ·
-
144 votes
David supported this idea ·
-
79 votes
David supported this idea ·
-
20 votes
David supported this idea ·
-
26 votes
David supported this idea ·
-
43 votes
David supported this idea ·
-
491 votes
David supported this idea ·
-
7 votes
David supported this idea ·
-
162 votes
David supported this idea ·
-
2 votes
David supported this idea ·
-
46 votes
David supported this idea ·
Hi Andrew,
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 ?
thank you.
regards,
David.