Management Server/Master Management Server
CPU
Intel Xeon E5503 (2 GHz) or higher
Memory (*1)
At least 2 GB (excluding OS)
The feature below requires additional memory.
Log viewing database
0.5 GB or more
HDD specifications
SATA 7200 rpm in the case of RAID0
SAS 15000 rpm in the case of RAID5
However, RAID5 is not recommended as it lowers the update performance.
Hard Disk Capacity (excluding OS) (*1)
Program Manual
160 MB
Database system (added by Systemwalker Desktop Keeper)
170 MB Database space
For information on how to estimate capacity, refer to "3.1.2 Estimating Database Capacity".
Backup file space
The entire log CSV file = average record length (byte) x the number of clients x backup time (days) x number of operation logs per day (piece/day) average record length: 500 bytes
Space for saving the Management Console
For details on space for saving the Management Console, refer to "Management Console".
Space for saving the screen capture data (when using the screen capture function)
For how to estimate the capacity needed for screen capture, refer to "Estimating the capacity of screen capture data"
Space for saving backup data of original files (when using the original file backup function)
Refer to "Data capacity of backup original file" for details.
The disk capacity required for sending log data (when the Log Analyzer Server is used)
For an estimation of the disk capacity required for necessary temporary workspace during the execution of log data transfer, refer to "Estimating temporary disk capacity required for sending log data".
The available drive capacity of the following folders must be larger than 1% of the total drive capacity:
Folder for saving attached data
Folder for command log
Folder for collective log sending
Destination folder for saving E-mail content
Folder for trace log
*1: The requirement for memory and disk capacity may change according to system structure, scale and available resources.
Note
Issues to be considered according to the capacity of installation drive of Management Server/Master Management Server
Specify a drive that can be guaranteed to have the following capacity to be the installation drive of Management Server/Master Management Server.
Work space during data backup (used during operation only)
A space of about 10 GB is required for processing 10 million records, so estimate the required space according to the number of records to be processed.
Number of records x 500 (average record length) x 2 (coefficient)
For example, to back up a maximum of 10 million tables,
10 million x 500 bytes x 2 = about 10 GB
Work space during data restoration (used during operation only)
Space is the same as the size of the file to be restored.
Log Analyzer Server
CPU
Intel Xeon E5503 (2 GHz) or higher
Memory (*1)
At least 2 GB (excluding OS)
Hard Disk Capacity
At least 320 MB
Disk capacity for database (*1)
For information on how to estimate capacity, refer to "3.1.2 Estimating Database Capacity"
*1: The requirements for memory and disk capacity may change according to system structure, scale and available resources.
Management Console
CPU
Celeron 2 GHz or higher
Memory
At least 256 MB (excluding OS)
Hard disk capacity
At least 80 MB
Note
Logs cannot be displayed in the following cases:
When logs are displayed in the Log Viewer, each log occupies about 7.5 KB of memory.
If the number of logs reaches 100,000, memory of 100,000 x 7.5 KB= 750 MB will be used.
Therefore, when there is less available memory in the Management Server or in the PC on which the Log Viewer is running, logs may not be displayed.
Besides, in the 3-level structure, the same memory is used when the logs of the sub-level Management Server are displayed by connecting with the Log Viewer of the Master Management Server. Thus, when there is less available memory in the sub-level Management Server or in the PC where the Log Viewer is running, logs may not be displayed.
Report Output Tool
CPU
Celeron G530T 2 GHz or higher
Memory (*1)
At least 512 MB (including OS)
Hard disk capacity
At least 50 MB
Disk capacity for log output (*1)
The following disk capacity is required:
400 bytes x output logs
*1: The requirements for memory and disk capacity may change according to system structure, scale and available resources.
Relay Server
CPU
Intel Xeon E5503 (2 GHz) or higher
Memory
At least 2 GB (excluding OS)
Hard disk capacity
At least 2 GB
Client (CT)
CPU
Pentium III 600MHz or higher
Core i3 2.0 GHz or higher if the local proxy method is used as the web communication monitoring method
Memory
At least 320 MB (excluding OS)
640 MB or higher (excluding the operating system) if the local proxy method is used as the web communication monitoring method
Hard disk capacity
At least 130 MB
At least 945 MB (when using the original file backup function and E-mail content saving function)
Detailed information is as follows:
Item Name | Required Disk Capacity | Description |
---|---|---|
Attached data (screen capture data) | 15 MB | The hard copy image of the screen captured by the Screen Capture function will be saved to the client (CT) temporarily, even if it has been saved as attached data on the server. This is the required capacity. (The average capacity of the amount of screen capture data that are saved to the client (CT) is 100.) The collection still can be performed when the amount of collected data exceeds this capacity. However, if the capacity of the drive in which the folder used for saving log files of client (CT) is located is less than 50 MB, the screen capture data will not be collected. |
Attached data (backup original file data) | 700 MB | If the original file backup function is used when exporting files using the file export utility, the attached data will be saved to the client (CT) temporarily, even if it has been saved as attached data (original backup data) on the server. This is the required capacity. This capacity can be changed in the terminal operating settings of the Management Console. If the amount of collected data exceeds this capacity, the original file backup will not be performed. |
Attached data (E-mail content data) | 50 MB | If the E-mail content saving function is used when sending E-mails, the attached data will be saved to the client (CT) temporarily, even if it has been saved as attached data (original backup data) on the server. This is the required capacity. This capacity cannot be changed. Besides, if the E-mail content data exceeds this size, the E-mail content cannot be saved. |
Attached data (email content data) | 50 MB | If using the email content saving feature when receiving emails, the attached data will temporarily be saved to the client (CT) even if it has been saved on the server. The capacity is required for that purpose. This capacity cannot be changed. Additionally, the email content cannot be saved if the email content data exceeds this size. |
Prohibition log | 10 MB | If the client (CT) cannot be connected with the Master Management Server or Management Server, the prohibition logs will be saved to the client (CT). If the available capacity of the drive in which the folder for saving log files of the client (CT) is located reaches 100 MB, multiple new files can be created. The maximum size of a file is 10 MB. Besides, if the available capacity of the drive in which the folder for saving prohibition logs is located is less than 100 MB, the following prohibition logs will be deleted. The drive for saving prohibition logs is the one for saving log files, which is specified during the installation of the client (CT). Initial value: <OS installation drive> |
Operation log | 30 MB | If the client (CT) cannot be connected with the Master Management Server or Management Server, the operation logs will be saved to the client (CT). If the available capacity of the drive in which the folder for saving log files of client (CT) is located reaches 200 MB, multiple new files can be created. The maximum size of a file is 30 MB. Besides, if the available capacity of the drive in which the folder for saving operation logs is located is less than 200 MB, the following operation logs will be deleted. The drive for saving operation logs is the one for saving log files, which is specified during the installation of client (CT). Initial value: <OS installation driver> |
Error log | 60 MB | On the client (CT), the initial setting of operation records and error information is a maximum if 2 MB per day over a period time of 30 days, so a maximum of 60 MB can be saved in total. Thus, the capacity is 60 MB. The capacity of the error log can be changed. For the change method, refer to "Change Operation Settings of Client (CT)" in the User's Guide for Administrators. Besides, if the capacity of the error log exceeds the disk capacity, the following error log will be overwritten. |
Others | 30 MB | The capacity needed for the modules and manuals. |
Printer (for report output)
Printer is used according to the report output function when printing reports.
The following performance is required for the printer being used:
A4 printing is available
Black-and-white printing (color printing is recommended) is available
Resolution of 600dpi or higher
Smart Device (Agent)
Internal Memory
At least 30 MB
Capacity varies because the logs with variable length (such as URL) are stored.