[DOCS-9602] Comment on: "manual/reference/program/mongodump.txt" Created: 06/Dec/16  Updated: 30/Oct/23  Resolved: 14/Jul/23

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Docs Collector User (Inactive) Assignee: Cory Bullinger
Resolution: Done Votes: 1
Labels: collector-298ba4e7, quick-win, server-docs-bug-bash
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: https://docs.mongodb.com/v3.2/reference/program/mongodump/
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0
Screen Resolution: 1536 x 864


Participants:
Days since reply: 7 years, 10 weeks, 1 day ago

 Description   

I'm running the following command with the result error shown below:

mongodump --username some_user --password some_pass --db some_db --authenticationDatabase admin --gzip --oplog --dumpDbUsersAndRoles --out /my/dir/
2016-12-06T19:04:32.525-0300    Failed: bad option: --oplog mode only supported on full dumps

It's running against a SECONDARY on a replica set.
The documentation doesn't mention there is a need for a backup to be a full backup or that the --oplog option doesn't work on a SECONDARY. It even mentions a single database in the description of this option. So in this case, I'm not sure what the cause of the error is.


Generated at Thu Feb 08 07:58:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.