[SERVER-10841] Mongodump fails partway through without authenticationDatabase option. Created: 22/Sep/13 Updated: 10/Dec/14 Resolved: 22/Sep/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.4.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kevin Lin | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | Linux | ||||||||
| Steps To Reproduce: | mongodump -u admin -p whatever --db database --out /var/mongo/backup |
||||||||
| Participants: | |||||||||
| Description |
|
The mongodump tool stops when it encounters a collection for which it doesn't have permissions. If a database has a large number of collections, the administrator may erroneously assume that the dump was successful based on the fact that "most" of the collections were backed up, especially if the dump is run in a cron context. Mongodump should backup every collection that it has permissions for. (Failing completely without backing anything up would also be preferable to backing up a random subset of collections) |