-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
Environment:Reading 3.2 manual
*Location*: https://docs.mongodb.org/manual/core/backups/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.80 Safari/537.36
*Referrer*: https://docs.mongodb.org/manual/administration/strategy/
*Screen Resolution*: 2048 x 1152
*repo*: docs
*source*: core/backups
Reading 3.2 manual *Location*: https://docs.mongodb.org/manual/core/backups/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.80 Safari/537.36 *Referrer*: https://docs.mongodb.org/manual/administration/strategy/ *Screen Resolution*: 2048 x 1152 *repo*: docs *source*: core/backups
"To mitigate the impact of mongodump on the performance of the replica set, use mongodump to capture backups from a secondary member of a replica set. Alternatively, you can shut down a secondary and use mongodump with the data files directly. If you shut down a secondary to capture data with mongodump ensure that the operation can complete before its oplog becomes too stale to continue replicating."
How I remember in 3.0 mongodump stops doing backups directly from files. Only via mongod.