[DOCS-10705] Explain that mongodump --oplog only works against full dumps Created: 22/Aug/17 Updated: 30/Oct/23 Resolved: 18/Nov/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | tools |
| Affects Version/s: | 3.4.7 |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Torsten Spindler | Assignee: | Anthony Sansone (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | docs-triage, mongodump, oplog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
https://docs.mongodb.com/manual/reference/program/mongodump/#options |
||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 6 years, 11 weeks ago | ||||||||
| Story Points: | 0.1 | ||||||||
| Description |
|
The --oplog option cannot be used when --db is in use as well: $ mongodump --host raw/jaguar.local:27000 --db load --oplog The documentation on https://docs.mongodb.com/manual/reference/program/mongodump/#options for the --oplog option does not mention this restriction. |
| Comments |
| Comment by Githook User [ 29/Nov/17 ] |
|
Author: {'name': 'Anthony Sansone', 'username': 'atsansone', 'email': 'tony.sansone@mongodb.com'}Message: Added mongodump per |