Skip to content

Brian

My feedback

5 results found

  1. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Brian shared this idea  · 
  2. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Brian shared this idea  · 
  3. 59 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    16 comments  ·  Atlas » Backup  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Brian commented  · 

    This is also a very important feature for us; was disappointed to see this regression in backup functionality at Atlas.

    Brian supported this idea  · 
  4. 164 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    37 comments  ·  Atlas » Backup  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hi all – We are currently developing collection and database-level restores. We expect this feature to be released in CY2025, but will update here once it is launched.

    An error occurred while saving the comment
    Brian commented  · 

    I would also like to suggest restoring the "queryable backup" functionality. We often use this to help customers that accidentally delete data, and diagnose issues by looking at the past state of the database. The removal of legacy backups in 4.2+ is what has kept us from upgrading beyond 4.0.

    Brian supported this idea  · 
  5. 13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Timeout was increased from 60 seconds to 90 seconds. There aren’t currently plans to increase it further, but keeping the issue open in case it needs it be looked at again in the future.

    Brian supported this idea  · 

Feedback and Knowledge Base