Ops Tools
40 results found
-
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 -
Disable point-in-time restores
It would be nice to have the ability to set the parameter "Allow point-in-time restores going back" to ZERO (disabling PIT restores). This could be useful in situation where a database is producing a lot of oplog and DBA wants to avoid the saturation of oplog-store. In other words: "I want to mantain shapshot backup functionality, but deactivate PIT functionality".
1 vote -
Incremental backup with reduced snapshots size
The actual size of EACH snapshot is equal to datapath filesystem size. Every snapshot is essentially a copy of all db files. This prevents the use of OPS Manager Backup for large databases. It would be desirable to have a "real" incremental backup, based on one "baseline-snapshot" plus "delta-snapshots" of reduced size.
1 vote -
reencrypt existing snapshot with new kmip key
Customer may decide to migrate from one KMIP provider to another or from one KMIP server to another. If you need store backups for a long period of time (7 years for compliant reason is not an exception), it becomes difficult to make sure that you can restore snapshots from old keys and all old KMIP servers still up and running.
it turns out that it's not possible to export old keys from one kmip provider and import into another kmip provider due to security reasons.
But at the same time - it looks like much easier to implement option…
1 vote -
Added features to improve backup performance on filesystem
Currently, the ability to use multiple workers in Ops Manager is only available for S3. If possible adding this capability, or additional enhancements, to filesystem storage would be beneficial.
1 vote -
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 -
Ops Manager should allow to perform restore/recovery on individual replica node
Currently Ops manager automatic restore process does not support restoring snapshots to a single node of a existing replicaSet instead Ops Manager restore snapshots to an existing replicaSet.
This will be require in case any individual replica node down for longer period and oplog overwrite on primary.
Thank You1 vote -
Allow setting the backup PreferredMember via the API for sharded clusters
It's currently only possible to set a backup PreferredMember via the API for a standalone replicaset, but it's not possible to set the PreferredMember for shards of a sharded cluster.
You can do this via the Web UI, but that's incredibly tedious if you have many shards and it would also be valuable to be able to change the PreferredMember in automation scripts.
1 vote -
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 -
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 -
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 manager must provide options or may have certifies some enterprise backups or monitoring platforms where customers can seamlessly leverage existing features for backup and monitoring instead of building or testing their own things.
2 votes -
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 -
Ops Manager UI estimates backup time and restore
Backups and restore estimation as UI feedback for regular and continuous backups
1 vote -
Increase maximum retention periof of backups
Currently OpsManager's maximum retention period for backups is 84 months (7 years). We have the requirement to keep 10 years of backups, hence adding some values (96, 108, 120, 132, 144) in the "Store monthly snapshots for... months" in the backup schedule would be helpful. Another option might be to allow custom values (I guess this is the purpose of https://feedback.mongodb.com/forums/924355-ops-tools/suggestions/39441955-make-snapshot-retention-policy-more-customisable)
1 vote -
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 -
mongorestore from metadata
hi
When start mongorestore, data is restored first.
so, performance is poor, and recovery takes a long time.
would please proceed from the metadata(index) and change it so that it can be restored quickly.as-is: data > metadata(index)
regards,
park1 vote -
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 -
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.
80 votes -
Never delete the most recent backup snapshot
When backup snapshots cannot be completed as scheduled, and they are behind, Ops Manager really should NEVER delete the most recent snapshot. For example, if the snapshot retention policy is to take a backup every 24 hours and keep daily backups for 2 days, and weekly backups for 2 weeks, a new snapshot should not automatically expire after 2 days. If backups are not completing for some reason, and it goes 2 days without a successful new snapshot, the most recent daily backups are deleted and we are left with the most recent weekly backup instead. There really should never…
3 votes -
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
- Don't see your idea?