Below: From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Sven Wells Sent: Tuesday, April 22, 2014 10:38 AM To: [email protected]<mailto:[email protected]> Subject: [msmom] SCOM 2012: All Management Servers resource pool?
Hello, We are getting ready to add 3 more Management Servers to our existing 8. These three new management servers will be designated for Network monitoring and nothing else. My questions are as follows: 1. Is it mandatory that these three management servers also have membership in the All Management Servers resource pool? [KH] Absolutely not. In fact, you might see better performance if you DON'T include them in the AMSRP. With a lot of management servers participating in the AMSRP, you can also consider removing the "default observer" which is the database. There is no simple rule of thumb here, however, if I have three or more MS participating in the AMSRP, and I have other ADDITIONAL management servers with dedicated purposes that might be heavy load, like network, Linux, URL, or Veeam servers, I will almost always consider recommending the removal of those management servers from AMSRP. http://support.microsoft.com/kb/2853431 2. Is there a best practice for how many Management Servers should have membership in the All Management Servers resource pool? Nope. Not that I am aware of anyway. The "best practice" would be to use a minimum of two management servers to provide high availability for the AMSRP functions. The secondary best practice would be to provide as many management servers as necessary to be able to distribute the load assigned to the resource pools, which would include the AMSRP. In large environments, this often happens naturally as you scale out additional management servers for agent load. 3. Can we, should we also designate other Management Server resource pools for other monitoring associated with MPs that seem to be very busy? Not sure I understand what you are talking about. Resource pools are a way to assign workflows in a highly available fashion that you need to run on management servers (and gateways). Just because a management pack creates "load" or is "busy" depends greatly on where that MP needs to execute workflows.
