The backup archives can be very large, and if my download is interrupted, without Accept-Range, it is not resumable. A length header is also missing, so the downloader doesn't know the size of the archive.

We are currently looking for a solution to secure our Atlas backups.

Something similar to AWS Glacier Vault Lock [1] or a simple grace period before backups are deleted once and for all would be nice.

It would be amazing to protect the Atlas backups from being deleted.
Currently, if one of our Atlas admins was compromised, the damage for the company would be enormously high. So we need to implement measures against the final deletion of our most mission critical data.

also mentioned in: [2]

[1] https://aws.amazon.com/de/blogs/security/amazon-glacier-introduces-vault-lock/
[2] https://developer.mongodb.com/community/forums/t/is-there-a-vault-lock-for-atlas-backups/11041

When performing a forensic analysis for the purposes of a restore, in order to determine the appropriate point in time when our data was last "sane", it would be awesome if we could start with a point-in-time restoration, and play the journal forward, e.g. performing a bisect on the data.

Allow to create a backup when we want, on every type of cluster (like we could do with mLab plans)

It would be great to have a feature that schedule live migration from a replica set of a PROD cluster to a DEV cluster directly in ATLAS.

The plus of this solution are :
- I dont need a dedicated server to do this job on my side (deploy it, configure it, script it, open network/port, etc ..)
- I will not have to dump the whole databases from the cloud then uploading it afterwards (can be long)
- Gain from outbound price in the cloud (more for you this one)

Hi,

It would be great to have support for yearly backup, including via terraform:
https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/cloudprovidersnapshotbackuppolicy.

Thanks

To speed up recovery after restoring from a snapshot or having a node replaced, it would be nice to have the option to use AWS Fast Snapshot Restore

https://aws.amazon.com/blogs/aws/new-amazon-ebs-fast-snapshot-restore-fsr/

This would allow the disk to have full performance as soon as available.

It would be great to have an alert that notifies you when someone edits the backup policies.

This would be good to validate and everyone to be aware of, because a bad change can cause major problems if it is necessary to restore a backup.

The Legacy Backups have a feature to allow connecting (tunnelling) to a snapshot to query it. This allows querying a database snapshot which is great for quickly inspecting data in the past for troubleshooting. This would be handy to have for the Cloud Backups. With Cloud Backups instead I now have to download a snapshot, load it temporarily on a cluster and remove it when done.

It would be nice and convenient if lower-tier users could have the cloud backup option available (I believe m5 is the smallest but it's $9/month). I use m0 for one of my projects and I know mongodump is an option but I would much rather pay $1/month extra for backup capabilities. This project is quite small and I don't need much resources, but I would like the ability to scedule daily backups for a small fee.

After an incident I may single out a snapshot and decide it is important. At this point I am able to change the retention policy to keep it for a longer time.

It would be useful to also be able to add a note or a description to that snapshot so that I may tell future me why that snapshot was important and what incident it is tied to.

Given how import backups are to an enterprise's business continuity plans, the set of common sense default alerts set by Atlas should include an alert for Cloud Backup on projects with Cloud Backup enabled. Either "CPS snapshot has been stuck in queue for 1 hour" or "Snapshot schedule feel behind by 1 hour" would suffice.

Given how import backups are to an enterprise's business continuity plans, the set of common sense default alerts set by Atlas should include an alert for Cloud Backup on projects with Cloud Backup enabled. Either "CPS snapshot has been stuck in queue for 1 hour" or "Snapshot schedule feel behind by 1 hour" would suffice.

Atlas Legacy Backup used to have digest hash (SHA1 Checksum) on the restore job, but it is currently not available in Atlas Cloud Backup. This feature will be helpful in validating the integrity of the downloaded file.

In one click I would like to copy the exactly one database and put it in another cluster. This is especially useful for debugging.

This would allow us to easily recreate the database from our production cluster and put our staging (or other possible clusters) cluster into an exact state to help replicate issues or bugs.

Many clients download backup snapshots to keep an offline copy of their data either to restore it into their on-prem development environment or to keep an offline copy of their data. At the moment, Atlas does not allow downloading backup snapshots that have customer BYO-KMS encryption enabled.

When I recently attempted to restore a db backup I got a cryptic error message stating "Error: Cluster Not Found"--which was extremely confusing considering that I pressed the restore button in the backup options. After some great tech support, I added my user as project owner and everything worked fine.

Please make the error message clearer in both the Restore and Download backup scenarios.

Two different ideas for this:
-When building a new cluster having the option to build it using a cloud backup snapshot for DR when a cluster is down

-Same idea to restore to a new cluster but from the restore target dropdown IE Restore to New cluster which opens the create a cluster workflow with the cloudbackup snapshot section populated