question

TonyStrother-2074 avatar image
0 Votes"
TonyStrother-2074 asked StoyanChalakov answered

How many management servers for scom 2019 deployment?

Afternoon, I am planning my Prod deployment of 2019 side by side with my current 2012r2 environment. I use a bit of a resource heavy handed powershell script for capturing alerts and sending notifications on my existing 2012R2 environment (2012R2 UR 12). As a result I have the two management servers scheduled for an early morning restart 7 days a week. I want to continue to use the script in the new 2019 environment. Since the first management server does 95% of the alert/notification work, no matter what MS documentation says, here is my thought.
4 management servers - Windows Server 2019
1-only for alerts/notifications, no monitored servers to support
2-3 use as management servers to balance monitored server load, 20-30 linux servers, scom web server,IIS/scom reporting services.
4- SQL 2019 Native reporting services
There will also be a standalone SQL 2019 server to hold the SCOM databases.
I would greatly appreciate your comments and input.
Thanks,
Tony


msc-operations-manager
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

StoyanChalakov avatar image
1 Vote"
StoyanChalakov answered

Hi Tony,

I have some experience in planning SCOM Management Group Design, so here are my thoughts:

  • Your statement:

    Since the first management server does 95% of the alert/notification work, no matter what MS documentation says, here is my thought.

is a bit surprising, considering the fact that this is taken care by the Notification Ressource Pools and the "load" should be distributed among all the members of this ressource pool.

  • In my opinion, having two managament servers for your Windows Server and a small aount of Linux clients (as in your case) is good approach. Of course if the number of Linux Systems increases, you need to consider a dedicated management server or even two of them, depending on the HA requirements. This makes it much more easier to estimate the load on those if they are dedicated for Linux System Monitoring, where the load is on the management server.

  • Installing the SCOM web console on one of those servers is also a standard approach and something I also do.

  • I am not quite sure why you mention SCOM Reporting Services also on your managament servers, but since you have planned a 4th server with SQL Reporting Services, it is clear that you install also the SCOM Reporting Services on it, right?

  • Regarding the SQL backend: Of course it is nice to have some HA at Application Level (SQL Always On for example), but if oyur have a good backup strategy, a single server should also do the job. My only recommendation would be to create different instances for both DBs.

This recommendation, as well as many other tips regarding optimizing the SCOM performance are listed in an article, I wrote a couple of years ago. Please make sure you go over the individual suggestions, this can only help you increase the performance of your new MG:

System Center Operations Manager (SCOM) Management Group Performance Optimizations
https://social.technet.microsoft.com/wiki/contents/articles/53582.system-center-operations-manager-scom-management-group-performance-optimizations.aspx

I would say you have planned well. If you make the additional step and tune your MG according to the recommendations, listed in the article, I think you can forget about performance issues.

I hope I was able to help!


(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)
Regards
Stoyan Chalakov



5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.