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.

When I recently attempted to restore a db backup I got a cryptic error message stating "Error: Cluster Not Found"--which was extremely confusing considering that I pressed the restore button in the backup options. After some great tech support, I added my user as project owner and everything worked fine.

Please make the error message clearer in both the Restore and Download backup scenarios.

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

Right now I have to give an admin permission to allow someone on my team to query snapshots from a backup (i.e. downloading the tunnel file).
I don't want to give an admin permission just to allow our data analysts or a developer trying to understand data corruptions to view the database at an older date.

I use Atlas because it's easy to set up, especially with backups. Without this feature, I have to build sync tools with the API to make sure my backups are secure. If someone got into our database and deleted the cluster - the backups are completely lost.

I have customers that would like the ability to retain annual snapshots going back 5 or so years for compliance reasons. Currently, you can do this with monthly snapshots by retaining for 5*12 months, but then you have to store all the monthly snapshots in between.

Provide a per cluster mechanism to shut off client access for restore operations.

We would like the option to have our Atlas backups automatically copied to a 2nd region to support our DR initiative. I realize we could create a live database node in a 2nd region, but that is more costly and complex. Having the backup sync to another region that we can restore off of in case the primary region fails would be simpler and more cost effective.

Is this something that is on your roadmap, and if so, when will it be released?

Thanks!

seems like a potential enhancement for the snapshot schedule to consider cpu/connection/etc load metrics before deciding to run or not

Sorry but this is a must. GRS is a 2 region datacenter backup, LRS only 1. Fire or disaster will take out everything if LRS is used.

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.

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.

When viewing Cloud Provider Snapshot information, all dates are listed in the time zone on the User's profile. However, the date/time to be entered when trying to perform a PIT restore has to be entered in UTC time. This is asking a lot of someone who is probably already really nervous to be able to correctly calculate the difference between their time zone and UTC time.

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!

Add a note in the cluster builder UI where to find the Cloud Provider Snapshot (i.e. Cluster name > Backup tab). Customer who are used to using Continuous backup might not realize that there's a difference and panic when they see their backups 'gone' (especially if they have multiple clusters in a project, some of which still use Continuous backup).

This is a feature request for ability to stop the snapshot restore in the Atlas UI

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.