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
-
Backup Snapshot Distribution: allow to choose which policies should be copied to other region
Currently we can choose only a policy type (e.g. hourly, daily).
If we have multiple hourly policies with different retention times, we would like to choose which one should be replicated to another region. Currently it would replicate all the policies with hourly schedule.End goal:
We would like to setup a backup policy where the snapshots are retained in the secondary region for one day only (or less if we had hourly option), while the snapshots in primary region are retained for 7 days. For the same hourly schedule.2 votes -
Support for folders with snapshot export bucket
When creating a snapshot export in Atlas, there isn't any support for storing exports in specific folders, i.e. bucketname/mongodbatlas/exportedsnapshots. Instead, the exports have to be stored in bucketname/exported_snapshots.
This creates an issue for posterity, which could in-turn result in data being accidentally deleted.
1 vote -
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 -
Backup Compliance Policy to enforce "Snapshot Distribution"
Backup Compliance policy currently can help with protecting snapshots in other regions using "Keep all snapshots when removing additional snapshot regions" option to prevent users from deleting backups copied to other regions. However we do not have a way to enforce that snapshot backups are copied to all regions where a primary could be elected.
In order to achieve faster RTO having backup snapshots in all regions where a primary can be elected is important. Hence the feature to enforce copying backup snapshots and oplog backups to other regions via backup compliance policy is very important to compliance mandates and…
3 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 -
Support hourly backup every 24 hours, or support Point-In-Time restore without an hourly backup
To have Point-In-Time restore, an hourly backup policy is required.
However, the maximal interval for an hourly backup is every 12 hours.
I would like to take a backup only once every 24 hours, but still have Point-In-Time restore possible.So, please support either PIT-restore without an hourly backup policy in place, or support an hourly backup policy with an interval of 24 hours.
2 votes -
Allow to change defaultWriteConcernSource to global to avoid flipping the flag
Customers experience following error messages due to the defaultWriteConcernSource mismatch between the source and target cluster when restore the snapshot.
Error: Can not restore a snapshot with custom default write concern 1 to a cluster that does not have a custom default write concern.
Error: Can not restore a snapshot with custom default write concern majority to a cluster that does not have a custom default write concern.
Ability to directly change the defaultWriteConcernSource without flipping between w:1 and w:majority will be convenient for the users.
Option location:
Cluster > configuration > Additional Settings >
More Configuration Options > Default…2 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 -
Permit downloading of serverless instance snapshots.
Currently this is not supported. The consequence is that there is no way to restore just a single database or collection from a snapshot. This obviously greatly reduces the value of snapshots.
2 votes -
Read-only access to project snapshots
Create a role that allows less-privileged users to download project snapshots.
Project Owner rights are currently required in order to simply download a project snapshot. Our team needs to pull snapshots in a variety of contexts, for development and offline analysis -- especially from projects associated with our non-production environments -- and we have to harass our administrators each and every time. It's frustrating to everyone involved.
1 vote -
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 -
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 -
Allow turning off backups on serverless and free instances
We have a use case where we would have liked to use a serverless instance but cannot since we cannot disable backups on serverless instances.
We can't enable backups on this specific instance because of data retention restrictions so being able to turn them off completely on serverless and free instances would be ideal.
2 votes -
API to list clusters that has snapshots on it- even deleted clusters
Today we use the API below to list the clusters that exists in a project
GET https://cloud.mongodb.com/api/atlas/v1.0/groups/{GROUP-ID}/clusters?pretty=true
After having the clusters list, we can list the snapshots from one specific clusters using the API:
https://www.mongodb.com/docs/atlas/reference/api/cloud-backup/backup/get-all-backups/
GET https://cloud.mongodb.com/api/atlas/v1.0/groups/{GROUP-ID}/clusters/{CLUSTER-NAME}/backup/snapshots
Now on Mongo Atlas I can delete a cluster and ask not to delete their snapshots. So if I want to use the same functions I can't, because the list of the clusters do not show the clusters that have been deleted but still has snapshots on atlas.
It would be great if the API that lists the cluster also give us…
3 votes -
Restore protection similar to termination protection
A restore protection option similar to the termination protection for clusters.
When a cluster has restore protection enabled, it can't be the target cluster for a restore operation. This will prevent accidental restores to the wrong target cluster from affecting the protected cluster.The motivation is preventing mishaps from affecting critical production clusters.
The UI for selecting the target cluster of a restore operation has you select the cluster from a dropdown and then type in "I Agree". That still leaves you open to mistakenly select the wrong cluster if you aren't paying good enough attention.
The restore protection feature…3 votes -
Provide option to remove hidden node in NVMe clusters
NVMe clusters default to add a hidden node where backups are pulled from. This is due to the reduced durability of NVMe volumes. In cases where durability isn't a concern, I would like to disable backups and remove the hidden node altogether.
The UI currently provides the ability to stop backups by modifying the backup policies (see attachment). However, I cannot remove the hidden node which is simply incurring extra cost.
Obviously there would need to be a major warning provided to the user, but this is not unprecedented in industry. AWS has spot instances that are quite successful.
My…
3 votes -
disabling snapshots
When we disable de snapshot from one cluster, the following message is shown in the same page but it does not appear at the page that shows the changes that are being made
It would be better if this message were also at the second page (as image uploaded)
Please Note: This action is irreversible. Turning off or altering your type of backup will delete all of your existing snapshots immediately. If you want to keep old versions of your data, visit the backup dashboard and download your snapshots
3 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.
48 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
-
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
- Don't see your idea?