Cloud Backups should be recoverable even after a cluster delete otherwise they can't really be considered backups. One way to do this would be to allow for automated backup downloads to customer specified cloud provider storage.

Currently Cloud mongo support for backup in below 6 regions only, Can you please start support for the Mumbai region also(ap-south-1).

1) eu-west-1 - Europe (Ireland)
2) ap-southeast-2 - Asia Pacific (Sydney)
3) eu-central-1 - Europe (Frankfurt)
4) eu-west-2 - Europe (London)
5) us-east-1 - US West (N. California)
6) us-west-2 - US East (Ohio)

mongodb doesn't have 7 years backup retention for yearly backup. Please add feature to take yearly backup and enable backup retention for years

For DR strategy, one need to have its backups outside Atlas.
This can be achieved in several ways. Some are:
- Provide APIs to download the current backups and let the customers automate this on their side
- Write backups in the customer provided cloud account (aws s3, azure blob stroage...) My favorite option

I found many ideas related to my needs, but they were too specific. This need is more general: just provide a way to have backups automatically outside of atlas.

Like we can do in Cloud Manager Continuous Backup, We can query a snapshot. This download an .EXE file that will create a tunnel directly to the Backup Storage and allow us to retreive the document that we need (using localhost:27017), without restoring the whole backup, or having a 2nd database, giving access to the developer, ...

It would be great to have the option to save Atlas backup snapshots without indexes. When using TTL indexes, when the data is restored, it is automatically removed because it is expired. Being able to create snapshots without indexes would save a lot of time to the current workaround.

We would like to schedule our monthly backup and 1st Sunday of every month. Currently, this option is not available via the Atlas Console. It gives options like 1st, 2nd, 3rd, 4th...etc of every month but not a specific day like Sunday or Monday. Please consider adding this option as it will be ideal for us to take our monthly backup on a Sunday when the database is not busy.

hourly backup retention. Why minimum a day, so 24 backups stored? For big databases, this is an amount of data and money

This is an important security requirement. Right now Cloud backups only create backups in the same region as the data replica itself. It would be a nice improvement to support backups in different regions in the same country.

If the region is down, there is no way to pull the backups and restore in another region. With multi-region or dual-region, a customer would be able to get access to the backups.

Show Snapshot progress (from provider snapshots) and possibly an ETA in Atlas UI

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