MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

ADD NEW FEEDBACK

Feedback

    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...
    Guest over 5 years ago in Backup & Restore 0 Submitted

    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....
    Guest over 5 years ago in Backup & Restore 0 Submitted

    deleteMany() execution automatically disable the balancer on sharded clusters

    deleteMany() execution automatically disable the balancer on sharded clusters
    Marco Barbierato about 1 year ago in Replication & Sharding 0 Submitted

    we have an ask to use 4 in snapshotIntervalHours

    For the api - https://www.mongodb.com/docs/ops-manager/current/reference/api/backup/update-one-snapshot-schedule-by-cluster-id/ we have an ask to use 4 in snapshotIntervalHours. Right now its not supported. Supported ones are - 6, 8, 12, or 24. P...
    Guest about 1 year ago in Backup & Restore 0 Submitted

    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.
    Guest about 6 years ago in Backup & Restore 0 Submitted

    Automatically move HEADS in case of backup daemon problem

    In configuration with multiply daemons in case of daemon problem (down) switch to another one automatically with restart backup upon need.
    Ilya Shifman about 1 year ago in Backup & Restore 0 Submitted

    Integrating Ops manager with other enterprise tools

    Increasing foot print and creating a a smooth integration for customer environment for Mongodb by making it ready to plug and play for any enterprise. Big enterprises will have their own backup, monitoring and automation platforms. Mongodb or ops ...
    Guest over 3 years ago in Backup & Restore 0 Submitted

    Scheduled stepdown for smoother primary election

    Stepdown is a great tool that allows us to keep clusters operating smoothly. We use it for example when we want to perform some maintenance work on the host where the primary is currently running, to perform a rolling upgrade, and in many other ca...
    Guest almost 2 years ago in Replication & Sharding 0 Submitted

    allow mongosync to migrate few field from source to destination for collection in database

    right now mongosync will migrate all the fields from source to destination based on filter or non filter setting but there is no way to move few field out of all field for all document to migrate few field from source to destination for collect...
    Dasharath Dixit almost 2 years ago in Replication & Sharding 0 Submitted

    Use dedicated interface for replication and balancing

    Like many other big database system, MongoDB may support to specify dedicated interfaces for replication and/or for the balancer (sharding) Currently you can configure replication sets and shards members only by single hostname/IP-Address, i.e. *...
    Wernfried Domscheit almost 4 years ago in Replication & Sharding 0 Submitted