[SERVER-2025] Use oplog to make mongodump a point-in-time snapshot Created: 28/Oct/10 Updated: 12/Jul/16 Resolved: 30/Nov/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Tools |
| Affects Version/s: | None |
| Fix Version/s: | 1.7.4 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
will be point-in-time as of the end of the mongodump. Also need to add replay support to mongorestore. |
| Comments |
| Comment by Mathias Stearn [ 30/Nov/10 ] |
|
I should have been more specific. mongodump --oplog works with any version mongorestore --oplogReplay only works with new servers and already errors out if the server is too old |
| Comment by Scott Hernandez (Inactive) [ 30/Nov/10 ] |
|
Can you make those options throw an error if run against old versions (< 1.7.4)? |
| Comment by Mathias Stearn [ 30/Nov/10 ] |
|
Note that this won't work with old servers |
| Comment by auto [ 29/Nov/10 ] |
|
Author: {'login': 'RedBeard0531', 'name': 'Mathias Stearn', 'email': 'mathias@10gen.com'}Message: Use oplog to make mongodump/restore point in time |
| Comment by auto [ 29/Nov/10 ] |
|
Author: {'login': 'RedBeard0531', 'name': 'Mathias Stearn', 'email': 'mathias@10gen.com'}Message: make sure tools always use the same slave connection This is needed for |
| Comment by Mathias Stearn [ 28/Oct/10 ] |
|
Right. I'm planning on adding --oplog options to both tools. I may also add a --oplogUpdate to mongodump to fetch all new operations since the last dump |
| Comment by Eliot Horowitz (Inactive) [ 28/Oct/10 ] |
|
This should be an option - not default operation |