Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
-
Configure --jsonFormat=canonical flag in export policy.
JSON does not support all data types that are available in BSON. This means that when using JSON there will be a so called "loss of fidelity" of the information.
However, using the --jsonFormat=canonical flag in a mongoexport command will preserve all available BSON data types, so the "loss of fidelity" issue can be completely avoided.Now we plan to export our cloud backups to an AWS S3 bucket. To do this, we would like to set up an export policy to automatically export the snapshots. We could already do this via the API. However, the data is output in…
2 votes -
Allow backup download through PrivateLink
We need the ability to download our backups via PrivateLink connection. Our clusters aren't reachable via VPC peering as we solely use PrivateLink. The existing download capability doesn't support a PrivateLink URL to download our backups through.
1 vote -
Comprehensive Backup Ransomware Protection
MongoDB Atlas needs a modern, comprehensive, secure ransomware protection strategy for its customers. Simply providing the ability to backup a database, and encrypt that database with "bring your own key" is not enough. Below I highlight what I believe are key components of a comprehensive strategy (or at least a good start).
Immutable and Verifiable Backups
Once backups are created, Atlas should provide a facility to ensure the backup remains immutable. Further, Atlas should provide verification that a backup continues to be untouched / unmodified for its entire lifecycle.
Deletion Protection
Atlas should provide enhanced deletion protection for backups. Any…
1 vote -
Disable Specific API's
For certain API's, like the ability to Delete a backup, have the ability for an Owner to disable this API call entirely, to prevent bad actors from being able to destroy a system or even a good actor from unintentionally destroying a system. If a customer has a policy that no backups shall be deleted ever, have the ability to disable this API across the board.
1 vote -
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.6 votes -
Cloud backup is not very much use-full for emergency cases and we are blocked
Hello Team,
This is Raja Selvam,
I would like to get more details on Clod backup.
Lets say suppose i would like to get yesterday's backup from one of the collection.
I do not want to restore the backup into another new cluster.
I do not want to download the backup since my Data will be around 1 TB, Incase if I go for download option this will take 1 day.This solution also not working since we have to load the data to s3.
https://docs.atlas.mongodb.com/backup/cloud-backup/export/Can we have option for cloud backup like legacy backup in feature. We ate…
1 vote -
Allow OpLog Backups in Atlas M0-M5 Shared-Tier clusters running on MongoDB v.5.x
I have a backup process that is taking hourly dumps of the oplog on my production cluster running MongoDB v.5.0.6.
It works fine using older versions of mongodump. However, when I update my tools to any version higher than 100.3.1 (100.4.x and above), my oplog backups fail with the following error:
CMD : 2022-02-16T15:39:03.186-0500 Failed: error creating intents to dump: error counting local.oplog.rs: (Location40602) $collStats is only valid as the first stage in a pipeline.
According to Atlas Support, this issue is limited to M0-M5 clusters and will need to be addressed by the Atlas development team.
Can I ask…
1 vote -
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.
2 votes -
Need granular export details while exporting cloud backup to aws
Right now we get the notification when the cloud backup is successfully exported to AWS S3.
We need some granularity details in the notifications such as no of collections, size of collection/db, etc...
1 vote -
Backup Policy change approvals
The Backup Policy configuration shows a checkbox allowing the altered backup policy to affect all prior backups. The problem with this is that someone could accidentally (or maliciously) delete all prior backups.
This feature request would include implementing some sort of multi level approval prior to enacting said recursive backup policy changes (affecting prior backup snapshots).
4 votes -
Backi
We need the ability to backup every 5 mins, 15 mins is possible
At the moment it's only hourly ?1 vote -
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.
7 votes -
when making backups don't have the banner say "deploying your changes"
I was very confused recently when I logged in and saw the message "We are deploying your changes" despite nobody having made any changes to the cluster. Apparently what was happening was our scheduled backup was happening. This was a really confusing message to be seeing and resulted in a support request to work out what changes were being made.
It would be much better if the message when a scheduled backup was happening was more clear about what is happening and less misleading.
1 vote -
PITR should allow to choose which snapshot to use as base
PITR mechanism does not allow the user to choose which snapshot to use as base before replaying the oplog. Given that Atlas does not validate the snapshots after they have been taken, the user ends up needing to setup their own validation process. That alone is not a problem. However, when one needs to use the PITR mechanism, not being able to select a previously validated snapshot may lead for PITR restores to use unvalidated snapshots.
Either Atlas should enable, uppon choosing, the validation of snapshots right after they are taken, or allow the selection of valid snapshots (snapshots taken…
1 vote -
Delete documents from backups
Allow to delete documents from existing backups based on a query.
When off-boarding customers, we sometime need to delete all of their data, including historical data from backups. Having the ability to clean up those backups, without having to restore, delete, and take a new backup, would be amazing.
1 vote -
Restore snapshots on s3 back to atlas cluster
Currently we store Atlas snapshots on S3 for D.R purposes as well as for compliance reasons.
There was a scenario where an instance was deleted by mistake, and once an instance is deleted all of the atlas managed backup snapshots were gone. In order to restore the Atlas instance we had to do the following:
1) create a new atlas instance
2) restore the snapshot from s3 to a temporary mongodb database and then do a dump and restore in order to migrate the data back into the new atlas instance.
This is a time-consuming process, so if there is…
7 votes -
Recovery after cluster delete
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.
2 votes -
Cloud Manager backups support for Mumbai region(ap-south-1)
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)1 vote -
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.
3 votes -
Monthly backup
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.
1 vote
- Don't see your idea?