option to create a final snapshot before deleting a cluster
Today when an Atlas cluster is deleted, all backups/snapshots of this cluster are deleted along with it.
This is especially an issue when working with automation tools like terraform, where a cluster can be deleted by accident easily.
In AWS Aurora Postgres, for example, there is an option to create a "final snapshot" before deleting the cluster.
If this option is enabled for a cluster, whenever a user triggers the deletion of the cluster (either manually, via API, or any other method), a final snapshot will be created, before the cluster is deleted.
This final snapshot is then available independently of the deleted cluster, so in case of accidental deletion, we can create a new cluster based on this snapshot.
This would be a huge security and safety improvement.
Marius
shared this idea
Hello All,
I am pleased to announce that in Atlas you now have an option to retain all backups when terminating an M10+ cluster.
When you terminated a cluster through the Atlas Ui, on the termination confirmation pop up, you will now see an additional toggle labeled "Keep existing snapshots after termination". If you select this option when terminating your cluster, all of your backups for that cluster will be retained.
You can also choose to retain you backups for a cluster when deleting a cluster through the Atlas Administration API. When deleting a cluster through the API, you can include the retainBackups parameter and this will retain all of your backups after termination as well.
You can view or use the backups from a terminated (or other active) M10+ cluster by selecting the "Backup" tab in the left side navigation of the Atlas UI.
At any time before terminating a cluster, you can choose to take an On-Demand Snapshot, if you would like a final snapshot.
To protect from accidentally deleting a cluster in general, you can utilize the Termination Protection setting in Atlas, which when enabled prevents users from deleting any cluster.
In addition to these options, if you would like to protect your backups, in all scenarios, from ever being deleted before the designated retention period has ended, please learn more about our new backup feature called Backup Compliance Policy. This ensures your backups are never deleted early.
-
Kyle
commented
We're now at 2 years since this has been recommended. Where is MongoDB with this enhancement? This is upvoted 71 times.
-
Srinivas
commented
This feature is a must, especially when there is complete automation involved. This will reduce the additional overheads of managing these backup's.
-
Sudarshan
commented
This feature will help a lot in our solution where we are going to use MongoDB atlas.
-
Fulton Byrne
commented
I would even say that backups should be independent of cluster deletion.
-
Ralph
commented
Hi - this in my opinion is critical. We have just had an issue on a development environment where terraform performed a drop and recreate moving from an M5 to an M10. Not only is there no final snapshot, the cluster backups are not available post upgrade.
Doing an upgrade in the UI and then reflecting the change back into TF does a data migration but the this behaviour could really be dangerous.
-
Kyle
commented
Why has there not been any MongoDB response to this? This feedback item was opened almost a year ago and it has 41 votes currently. This is a critical item to prevent a complete and utter disaster to an accidental delete. You definitely should support keeping existing backups for your clusters as the default option and only if you opt out will the backups be deleted.
-
Davy
commented
Totally need that feature ! Could be a life saver.
-
Antoine
commented
We need this feature!
This would be awesome.
For now we are backuping all the backup in Google Cloud Storage. Backuping backup, that's crazy!