One of them is the needed size of the databases for OpsMgr. It depends on the count of Agents reporting to the OpsMgr environment and the time the data will be kept in the databases. For the Operations Manager DB this is default 7 days and for the Data Warehouse DB (used for reporting) this is default 400 days.
During the installation of OpsMgr the initial size of the databases has to be set. It is important to get it right from the start since it will create a single, arranged and unfragmented file where as later changes can fragment it which may cause performance problems in the future.
Gladly enough there are multiple good sources to be found which will aid you in estimating the needed sizes of these databases. I’ll list them here.
However, there is theory and practice. For the latter check out this thread on the TechNet OpsMgr forum. Here Kevin Holman gives some good advises how to go about it. Absolutely worth while to be read.
- Official Microsoft website for OpsMgr
Mapping Requirements to a Design for OpsMgr
- Microsoft System Center Capacity Planner 2007 Model
Downloaded here.
Needs a good understanding before it can be put to use. However, on the internet many explanations are to be found.
- SCOM Unleashed
As stated before, my personal SCOM Bible. The authors also run a blog on which they publicly share some good information from the book. Found here. (When you don’t have the book, buy it now since it is very very good and soon the edition covering R2 will come out as well!)
- System Center Central
Multiple Excel sheets are to be found there. One needs an account to download these sheets though, but the account is free.
- SCOM2007DBestimatorv1.xls
- OpsMgr2007_20DB-DW_20Size_20Calculator.xls
But also hardware is very important. Check here for hardware guidance for OpsMgr.
When everything is installed and working properly, it still needs attention. Kevin Holman (who else :) ) has written some good postings about it. Look here for these postings.
No comments:
Post a Comment