[DOCS-1245] Misleading comment saying point-in-time snapshop is impossible with mongodump Created: 16/Mar/13 Updated: 03/Nov/17 Resolved: 16/Jan/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Michael C. Harris | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Location: http://docs.mongodb.org/manual/administration/backups/ |
||
| Participants: | |
| Days since reply: | 10 years, 4 weeks, 6 days ago |
| Description |
Point-in-time snapshots are possible using mongodump --oplog (since 1.7.4) if the instance is running as part of a replica set.
Even if my assertion above is shown to be incorrect, only a single disadvantage is listed for each strategy. |
| Comments |
| Comment by Kay Kim (Inactive) [ 16/Jan/14 ] |
|
Closing as the backup strategy page underwent significant rewrite |
| Comment by Michael C. Harris [ 17/Mar/13 ] |
|
Thanks, I'll expand to include --oplogReplay and mention time.
Do you mean because of the difficulty of synchronising backups across nodes? If so, that's an issue that's not restricted to binary dumps. I'll move point-in-time snapshots to another paragraph, it's becoming clunky in the list. |
| Comment by Sam Kleinman (Inactive) [ 17/Mar/13 ] |
|
- I'll get someone else with more backup experience than I have to look this over, but I think it would be good to:
|