[DOCS-1513] Backups dependency on MMS data Created: 14/May/13 Updated: 14/Jun/13 Resolved: 05/Jun/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | Allison Reinheimer Moore |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 10 years, 37 weeks ago |
| Description |
|
I feel the dependency backup has on the MMS agent is not clearly stated. I think it's fair to say a good number of backup users were not in MMS to begin with and will skip over lots of the MMS bootstrapping that's necessary for the BRS system to work correctly. Information that I feel should be conveyed in some way: The list of replica sets and clusters that can be enabled for backup are populated entirely from the hosts that are added into MMS and what the MMS agent can discover from the seed list. If the appropriate hosts are not added and/or the MMS agent is not being correctly run, the list of replica sets and sharded clusters that can be backed up will be incomplete or oudated. |
| Comments |
| Comment by auto [ 05/Jun/13 ] |
|
Author: {u'username': u'schmalliso', u'name': u'schmalliso', u'email': u'allison.moore@10gen.com'}Message: |