My company is
monitoring a small amount of servers (18) and I have set the Database size to 6
GB. But the database keeps falling below 30% free space and I don't know what
could be causing it to grow so big?
I keep trying to shrink it but it doesn't make any difference. I don't just want
to increase the size as I'm sure for that amount of servers is should be growing
that big. We have got the default grooming schedules.
From the microsoft.public.mom
newsgroup
There are a few
factors that come to mind:
-
Disable a few Process Rule Groups
-
Change your Grooming Settings
- Set
up Multiple Configuration Groups
Disable a few Process Rule Groups
By default, MOM enables
the "Default Event Collection..."
Process Rule Group (PRG). This PRG collects all Windows Event Log events and
copies them to the MOM database. If you have security auditing on, these
events can account for a great deal of data in a hurry. Some folks have
disabled this PRG and others, being more specific for the data they want to
collect from agents.
Also, if you installed all of the Management and Application Packs, you
probably have many PRGs enabled that you don't need, and they might be
collecting events and performance data that you don't need. [This is what
happened to me]. You can either disable or delete these PRGs (disabling is
preferable in case you might need to enable them later).
Change your Grooming Settings
The default Database
Grooming settings might not be right for your needs. You can shorten the
times for grooming and get back some of the database space that way.
Especially helpful to reducing DB size are:
- All
sampled numeric data (this is mainly data for performance counters etc and
it can get HUGE in 90 days)
-
Windows NT Security Event log (This can also grow to a very large size,
depending upon auditing settings). NOTE: This cleans out the copies of
these events that MOM made in its own database. The events are still
around in the Windows Event log, depending upon the settings there.
WARNING - Database Grooming removes the data (from the MOM
database) forever. The MOM database should be backed up on a regular basis
if this data is needed for analysis reasons. For more information about
database grooming, see the
MOM Operations Guide, chapter 6 pages 7-13. For information about
backing up the MOM database, see the
MOM Operations Guide, chapter 6 pages 20-23.
Set up Multiple Configuration Groups
You might have either too
many agents connected to the DCAM, or agents that are "chatty". You might
want to split up the monitored servers into two groups and have them report
to two DCAMs.
I highly recommend the
MOM Operations Guide, specifically chapters 6 "MOM Database Management"
and 7 "MOM DCAM Management".
|
