OpsMgr 2007 Hardware Guidance (What hardware do I buy?)
Many of you have been waiting for the System Center Capacity Planner tool to be released and that should be available very shortly. Until then I have put together an excel sheet with some basic hardware recommendation for OpsMgr depending on how many server you want to monitor. These recommendations are based on what I have seen in some customers deployments and they are estimations on the higer side. I have also included rough Database and Data Warehouse sizes if you are using some of the basic Management Packs like (SQL 2005, IIS, DNS, DHCP and Windows Base OS). Make sure to read the notes at the bottom of the excel sheet as well.
Some additional deployment tips:
§ RAID Controller needs to have Write Cache enabled with a ratio of Read/Write set to 50/50 or 25/75
§ We recommend a maximum of 2000 Agents in a single Management Server (MS)
§ We recommend a maximum of 800 Agents in a single Gateway Server (GW)
§ We do not recommend agents reporting to MS when there are GW Servers reporting to MS
§ We do not recommend agents reporting to RMS when there are MS Servers reporting to RMS
§ If you are having multiple Management Groups write into a single Data Warehouse then I would add the recommended RAM requirements for each configuration
§ Always use 64bit servers for the Root Management Servers
§ Having all the OpsMgr roles on a single server is recommended if you are either testing the product or building a pre-production environment.
§ Do not have agents report directly to the Root Management Server. The RMS computes and distributes configuration information to all of the Management Servers and agents in the Management Group and therefore it is important not to add additional load on the RMS.
§ The number of simultaneous consoles has a direct impact on the performance of the system. Having a high end server for the Root Management Server will provide greater console scale and fast console response time.
§ The disk volume for the database should typically be RAID 10 with an appropriate number of spindles.
§ On the Root Management Server the most critical resource is RAM followed by CPU.
§ Use 64-bit hardware and a 64-bit operating system to allow for easy increases in memory beyond 4 GB and provide room for growth as needed.
§ For any given deployment it is a best practice to have the Root Management Server and Management Server in close network proximity to the database and data warehouse as they both write directly to each one.
§ Consider placing the SQL data file and transaction log on separate arrays. This placement allows the transaction log volume to perform I/O more efficiently because its workload consists of mostly sequential writes.
§ Use a battery-backed write-caching disk controller. Workload on the Reporting data warehouse and Root Management Server is reduced by write-caching on disk controllers.
§ When configuring read caching vs. write caching on disk controllers for the Root Management Server, allocating at least 50% of the cache to write caching is recommended.
§ It is recommended that the SQL Server tempdb database file and transaction log file be re-sized to 20% of the total size of the Operations Manager Database and Operations Manager Data Warehouse databases. It is also recommended to put the tempdb on a high-performance subsystem.
– Satya Vel