74 results found

1. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Backup  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Backup  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. snapshot

   Show Snapshot progress (from provider snapshots) and possibly an ETA in Atlas UI

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Backup  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Add editable description to a snapshot

   After an incident I may single out a snapshot and decide it is important. At this point I am able to change the retention policy to keep it for a longer time.

   It would be useful to also be able to add a note or a description to that snapshot so that I may tell future me why that snapshot was important and what incident it is tied to.

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Backup  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Allow "Project Data Access Read Only" to retrieve restore links.

   Allow "Project Data Access Read Only" to retrieve restore links. Currently, to retrieve a restore link from an Atlas cluster you must be a Project Owner.

   In the current version to take the link to the snapshot we need to use Restore Jobs part of the API. Problem is that the same POST endpoint is used for the restore job which can do changes in the system and needs Owner level of the access and to generate link to the stream with the snapshot data. This second type of the job should not need so big access level as should only need Project Data Access Read Only type of the access.

   Allow "Project Data Access Read Only" to retrieve restore links. Currently, to retrieve a restore link from an Atlas cluster you must be a Project Owner.

   In the current version to take the link to the snapshot we need to use Restore Jobs part of the API. Problem is that the same POST endpoint is used for the restore job which can do changes in the system and needs Owner level of the access and to generate link to the stream with the snapshot data. This second type of the job should not need so big access level as should… more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Backup  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. 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

   https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Clusters/operation/listLegacyClusters

   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 those clusters that have been deleted (at list the ones that still has backups on Atlas).

   We use these APIs to be able to migrate our snapshots for a Google cloud storage. So not having this option for the clusters that have been deleted causes problems if we need to migrate snapshots from old clusters.

   Today we use the API below to list the clusters that exists in a project

   https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Clusters/operation/listLegacyClusters

   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… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Backup  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. 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 use case involves pulling data from Kafka, making it queryable, and storing it for a short period of time (TTL indexed). It's not the end of the world if this data goes away because the nature of the data is such that useful data will come again.

   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… more

   •  

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Backup  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Backup  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Copy/move snapshots from a source to a target cluster

   It is recommended that restoring a cluster must either:
   1) Restore to a new Atlas cluster and reconfigure your application to use that new cluster once the new deployment is running, or,
   2) Ensure that the target Atlas cluster cannot receive client requests while you restore data.
   (src https://www.mongodb.com/docs/atlas/backup/cloud-backup/restore/#prerequisites)

   While doing a PIT restore with the source and target cluster being the same, our clusters have gone into a "down" state 3 times due to obscure errors, opslog not being large enough, or writes happening to the cluster during restore.

   We would like to take the safer route of always restoring to a new cluster.

   However, in doing so we lose the Atlas snapshots and possibly opslog data.

   Feature ask: Ability to copy or move snapshots from a source cluster to a target cluster. This operation would take place after the primary restore completes, if needed.

   A similar feature was asked here, but not exactly the same thing: https://feedback.mongodb.com/forums/924145-atlas/suggestions/44074839-restore-snapshots-on-s3-back-to-atlas-cluster

   It is recommended that restoring a cluster must either:
   1) Restore to a new Atlas cluster and reconfigure your application to use that new cluster once the new deployment is running, or,
   2) Ensure that the target Atlas cluster cannot receive client requests while you restore data.
   (src https://www.mongodb.com/docs/atlas/backup/cloud-backup/restore/#prerequisites)

   While doing a PIT restore with the source and target cluster being the same, our clusters have gone into a "down" state 3 times due to obscure errors, opslog not being large enough, or writes happening to the cluster during restore.

   We would like to take the safer route of… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Backup  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Allow instant backup on every type of cluster

    Allow to create a backup when we want, on every type of cluster (like we could do with mLab plans)

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Backup  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Enable AWS EBS Fast Snapshot Restore (FSR) on Atlas

    To speed up recovery after restoring from a snapshot or having a node replaced, it would be nice to have the option to use AWS Fast Snapshot Restore

    https://aws.amazon.com/blogs/aws/new-amazon-ebs-fast-snapshot-restore-fsr/

    This would allow the disk to have full performance as soon as available.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Backup  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Permission level to query snapshots

    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.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Backup  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Provide a granular mechanism to disconnect and disable all active sessions during a planned maintenance.

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

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Backup  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Smart backup scheduler (deferring snapshot backups X minutes based on load metrics)

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

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Backup  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Use the User's Profile Time Zone for PIT Restore

    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.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Backup  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Provide size (in bytes) in `GET /groups/{GROUP-ID}/clusters/{CLUSTER-NAME}/backup/snapshots` Public API call for each `snapshotId`

    What is the problem that needs to be solved? Provide size (in bytes) in GET /groups/{GROUP-ID}/clusters/{CLUSTER-NAME}/backup/snapshots Public API call for each snapshotId

    Why is it a problem? (the pain) You're doing your own automation with manual restore, and you can't programmatically know the actual filesize of .tar.gz file you'll be downloading for each snapshotId listed in GET /groups/{GROUP-ID}/clusters/{CLUSTER-NAME}/backup/snapshots Public API call until you actually download .tar.gz file for each snapshotId.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Backup  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. 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 also makes backup compliance policy feature comprehensive/consistent covering all backup related features offered by Atlas.

    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… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Backup  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. 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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Backup  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. 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 Write Concern

    Thanks.

    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… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Backup  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Add storage class configuration option to Cloud Backup snapshot Export to S3

    Setting the desired value for x-amz-storage-class header 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.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Backup  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close