4.5.3 Maximum disk space requirements for the management server and database server in a multi-server configuration system
The following describes the maximum disk space requirements for data folders on the management server and database server in a multi-server configuration system.
Maximum disk space requirements on the management server
In addition to the disk space shown in the table below, we recommend that you allocate 1GB of free space to a local data folder for use as a work folder during operation. AlthoughJP1/IT Desktop Management 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 |
Maximum space |
|---|---|---|---|
|
Data folder |
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. |
Maximum disk space requirements on the database server
In addition to the disk space shown in the table below, we recommend that you allocate 1 GB of free space for a local data folder for use as a work folder during operation. Although,JP1/IT Desktop Management uses information not covered in the following table, but such information requires a relatively small space and therefore has little influence on the estimate.
|
Data folder |
Saved data |
Storage period |
Maximum space |
|---|---|---|---|
|
Database folder |
The following information used by the management server:
|
Stored until deleted. |
2.0 GB |
|
The following asset information:
|
Stored until deleted. |
25 GB Actually, the disk space might exceed 25 GB because the folder size increases with the number of registered items. We also assume that the following information items have been registered, each item has no additional management items, and many large files are not registered. To register many large files to be managed, allocate sufficient free space separately.
|
|
|
Device information for managed devices |
Stored until deleted. |
50 GB This is based on the assumption that 50,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 15 GB This is based on the assumption of a system with 50,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 50,000 licenses owned + 10,000) x 1.5 KB = Approximately 18 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). |
50 GB This is based on the assumption that reports are stored for 10 years. |
Approximately 10 GB This is based on the assumption that 1,000 10 MB packages are registered. |
|
Data folder |
Packages used by the distribution function |
Stored until deleted. |
|
|
Revision history output folder |
Revision history archive |
When you enable output of the revision history archive, revision history is output to this folder as CSV files at regular intervals. |
Approximately 50 GB This is based on the assumption that 50,000 devices are managed, and the revision history archive spans five years. |
Related Topics: