The OpsMgr 2007 R2 Sizing Helper is an interactive document designed to assist you with planning & sizing deployments of Operations Manager 2007 R2. It helps you plan the correct amount of infrastructure needed for a new OpsMgr R2 deployment, removing the uncertainties in making IT hardware purchases and optimizes cost. A typical recommendation will include minimum hardware specification for each server role, topology diagram and storage requirement.
System Center Operations Manager | Performance Team
Disclaimer: This posting is provided "AS IS" with no warranties. Use of included tools and reports are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
Disclaimer:
This posting is provided "AS IS" with no warranties. Use of included tools and reports are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
Awesome sheet guys, this will help a lot, congrats! I'm happy to one server topology here, and in the next version of this XLS you can talk about suggested monitored network devices number too, please.
Regards,
How does clustering for redundancy fit into this guidance?
The deployment guide is the right resource that provides clustering guidance.
If you want to cluster a RMS, then each physical node in the cluster should have the same min h/w spec for the RMS role as specified in the sizing helper for a given scenario.
Very interesting, and certainly one of the nicest looking sizing spreadsheets I've seen. A couple of questions though,
1. What kind of assumptions are made as to the monitoring load. In other words is this assuming a base Windows, or is it factoring in monitoring Exchange, SQL, etc.
2. I don't see any reference to ACS, is that in here as well?
Hey bob - long time no see!
The assumptions behind the monitoring load is constructed from real customer data with key monitoring work load such as AD, Exchange, SQL, IIS, base OS & etc... (data are gathered from the larger enterprise customers - so the model tends to be more conservative & recommends numbers a little bit on the high end)
The key factors that influence ACS and the resulting topology is a bit different from the core OpsMgr deployment - so we didn't include ACS to prevent the sizing helper from getting over complicated...
You can still find ACS sizing guidance in the OpsMgr Design guide.