[DOCS-3447] Documentation should mention how we handle "slavedelay" hosts Created: 21/May/14 Updated: 16/Mar/15 Resolved: 13/Jun/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.6 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Daniel Coupal | Assignee: | Bob Grabar |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 9 years, 39 weeks ago | ||||
| Description |
|
The documentation for both OnPrem and Cloud should specify that selecting to backup from a secondary that has a slave delay is fine as long as the oplog window is large enough to catch up. http://mms.mongodb.com/help-hosted/current/tutorial/enable-backup-for-replica-set/ |