Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
69 results found
-
Option to restore one or more db from snap to cluster. Right now, it involves manual dump and restore
Currently we can only restore full cluster from backup like snap using GUI interface. If we want to restore one or more specific db, it needs manual dump and restore from backup. if we have an option to restore specific db to cluster through GUI interface, it will be very useful.
164 votesHi all – We are currently developing collection and database-level restores. We expect this feature to be released in CY2025, but will update here once it is launched.
-
Add tunnelling to allow querying Cloud Backup snapshots
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.
59 votes -
GCP Export Cloud Backup Snapshot support
Currently "Export Cloud Backup Snapshot" is a really good feature for off-line backups, but it only supports S3. This is quite limiting for organisations that don't use AWS. It would be really good if it also supported GCP Cloud Storage.
47 votesHi All, As an update we do have this on our roadmap. We are currently working to improve the consistency of sharded cluster exports and then we will tackle Exports to GCP later this year. The best estimate at this time is by the end of this year (2024) to have exports to GCP GA'ed. I will update here if theres a chance that we can deliver that sooner
-
Backup snapshots on a single database or collection
I would like to be able to configure backup snapshots of a single database or collection on a schedule or continuously. This feature would help projects that need snapshots but only on a subset of data. Cluster-level, topology dependent snapshots may not be appropriate or make sense financially for all projects.
38 votes -
Allow users to download backup snapshots from BYO-KMS encrypted clusters
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.
21 votes -
Can you add support for storing the archive data in GCP cloud storage?
The Cold Storage (Archiving) is available only in AWS S3 as of now. Can you please make it available in GCP cloud storage to move all the MongoDB archives?
15 votes -
SHA1 Digest hash for Atlas Cloud Backup Restore
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.
14 votes -
Alert for backup policy changes
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.
12 votes -
Cloud backup for m0 instances
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.
9 votes -
Snapshot cluster and copy
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.
9 votes -
Restore atlas cluster backup to differently encrypted Project
If we take a volume snapshot backup from one project which is encrypted with encryption key A, we need to restore it into another project with Encryption key B .
If we use Live migrate for this, it may take more time than volume snapshot restore.
We need this feature for quicker refreshes of database cluster.8 votes -
Alert for the absence of a snapshot backup policy
It would be great to have an alert option that notifies when there is a cluster configured without a backup policy defined.
This alert option would be helpful to ensure any defined company backup policy is audited and we are notified if a policy does not exist, or if someone accidently removes any defined policies on a give production cluster.
6 votes -
snapshots without indexes
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.
6 votes -
Cloud backup to new cluster
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
6 votes -
Add storage class configuration option to Cloud Backup snapshot Export to S3
Setting the desired value for
x-amz-storage-classheader for the S3 PUT Object for snapshot export so that exported snapshots can be put directly to the desired storage class without any custom lifecycle rules and wait time on S3 side.5 votes -
Backup persistence after termination should be standard
It is odd that snapshots are tied to clusters and lost/destroyed when clusters are terminated. Snapshots have their own retention policies for a reason. Persistence after cluster termination should be the rule, not the exception.
5 votes -
Restored snapshots from a dedicated instance to a serverless instance
I'd like to be able to spin up serverless instances for automatically provisioned dev/QA environments. I'd like to have production data available in them. So I'd like to restore a dedicated instance snapshot to a serverless instance.
5 votes -
Accept-Range for backup download
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.
5 votes -
Add a role or modify Project Cluster Admin role to allow administrators to mange backup
Today you must be Project Owner to manage backup scheduling and retention. This is far more excessive a permission than needed for DBAs to manage backup scheduling and retention. A role or another permission group for administrative tasks would be important for this product.
4 votes -
Select exclusive copy snapshot from different region to restore for testing DR from copy snapshot.
We have "Additional backup policy" feature enabled which will copy our snapshot to other region.As part of DR testing we want to exlusively select copy snapshot in other region to restore to perform DR.In the current cluster I don't see an option specifically to select snapshot from other region.
4 votes
- Don't see your idea?