How can we improve the Operational Tooling MongoDB provides?

To setup number of backup daemons in ops-manager.yaml

In ops-manager.yaml, can we define the number of the initial backup daemons?

4 votes

Ming shared this idea · Apr 3, 2020 · Flag idea as inappropriate… · Admin →

under review · Apr 15, 2020

2 comments

An error occurred while saving the comment

Martin commented · August 13, 2021 10:38 AM · Flag as inappropriate

Version 1.12.0 of the MongoDB Kubernetes Operator includes a new resource specification to set the number of Backup Daemons: spec.backup.members

Reference: https://docs.mongodb.com/kubernetes-operator/stable/reference/k8s-operator-om-specification/index.html#optional-onprem-resource-settings

Submitting...
AdminAndrey (Admin, MongoDB) commented · May 5, 2020 11:24 AM · Flag as inappropriate

With Ops Manager 4.2 and MongoDB 4.2 Backup there is no need for more than 1 Backup Daemon (especially when K8S will proactively maintain
However, there are edge cases when this needs to happen. We are going to look into it.

Submitting...

Signed in as (Sign out)

Signed in as (Sign out)

Ops Tools: Kubernetes Operator

Searching…

No results.
Clear search results

Give feedback
- Atlas 746 ideas
- Atlas Data Lake 26 ideas
- Atlas Search 81 ideas
- Charts 151 ideas
- Compass 198 ideas
- Connectors (BI, Kafka, Spark) 22 ideas
- Database 116 ideas
- Drivers 46 ideas
- MongoDB CLI 10 ideas
- MongoDB for VS Code 33 ideas
- MongoDB Shell 14 ideas
- Ops Tools 305 ideas
- Realm 216 ideas
- UI 67 ideas
- University 11 ideas