Users Guide

Understanding Performance Monitoring | Performance Monitoring
368 OMNM 6.5.3 User Guide
35 Deletion of old rows
enabled?
Most often, the only way old polling data is aged out of the system is by
dropping the old tables but there is also a property that controls whether or
not to delete old records within the tables without dropping the tables
completely. This property is
pm.retention.DeleteOldDBRecords and is
false by default. This feature was added in an earlier OpenManage Network
Manager version to deal with limitations that existed in older database
versions that are no longer supported. We strongly recommend keeping this
feature disabled because it produces a significant drag on system performance
and does not provide any added benefit beyond the dropping of expired tables
(and all the data within them), which occurs anyway.
36
Delete old rows in
retention tables
Deletes the old rows in the retention OpenManage Network Manager tables
according to the retention policy for the monitor associated with each table.
37
Deletion of excess
rows enabled?
Controls whether to delete excess records within the retention tables without
dropping the tables completely. This is accomplished using the following
porperty, which is false (disabled) by default:
pm.retention.PruneRowsInRawDataTablesToMaxCount
If you set this property to true, then the value of the the following property is
the maximum number of rows that any retention table can have:
pm.retention.RawDataMaxCount
This feature existed in earlier OpenManage Network Manager versions to deal
with limitations that existed in older database versions that are no longer
supported. We strongly recommend keeping this feature disabled because it is
a significant drag on system performance.
38
Delete excess rows in
retention tables
Deletes the oldest rows in the OMNM retention tables to get the row count
down to the maximum accepted number.
39
Done Done applying retention policies for polling data.
Process Description