Ops Tools
40 results found
-
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 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 -
Add a means for Ops Manager to expose blocks that have changed since a selected date/time or checkpoint.
Add a means for Ops Manager to expose blocks that have changed since a selected date/time or checkpoint. With this, changed blocks can be written to compliant (e.g. immutable) storage systems with the backup consistency guarantees provided by Ops Manager.
1 vote -
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 -
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
-
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.
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 wrapping in the table cell.
0 votes
- Don't see your idea?