[SERVER-14344] mongodump Created: 24/Jun/14 Updated: 10/Dec/14 Resolved: 24/Jun/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Tools |
| Affects Version/s: | 2.6.3 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Dwayne Mcnab | Assignee: | Ramon Fernandez Marina |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: |
| Description |
|
I am doing a backup of my sharded cluster in a testing environment and I am having issues getting mongodump to backup my data files. 2. set fsyncLock to false to disable sychronization on each of the secondaries above. 3. connect to two other secondaries in the set and ran mongodump. However I keep getting this error message, please see file attached. |
| Comments |
| Comment by Dwayne Mcnab [ 24/Jun/14 ] |
|
Thanks Ramon. Sent from my iPhone |
| Comment by Thomas Rueckstiess [ 24/Jun/14 ] |
|
Hi Dwayne, It looks like you're connecting to an existing mongod instance and also providing the --dbpath option. You should either choose one or the other: you can't run mogodump against database files if a mongod is using those files. If you want to run the dump from the live mongod, you do not need to add the --dbpath option; if you want to use --dbpath, you have to stop mongod. Please note: The SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For future MongoDB-related support questions please post on the mongodb-users group (http://groups.google.com/group/mongodb-user) or Stack Overflow with the mongodb tag. Regards, |