Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
74 results found
-
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 -
hourly backup retention
hourly backup retention. Why minimum a day, so 24 backups stored? For big databases, this is an amount of data and money
1 vote -
Option to take a Cloud Backup snapshot on destination cluster before restoring if Cloud Backup is enabled on it
An option should be provided to allow a user to take a snapshot of the destination cluster of a Cloud Backup restore before the restore is performed so that they can easily "revert" the restore if they need to (by just requesting a restore using the snapshot that was taken just prior).
It's possible to be in a situation where you've selected an incorrect snapshot for restoring or that you'd supplied the incorrect cluster for the snapshot to occur (this is less likely to happen in the UI than it is to happen programmatically via the API). Taking a snapshot…
1 vote -
take snapshots off of the activity tab for maintenance.
When I select the maintenance filter on the activity feed all the daily snapshots show up. I feel like there should be a backup screen that shows all the snapshots on the activity feed. this would make the maintenance screen more precise and relevant.
. The maintenance screen should only show what software maintenance goes on the atlas clusters. This should also include all the release fixes. so, I do not have to go to your
https://docs.mongodb.com/manual/release-notes/software releases page.It is very hard to tell what maintenance will be applied in a given time period. We have timeframes to apply…
1 vote -
CronJob Live migration to second cluster in second project
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)1 vote -
Provide a default alert for projects using Cloud Backup
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.
1 vote -
Provide a default alert for projects using Cloud Backup
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.
1 vote -
Dynamically Calculate Timestamp Limits for Continuous Backup Restore (via OPLOG Timestamp)
Currently, you can put in a OPLOG TIMESTAMP value that exceeds the maximum / minimum value for the Continuous Backup Time Window.
For example, on the "Date & Time" tab of the "Point in Time Restore" menu, you are given a warning that specifies: "You can only restore to a specific point in time after MM/DD/YYYY HH:MM"
This should be added to the "OPLOG TIMESTAMP" tab where a warning could be given such as "You can only restore to a specific point in time after XXXXXXXXXX" (Epoch time).
As such, you should enforce data form validation so that a user…
1 vote -
regular
Restore snapshots to different clusters.
I have a staging environment cluster whose data I'd like updated daily with anything new from my production cluster.
Currently I do a dump and restore, but this is slow because it gets piped externally.
Ideally I'd be able to restore a production snapshot to my staging cluster through a script running on a cron. Whether than is API or CLI doesn't matter.
1 vote -
Add colors to Backup times
Hi can I suggest a feature to the developers? Can the developers add colors to the Backup times? Because I have accidentally Backup an instance at 3:21 PM instead of a 3:21 AM I wanted. The colors will definitely help prevent such accidents from happening. It would also be nice if the developers can ensure that Backup times are not the same for AM and PM. Thanks!
1 vote -
Ability to stop the snapshot restore in the Atlas UI
This is a feature request for ability to stop the snapshot restore in the Atlas UI
1 vote -
Add more details on backup policy changes in Atlas activity feed
In Atlas when you search for "Cloud provider snapshot schedule updated for cluster" in the project's Activity page, it doesn't provide any details on schedule policy changes information, the customer have to call the snapshot schedule API to get the policy schedule change information. However, the API call output still doesn't have any history change information for audit purpose.
Please consider add that information to the Atlas activity feed page.
1 vote -
Ability to download backups without requiring a token with write permissions
I want to automate downloading the most recent continuous backup snapshot to a local machine nightly. The guys on your intercom help chat were pretty helpful in pointing me at
delivery.urlhere:https://docs.atlas.mongodb.com/reference/api/restore-jobs-create-one/
But I was surprised that in order to download a backup, I need to use a token with write permission. It would be great for security reasons if the machine I use to download backups could do so without needing to have a write token.
1 vote -
Improve the Interface for backup menu
Backup options display in different places for M5 and M40 instances. I think this is misleading and not consistent. Also, the form for backup restoring for M5 instances may easily lead to a catastrophe. That's because even when you explicitly enter a specific cluster, you can still select another cluster to restore to. Here is a video that I've recorded to explain my point of view:
https://www.loom.com/share/4d747b225c964af9809e0c8813a9b0811 vote
- Don't see your idea?