[SERVER-9536] mongodump oplog doesn't work with mongorestore oplogreplay Created: 02/May/13  Updated: 02/May/13  Resolved: 02/May/13

Status: Closed
Project: Core Server
Component/s: Tools
Affects Version/s: 2.4.3
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Sam Weaver Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

all


Issue Links:
Duplicate
duplicates TOOLS-106 mongorestore --oplogReplay + --oplogL... Closed
Operating System: ALL
Steps To Reproduce:

You must actually dump the oplog using mongodump -d local -c oplog.rs which will create a folder called local with oplog.rs.bson in it.

However, when you do a mongorestore --oplogreplay, it will look for a file called oplog.bson which is only created by doing a mongodump --oplog. So you actually need to name the oplog.rs.bson to oplog.bson and move it up a directory for this to work which is very messy.

If mongorestore can't find oplog.bson it will tell you to use mongodump --oplog which is just plain wrong.

Participants:

 Description   

Using mongodump --oplog does not work with mongorestore --oplogreplay.


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