[DOCS-4033] Clarify ability to use --oplog and --oplogReplay with <path> and mongorestore Created: 11/Sep/14 Updated: 30/Oct/23 Resolved: 01/Jun/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | William Berkeley | Assignee: | Allison Reinheimer Moore |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 8 years, 17 weeks ago |
| Description |
|
In the description for the <path> argument of mongorestore (http://docs.mongodb.org/manual/reference/program/mongorestore/#mongorestore-path-option), specify that you cannot restore from a subfolder of a dump if you're using --oplogReplay. In this case, you must restore the whole dump. e.g. mongodump --oplog produces dump/ directory with test/ subdirectory mongorestore --oplogReplay dump/test won't work to restore just the test database; you must restore the whole dump mongorestore --oplogReplay |
| Comments |
| Comment by Allison Reinheimer Moore [ 21/Oct/15 ] |
|
Added PR for 2.6 updates. https://github.com/mongodb/docs/pull/2400 |