Hi!
We’re trying to set up PBM for a sharded mongo cluster. There’s an agent running on every mongoc and mongod node, and the backup starts just fine. On each shard, the backup gets performed by an agent running on a secondary, but the agent initiates the “mongodump” connection against the shard primary. I’ve confirmed this via db.currentOp({$all: true})
on the primary. The result is that the uplink of the primary is saturated as data is streamed from there to the secondary, and from there to the configured remote storage. This is something that certainly blocks us from taking the tool into use.
This issue was referred to in https://jira.percona.com/browse/PBM-407?focusedCommentId=247887&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-247887but I didn’t find any continuation to that particular problem. Am I doing something wrong or is there a bug?
We’re running Mongo 4.2 and PBM 1.3.2. We use TLS with certificate authentication and the PBM_MONGODB_URI is of the form:
mongodb://pbmuser:pass@local.node.fqdn:27017/?tls=true&tlsCertificateKeyFile=/path/to/certkey&tlsCAFile=/path/to/cafile