4.5.4 Guidelines for disk space requirements for the operation log database
Use the following formula as a guideline for estimating the disk space required for automatically restoring operation logs to the database.
- When all the operation logs are acquired
-
Number of managed computers x Period for storing automatically restored operation logs (days)# x 1.52 (MB) = Disk space required for automatic restoration (in MB)
#: The period for storing automatically restored operation logs is 300 days at maximum.
However, if the disk space required for automatic restoration is less than Period for storing automatically restored operation logs (days) x 1.5 (GB), the guideline for the disk space should be Period for storing automatically restored operation logs (days) x 1.5 (GB).
When HIBUN logs are imported, the disk space required depends on the types of HIBUN logs to be imported and your environment. Therefore, operate the logs for about one week or one month, use the following formula to determine the daily disk usage, and then multiply the usage by the safety factor (about 1.5) to obtain the disk space.
Period for storing automatically restored operation logs (days) x Disk usage per day (MB) x Safety factor = Disk space required for automatic restoration (in MB)
The following shows a guideline for the disk space required when the number of automatically restored operation logs is 100,000,000 and 300,000,000.
- With 100,000,000 operation logs
-
74.3 GB
- With 300,000,000 operation logs
-
222.7 GB
When the number of automatically restored operation logs is 100,000,000 and 300,000,000, the operation logs can be stored in the database for the following period.
Number of managed computers |
Guideline for the number of days during which the operation logs can be stored |
|
---|---|---|
100,000,000 operation logs (74.3 GB of disk space) |
300,000,000 operation logs (222.7 GB of disk space) |
|
500 |
4 months |
1 year |
1,000 |
2 months |
6 months |
2,000 |
1 month |
3 months |
5,000 |
2 weeks |
1 months |
10,000 |
1 week |
3 weeks |
30,000 |
1.5 days |
1 week |
Note: A month is calculated as 20 business days.
Use the following formula for estimating the disk space required when you manually restore the operation logs to the database.
- When all the operation logs are acquired
-
Number of computers whose operation logs are to be restored x Period for operation logs to be restored per day (days) x 1.52 (MB)
If the calculated value is less than Period for operation logs to be restored per day (days) x 1.5 (GB), the guideline for the disk space should be Period for operation logs to be restored per day (days) x 1.5 (GB).
When HIBUN logs are imported manually, the guideline for the disk space should be Disk usage per day (MB) x Period for operation logs to be restored per day (days), which is determined when you obtain disk space required for automatic restoration.
- When you manually restore the operation logs for 3 months for 200 managed computers
-
The following formula is estimating the disk space required when you manually restore the operation logs.
90 days x 1.5 (GB) = 135 (GB)
When manually collecting the operation log of half a year (180 days) from 200 computers on one day time span, the approximate disk capacity of the operation log that is manually collected is as follows.
180 days x 1.5 (gigabyte) = 270 (gigabyte)
Assuming that the number of days for automatic collection is 30 days, set the maximum number of days of setup operation log setting to 210 days.
- Important
-
Even if the operation log is deleted from the management screen, the size of the operation log database will not be reduced. When collecting and deleting operation logs, do not subtract the amount of deletion, but only consider the amount of data to be collected as the approximate disk capacity. For details about the operation log database, refer to 2.10.2 Managing operation logs on the management server.
Related Topics: