MongoByte
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.
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.
|
What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. |
When testing restore procedures, we need to restore a snapshot to a new cluster. In order to so, one must create a cluster first with the same config than the source cluster. The restore only suceeds when the configs match. This is a very cumbersome process. |
|
What would you like to see happen? Describe the desired outcome or enhancement. |
Restore a snapshot to a new cluster with the same config as the source cluster, with one click/API call |
|
Why is this important to you or your team? Explain how the request adds value or solves a business need. |
It would greatly reduce our efforts of restore testing. |
What steps, if any, are you taking today to manage this problem? |
@Guest We’re currently testing a new cluster cloning capability in Atlas to make it easier to create new environments based on an existing cluster. This feature allows you to clone a cluster’s configuration, and optionally its data, into a new cluster within the same project or across projects.
As part of this workflow, you can restore data into the new cluster from the latest snapshot or choose from compatible snapshots if backups are enabled on the source cluster.
For this initial phase, cloning will be offered as a separate workflow, and the existing restore flow will remain unchanged. We’re starting here so we can learn how customers use the feature and gather feedback before exploring deeper integration with restore workflows.