[DOCS-5428] Ops Manager sizing - discrepancy between "Basic Production Deployment" and "Medium Architecture" from sizing spreadsheet Created: 13/May/15 Updated: 11/Jan/17 Resolved: 27/Jul/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mark Helmstetter | Assignee: | Bob Grabar |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | mms, mms-backup, mms-docs, opsmanager | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 7 years, 29 weeks ago |
| Epic Link: | docs-install |
| Description |
|
In our 3 server "Basic Production Deployment" (https://docs.opsmanager.mongodb.com/current/tutorial/install-basic-deployment/) diagram, we have the backup daemon component and corresponding heads on "Server 2", hosted on the same server as the blockstore primary. However for our internal sizing calculator the "Medium Architecture" component distribution places the backup daemon on "Server 1", the same server as the MMS application and MMS app db. Ideally it seems that our diagram should be consistent with the sizing recommendations. |
| Comments |
| Comment by Emily Hall [ 27/Jul/16 ] |
|
Closed for housekeeping on 7/27/2016 by Emily Hall. |