[DOCS-6847] Comment on: "manual/core/backups.txt" Created: 18/Dec/15  Updated: 14/Dec/16  Resolved: 07/Mar/16

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Pavel Chertorogov Assignee: Allison Reinheimer Moore
Resolution: Done Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
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


Participants:
Days since reply: 7 years, 49 weeks, 2 days ago

 Description   

"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.



 Comments   
Comment by Allison Reinheimer Moore [ 07/Mar/16 ]

Fixed as part of the /core/backups rewrite.

Comment by Githook User [ 15/Jan/16 ]

Author:

{u'username': u'schmalliso', u'name': u'Allison Moore', u'email': u'allison.moore@10gen.com'}

Message: DOCS-6847: mongodump must connect to a running mongod in 3.0

Signed-off-by: kay <kay.kim@10gen.com>
Branch: v3.0
https://github.com/mongodb/docs/commit/def677b33bbe512a7358927aac3a3117897deb3f

Generated at Thu Feb 08 07:53:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.