4.5.2 Disk space requirements for the management server
The following describes the disk space requirements for data folders on the management server.
In addition to the disk space shown in the table below, we recommend that you allocate 1 GB of free space to a local data folder for use as a work folder during operation. To acquire operation logs, you need to add 500 MB of disk space for 5,000 managed computers. AlthoughJP1/IT Desktop Management 2 uses information not covered in the following table, such information requires a relatively small space and therefore has little influence on the estimate.
|
Data folder |
Saved data |
Storage period |
Disk space |
|---|---|---|---|
|
Database folder |
The following information used by the management server:
|
Stored until deleted. |
0.5 GB |
|
The following asset information:
|
Stored until deleted. |
0.1 GB In addition, this value is based on the assumption that the following information items are registered, and that for each information item, no additional management items exist:
|
|
|
Device information for managed devices |
Stored until deleted. |
10 GB This is based on the assumption that 10,000 devices are managed. |
|
|
Revision history |
Stored until the used disk space reaches the maximum. If the maximum space is exceeded, entries are deleted beginning from the oldest. |
Approximately 7 GB This is based on the assumption of a system with 10,000 managed devices, in which the number of device information changes recorded daily per device is the total of the following:
|
|
|
Events |
Stored until the used disk space reaches the maximum. If the maximum space is exceeded, events are deleted, beginning from the oldest. |
(250 x Number of managed computers 10,000 + 10,000) x 1.5 KB = Approximately 4 GB This is based on the assumption that the following conditions exist:
|
|
|
Reports for the specified storage period |
Stored for the specified number of years (from 1 to 10) as the storage period. |
10 GB This is based on the assumption that reports are stored for 10 years. |
|
|
Data folder |
Attachments for the following asset information:
|
Stored until deleted. |
5 GB In practice, the required disk space might exceed 5 GB, because the required disk space increases with the number of registered information items. This value is also based on the assumption that the information items below are registered, and that no information items exist to which many large files are registered. To register and manage many large files, allocate sufficient free space separately.
|
|
Packages used by the distribution function |
Stored until deleted. |
Approximately 10 GB This is based on the assumption that 1,000 10 MB packages are registered. Note that the packages distributed from the higher management server are also included. |
|
|
Temporary storage data of operation logs |
Stored until the data is stored in the operation log backup folder. |
Approximately 150 GB Required for acquiring operation logs. This is based on the assumption that the following conditions exist, and when operation log backup to the backup folder has not been performed for 2 weeks (5 business days per week):
|
|
|
Information to be sent to the higher management server |
Information is stored until it is sent to the higher management server. |
24 GB Required for the management relay server. This value is based on the assumption that information has not been sent to the higher management server for 2 weeks (5 business days per week). |
|
|
Operation log database folder |
Operation logs when only operations closely related to information leakage are logged (automatically restored operation logs) |
Operation logs are stored for a period specified in the Period for storing automatically restored operation logs field under Operation Log Settings in the Settings module. |
Approximately 45 GB This is based on the assumption that the following conditions exist:
|
|
Operation logs when all operations are logged (automatically restored operation logs) |
Operation logs are stored for a period specified in the Period for storing automatically restored operation logs field under Operation Log Settings in the Settings module. |
Approximately 446 GB This is based on the assumption that the following conditions exist:
|
|
|
Operation logs restored from the backup folder for reference in the operation log list (manually restored operation logs) |
Stored until deleted. |
Approximately 135 GB This is based on the assumption that the following conditions exist:
|
|
|
Operation log backup folder |
Backed up operation logs |
These logs are stored until deleted when the operation log backup folder is specified. If you attempt to reference the restored operation logs in the operation log list, they are restored in the operation log database folder, but the operation logs in the operation log backup folder are not deleted. |
There is no space limitation. Prepare a backup folder by referring to the value obtained as follows: Storage period (days) defined by the administrator x number of managed computers x 70 (KB per day per device). This is based on the assumption that the following conditions exist:
|
|
Revision history output folder |
Archived revision history |
When you enable output of the revision history archive, revision histories are output to this folder as CSV files at regular intervals. |
Approximately 10 GB This is based on the assumption that 10,000 devices are managed, and the revision history archive spans five years. |
Related Topics: