15.1.3 Estimating IM database capacity requirements

When using the integrated monitoring database and the IM Configuration Management database, estimate the amount of capacity (disk capacity) required for the databases on the managers where JP1/IM - Manager is running. The table below describes the size model of IM database, which is selectable when you build a system, as well as the system scale corresponding to each database size.

For details about the disk capacity required for an IM database, see the Release Notes for JP1/IM - Manager.

For details about the approximate disk capacity required for each IM database size, see Setup information file (jimdbsetupinfo.conf) in Chapter 2. Definition Files in the manual JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Table 15‒1: Database size models
Size model	Details	Example of system scale
Small scale (S)	Integrated monitoring database	9 GB	Total items of event information: 1,000,000 (approx.)^#1 This number is based on the following assumptions: Average event size: 1 KB^#2 Number of events generated per day: 33,000 Storage period for event information: 30 days
Small scale (S)	IM Configuration Management database	1 GB	Maximum number of managed hosts: 1,024 hosts^#3 Total number of business groups and monitoring groups: 100
Medium scale (M)	Integrated monitoring database	33 GB	Total items of event information: 4,000,000 (approx.)^#1 This number is based on the following assumptions: Average event size: 1 KB^#2 Number of events generated per day: 130,000 Storage period for event information: 30 days
Medium scale (M)	IM Configuration Management database	1 GB	Maximum number of managed hosts: 1,024 hosts^#3 Total number of business groups and monitoring groups: 100
Large scale (L)	Integrated monitoring database	96 GB	Total items of event information: 12,000,000 (approx.)^#1 This number is based on the following assumptions: Average event size: 1 KB^#2 Number of events generated per day: 400,000 Storage period for event information: 30 days
Large scale (L)	IM Configuration Management database	10 GB	Maximum number of managed hosts: 10,000 hosts^#4 Total number of business groups and monitoring groups: 100

Legend:

--: Not applicable.

#1

Total items of event information might exceed the maximum allowed value depending on the timing of erasing events.

#2

Total items of event information decreases if the event size is larger than 1 kilobyte.

#3

The maximum number of hosts that can be monitored by one IM Configuration Management is 10,000. The number of hosts that can be managed is limited by the system configuration and network traffic. For details about the limit values, see Appendix D. Limits.

When the number of hosts (including managers) monitored by IM Configuration Management exceeds 1,024, the size model of the IM database must be the large scale (L).

#4

Considering the configuration of agents, the maximum number of hosts of JP1/IM - Manager and instances of JP1/IM - Agent or JP1/Base that can be placed directly below JP1/IM - Manager is 2,500. The number of hosts that can be managed is limited by the system configuration and network traffic. For details about the limit values, see Appendix D. Limits.

For details about the amount of capacity (disk capacity) required on both the shared disk and the local disk to use an IM database in a cluster system, see the Release Notes for JP1/IM - Manager.

For details about the approximate disk capacity required for each IM database size, see Cluster setup information file (jimdbclustersetupinfo.conf) in Chapter 2. Definition Files in the manual JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

We recommend that you set a database size that provides sufficient leeway should the number of generated events suddenly increase during system operation.

When the integrated management database reaches its maximum capacity, JP1 events are deleted from the earlier events. The maximum number of JP1 events that can be deleted at one time is 20,000 regardless of the database size (this value might be smaller than 20,000 depending on the size of the stored JP1 events).

To Page Top