[DOCS-3831] What resources does the MMS backup agent need? Created: 28/Jul/14 Updated: 11/Jan/17 Resolved: 20/Aug/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Joanna Cheng | Assignee: | Unassigned |
| 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, 26 weeks ago | ||||
| Description |
|
We recommend not running on a t1.micro instance on MMS, but what kind of CPU/memory requirements does the backup agent need? |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 20/Aug/14 ] |
|
The recommendation against using t1.micro is to avoid CPU starvation caused by Amazon's scheduling policies for those instance types, and not, necessarily because the smaller instances are incapable of running backup agents. I think the following question answers the question. The amount of CPU/memory depends on much data you have to collect/send and how many hosts you use: |