Ops Tools
42 results found
-
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 -
FCV 4.2 backup snapshot progress description UI issue
In the "Continuous Backup" when a FCV 4.2 backup snapshot is in progress the progress label text can be too long to be displayed:
Sync:
Transferring - Snapshot received XXXMB of YYYMB from zzz/www files over N hrs (xxx kB/s). Overall progress - XX %The CSS currently has
overflow: hiddenso the text that doesn't fit the table cell in the page is hidden.The only way to see the complete status is enlarging the browser window or zoom out the page.
Please improve the page by improving the CSS style of this page, for example by enabling text…
3 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 -
Allow configuring Ops Manager to bypass Proxy for the S3 on-prem
Allow configuring Ops Manager to bypass Proxy for the S3 on-prem.
Configuring the S3 Blockstore also respects the Ops Manager Proxy settings. This is not practical if it is the S3 on-prem which typically does not require external (Internet) access.
2 votes -
we have certain instances where we have more than one databases for their own respective functionality. and we want to keep their backups se
we have certain instances where we have more than one databases for their own respective functionality. and we want to keep their backups separate from each other. would separate or individual backup/restore process is available through Ops Manager?
2 votes -
Allow Point-In-Time restores going back to a configured amount of hours/days
What is the problem that needs to be solved? Allow Point-In-Time restores going back to a configured amount of hours/days (similar to Ops Manager).
Why is it a problem? (the pain) Oplogs are captured for the last 24 hours only, and sometimes the requirement is to be able to execute Point-In-Time restores for longer than 24 hours (48 hours, etc. (to be defined by customer's project/goal)).
2 votes -
Allow honorSystemUmask to be set on Ops Manager HEADDBs
If honorSystemUmask is set to false, new files created by MongoDB have permissions set to 600, which gives read and write permissions only to the owner. New directories have permissions set to 700.
As a result it makes it difficult to read the HEADDB logs in some environments. Allowing honorSystemUmask to be configurable would allow the customer to choose permissions based on their own security policies.
2 votes -
Add configuration option to disable seedSecondary scripts in snapshots
Currently each snapshot includes the seedSecondary scripts that no longer work for MongoDB 3.6 or greater.
-r-x-w-r-t 1 107 65534 767 Jan 30 11:40 seedSecondary.sh -rw-r--r-- 1 107 65534 754 Jan 30 11:40 seedSecondary.batPlease add an option to disable adding these files to snapshots or remove them completely as they are deprecated for MongoDB 3.6+.
2 votes -
2 votes
-
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.
1 vote -
Mongo Atlas: create backup before updating version
If I upgrade Atlas cluster, Atlas automatically creates a backup with the new version.
I'd rather have a backup of the cluster with original version.
It will allow to restore to the previous version.
Current workaround: create a backup manually before upgrade.1 vote -
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 -
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 -
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 -
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
- Don't see your idea?