Hello,
I would like to update everyone on some changes we have made over the last couple of quarters that resolves multiple parts of the overall goal here, in addition to the methods Ben outlined in the past
First, is Import Archive from S3 ( https://www.mongodb.com/docs/atlas/backup/cloud-backup/import-archive/ ) in Atlas. This walks you through how to import an archive from S3 back into Atlas.
In addition to this we now have other protections around cluster and backup deletion protection to protect against human error but also to ensure you can comply with various requirements automatically 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 ( https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Clusters/operation/deleteLegacyCluster ) API ( https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Clusters/operation/deleteLegacyCluster ) , 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.
To protect from accidentally deleting a cluster in general, you can utilize the Termination Protection ( https://www.mongodb.com/docs/atlas/cluster-additional-settings/#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 ( https://www.mongodb.com/docs/atlas/backup/cloud-backup/backup-compliance-policy/ ).
- Backup Compliance Policy allows organizations to configure a project-level policy to prevent the deletion of backups before a predefined period, guarantee all clusters have backup enabled, ensure that all clusters have a minimum backup retention and schedule policy in place, and more.
- With these controls, you can more easily satisfy data protection requirements (e.g., AppJ, DORA, immutable / WORM backups, etc.) without the need for manual processes.
- Please note that the Backup Compliance Policy can not be disabled without MongoDB support once enabled so please make sure to read our documentation thoroughly before enabling.
In addition to Backup Compliance Policy, organizations can also utilize our multi-region Snapshot Distribution ( https://www.mongodb.com/docs/atlas/backup/cloud-backup/snapshot-distribution/ ) to automatically copy backups (snapshots and oplogs) to additional Atlas regions. If your primary cloud experiences a region outage then Atlas will be able to recover with a copied backup from another region, just like any normal restore.
With all of these features, you can automatically protect your data and meet compliance directly in Atlas.
