[DOCS-2478] Comment on: "manual/core/backups.txt" Created: 06/Jan/14  Updated: 03/Nov/17  Resolved: 07/Jan/14

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

Type: Improvement Priority: Major - P3
Reporter: Asya Kamsky Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: http://docs.mongodb.org/manual/core/backups/#replica-set-backups
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36
Referrer: http://docs.mongodb.org/manual/tutorial/back-up-and-restore-with-mongodb-tools/
Screen Resolution: 1920 x 1080
repo: docs
source: core/backups


Issue Links:
Duplicate
duplicates DOCS-2422 Rewrite /core/backup page Closed
Participants:
Days since reply: 10 years, 6 weeks, 2 days ago

 Description   

First paragraph, sentence starts with Also and has no subject.

Middle of page, sentence reads "Typically, filesystem snapshots are because of their accuracy and simplicity" - missing word, presumably "better"?

In "replica set considerations" there is a bullet:
"As an alternative you can create a backup with the mongodump program and the --oplog option. To restore this backup use the mongorestore program and the --oplogReplay option."

This doesn't actually restore a replica set member, it restores its data. I think this may mislead someone into thinking that this restore would be ready to be added to a replica set (it won't be because it has no local DB and no oplog).


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