Skip to content

Ops Tools

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

40 results found

  1. On demand snapshots in Ops Manager

    Allow the possibility of performing a snapshot on-demand.

    Usually the snapshot time ends too far away in time after configuration changes of the backup job (i.e: changing the block size). For testing purposes it would make sense to allow performing a snapshot on-demand to get it generated and proceed with further testing/tuning if required.

    79 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

    6 comments  ·  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)
  2. Allow Ops Manager users to move/migrate backup job snapshots from one S3 bucket to a different S3 bucket

    Ops Manager users with S3 blockstores may need to move snapshots and backup jobs to a new S3 bucket. For MongoDB blockstores, this is accomplished using a groom.

    Move Blocks to a Different Blockstore
    https://docs.opsmanager.mongodb.com/current/core/administration-interface/#groom-priority-page

    This feature request is to provide the same feature to groom backup snapshots/jobs to a new bucket for S3 blockstores.

    39 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

    3 comments  ·  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)
  3. Provide recurring/daily reporting on backup status from Ops Manager

    Ops Manager should generate a recurring/daily report of the status of all backups. This report should include at least a list of successful snapshots, a list of unsuccessful snapshots (over the configured reporting period), and the latest successful snapshot for each deployment being backed up. Additionally, this report may include resource availability such as storage available for future snapshots.

    35 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

    5 comments  ·  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)
  4. Add support for virtualization volume management in Ops Manager Backup snapshots and restores.

    Streaming snapshots during a restore from a blockstore out to the MongoDB Agent cases the RTO (recovery time objective) to grow linearly with the compressed datasize in the largest shard/RS of the snapshot. The RTO of an Ops Manager restore could be very significantly improved by leveraging volume management infrastructure (such as from VMWare) to restore previously acquired snapshots as virtual filesystems (volumes).

    22 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

    0 comments  ·  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)
  5. Automated restores between multiple Ops Manager deployments

    Ability to utilize API and/or UI to restore a snapshot downloaded from one Ops Manager deployment to a separate distinct Ops Manager deployment.

    Some environments require separation of Production and Staging systems, including Ops Manager deployments. It is desirable to use Production data in some testing scenarios. Currently the data has to be loaded or restore manually.

    21 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

    2 comments  ·  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)
  6. GUI for Queryable Snapshots

    It would be good to have a GUI created for the queryable snapshot interface so less experienced users, that may not have any mongod experience, can successfully restore a collection/document without additional training.

    Ideally, the feature allows for the creation of some subset of documents using a query building tool (even collection level would be acceptable) that can then be pushed to a target environment automatically or pushed to a mongodump file that can be used as a restore tool later. Their primary concern is just to ensure that individuals without direct mongod experience or server access can generate a…

    14 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

    2 comments  ·  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)
  7. Allow assignment of Backup Resources before starting Backup Job

    For very large clusters, ideally backup resources should be assignable before the backup begins. For each shard and config server, assignment of the following would assist in scaling Ops Manager backups.

    • Snapshot Store
    • Oplog Store
    • Backup Daemon (if using FCV <= 4.0)

    Starting the backup could trigger an email to the Backup Administrator who could then assign these resources on the Admin page.

    12 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

    2 comments  ·  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)
  8. Create an option to turn ON/OFF daily snapshots schedule from "Ops Manager- Continuous Backup - Edit snapshot schedule"

    Currently, we have the option to take daily snapshots at different intervals (6 hrs, 8 hrs, 12, hrs, 24 hrs) but we do not have an option to not configure daily snapshots. While daily snapshots are considered essential, we have almost 200 replica sets of different DB sizes and the daily snapshots, tend interfere with itself due to large DB size and not completing itself in good time for the next day's daily snapshot to run. So if we turn off the daily snapshot or tune the frequency of the daily snapshots on select large replica sets, we will avoid…

    10 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

    1 comment  ·  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)
  9. Support Azure blob storage with Ops Manager Backups

    Hello,

    This is a request for Ops Manager to support Azure blob storage as a snapshot store. Currently the following snapshot store options are supported: blockstore, AWS S3 bucket, File System Store.

    While it may be possible to use an S3 API to communicate between Ops Manager and Azure blob storage, thereby storing Ops Manager backups in Azure, this workaround is not officially supported by MongoDB and is thus risky to implement.

    8 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

    0 comments  ·  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)
  10. Sharded Cluster Snapshot Restores - Throttling and Src/Dst Mapping

    When restoring a sharded cluster snapshot, provide a means of mapping the source shard replica set names to the target shard replica set names. This will allow users to predictably restore large/small shards to the appropriate target hosts.

    Currently, this can be done for sharded clusters with fewer than 10 shards by naming the shards in a predicable shard## pattern. However, greater than ~10 shards leads to an alphabetical => alphanumeric restore plan (e.g. shardA10 restores to shardB2).

    Restoring large sharded clusters can also overwhelm networks where MongoDB Agents are downloading snapshots from Ops Manager(s) at the same time. Please…

    8 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

    0 comments  ·  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)
  11. Restore indexes using mongoimport - metadata.json

    When importing an archive from s3 we are given compressed gz files for the JSON data and a metadata.json file which has index info, however there is no efficient way to restore these indexes as mongoimport doesn't support creating indexes. Indexes need to be created manually. When needing to restore multiple collections this can take a very long time.
    It would be great if mongoimport could use this file to create indexes after an import (like mongorestore).

    6 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

    0 comments  ·  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)
  12. Attain granularity on the Ops manager backups & restore

    Backups:Under a project, in a single cluster we may deploy multiple databases which belongs to different applications that are somehow interlinked in terms of their functionality. Different databases requires different backup strategies, retention periods, and so different snapshot schedules. However, the level of granularity on Ops Manager "Continuous Backup" doesn't match the above requirement.

    Restore: How could we restore a single collection, or a database without touching the other databases/collections within a cluster? The restore process that we have today seems to be restoring the whole cluster and not to the level of database/collection. Queryable backup snapshot seems to be…

    6 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

    0 comments  ·  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)
  13. Backup Daemon should check for the available filesystem before starting a groom job

    When a groom job starts, it might get stuck or fail if the available disk space is not enough to copy all live blocks to another directory.

    It would be helpful if the Backup Daemon checks the available disk space before starting a groom job, and notifies the user:
    1. via Ops Manager UI
    2. report it in the logs
    3. sends an alert that the upcoming/scheduled groom job would not start due to low disk space.

    5 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

    0 comments  ·  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)
  14. Restore Backup Snapshots to Sharded Clusters via mongos

    Migrating large sharded clusters to a different cluster pre-sharded with different shard keys requires a significant amount of time to balance post-restore.

    This is a feature request to restore a snapshot on a per document basis through a mongos. The desired result is a completed restore with collections/documents residing on their target shards.

    5 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

    0 comments  ·  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)
  15. In the event of an integrity check job failure, an alert should be shown on Ops manager UI instead of solely relying on email

    Integrity Check Jobs failures get emailed to the configured "mms.backup.alertsEmailAddr" address and logged in daemon.log. This information should also be available in Ops Manager UI so that the user can quickly check before trying any restoration.

    5 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

    0 comments  ·  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)
  16. Add Ops Manager check to prevent making backups of itself (Backing databases - AppDB, Oplog, Blockstore)

    Otherwise, an Out Of Memory condition may result and disable Ops Manager.

    5 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

    1 comment  ·  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)
  17. Multi Region S3 BlockStore

    On an S3 Blockstore, right now we are able to stick to only one region backup because S3 do not support versioning & Replication. For an high availability systems a backup also needs to be in multiple regions.

    If we could add the following that will be good.
    1. Configure Multiple backups in a project because S3 snapshot store can be only used in one region.

    4 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

    0 comments  ·  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)
  18. Mongoimport should support delimiter option when importing csv txt files such as |,: etc

    Mongoimport should support delimiter option when importing csv txt files such as |,: etc
    Mongoimport ....... --delimitor :

    4 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

    1 comment  ·  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)
  19. Changes to Backup Configuration

    Ability for changes in a project's Backup Configuration page to take effect without having to terminate and restart backups. Terminating backups removes all existing backups thus exposing an organization to risk. Backups can be stopped and restarted for the changes to take effect but not completely terminate them. This would help when changes are needed into terms of backup daemons, blockstores, types of blockstores, etc.

    4 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

    0 comments  ·  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)
  20. Export Cloud Backup to AWS S3 as CPS

    Currently, the Atlas provides possibility to configure an automated export cloud backups to an AWS S3. It uploads the contents of your database to S3 as gzip files with documents in extended JSON format within. It is possible to restore from these files using mongoimport tool.

    However, for some our use cases we would like to have backups exported to our AWS S3 as CPS (cloud provider snapshots) - actually a snapshot of the database directory at the filesystem level - in order to be able to restore very fast (the import via mongoimport and re-building of indexes can take…

    3 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

    0 comments  ·  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)
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base