Design Choices for MOM Configuration Groups
Goto the MOM Home Page
 
I would like to install MOM to monitor the production environment/domains and a test environment. These are very small environments/domains (less than 30 servers). And the test environment will be changed and reinstalled often.

What will be the best Design choices? Single Configuration group, single server? Possible problem: unnecessary messages from the 'ruin' test environment.

Multiple Configuration Groups? Problem: Extra hardware needed (2 MOM servers, database, DCAM).

Or are there other options?

Contributed By: Travis Wright [MSFT]
You can reuse your hardware by creating multiple instances of SQL Server.  MOM 2000 SP1 supports installing more than one MOM DB (OnePoint) on a server as long as they are installed on different SQL Server instances.

For Configuration Groups which contain the number of computers you are talking about (30) a single DCAM/DB server should be able to manage them just fine although you won't have DCAM redundancy that way. That is another way you can save on hardware costs.

Consider using the MCF to forward data from multiple configuration groups to a single configuration group. This might also help you in your design.

See the MOM Performance and Sizing white paper for more information that
might help you in your architecture decisions.

http://www.microsoft.com/mom/techinfo/administration/perfsize.asp?sd=gn&ln=en-us&gssnb=1&gssnb=1

See the Supported Configurations guide to make sure that your architecture
design decisions are within the boundaries required for Microsoft support.

http://www.microsoft.com/downloads/details.aspx?familyid=291adde4-eb5e-4ecc-a160-7d50e80d1faa&displaylang=en

© FAQShop.com 2003 - 2008

Goto the MOM Home Page

Email the Author