[DOCS-10944] Clarify that using mongorestore with --oplogReplay option means you must restore the full dump Created: 25/Oct/17  Updated: 30/Oct/23  Resolved: 18/Nov/17

Status: Closed
Project: Documentation
Component/s: tools
Affects Version/s: 3.4.2
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Spencer Brown Assignee: Anthony Sansone (Inactive)
Resolution: Fixed Votes: 0
Labels: mongorestore, oplog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

https://docs.mongodb.com/manual/reference/program/mongorestore/#cmdoption-oplogreplay


Issue Links:
Related
related to DOCS-11010 mongorestore access control docs out ... Closed
Participants:
Days since reply: 6 years, 11 weeks ago
Story Points: 0.2

 Description   

mongorestore with --oplogReplay requires that the full dump be restored. This should be noted in the description for the --oplogReplay option. Something like:

"--oplogReplay must restore the full dump of the replica set member. You cannot use options that limit the databases and collections being restored."

Here is an example of the error you receive: (this with MongoDB 3.4.9)

mongorestore  --username admin --password <redacted> --authenticationDatabase admin --oplogReplay --nsInclude foo.*
2017-10-25T07:15:50.253-0500	Failed: cannot use --oplogReplay with includes specified



 Comments   
Comment by Githook User [ 29/Nov/17 ]

Author:

{'name': 'Anthony Sansone', 'username': 'atsansone', 'email': 'tony.sansone@mongodb.com'}

Message: (DOCS-10944): Added limitation of --oplogReplay.
Branch: master
https://github.com/mongodb/docs/commit/bee2b022e822aa298b188ba06ccec50dde42f87a

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