-
Type:
Task
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
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
*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
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).
- duplicates
-
-
- Closed
-