This section describes how to estimate the database capacity of the Management Server/Master Management Server and the Log Analyzer Server.
When there is a Master Management Server and multiple Management Servers, it is necessary to estimate the database capacity of each server respectively.
Preparation
The following information is required for estimating the capacity of database:
Number of the clients (CTs)
Number of smart devices (agents)
Number of months for saving operation logs
Number of non-file operation logs
Number of file operation logs
Number of the clients (CTs) and smart devices (agents) in total
Number of the clients (CTs) and smart devices (agents) managed by the Management Server
Number of the clients (CTs) that manage the Management Servers
Number of months to save operation logs
Number of non-file operation logs
Number of file operation logs
Number of clients (CTs)
The estimated number of clients (CTs) is the number of clients (CTs) connected directly with 1 Master Management Server or Management Server that creates the database. If there is no client (CT) connecting to the Master Management Server directly, calculate as 0.
When installing the client (CT) to a virtual environment, add the number of users connecting to the virtual environment as the number of CTs.
Number of smart devices (agents)
Add the number of smart devices (agents) connected to the Relay Server, treating them as Clients (CTs). In 3-level structure, count the number of Clients (CT) that are directly connected to the Master Management Server as the number of smart devices.
Number of clients (CTs) and smart devices (agents) in total
This is the number of all the clients (CTs) connected with the Management Server or Master Management Server.
It is necessary to estimate the database capacity of the Master Management Server in a 3-level structure.
Number of months to save operation logs
This is the number of months during which the operation logs are saved in database.
Number of file operation logs
This is the total number of events of file operation executed at one client (CT) for each day. File operation refers to the "File operation log" item in the "Operation Log Type" contained in the table below.
The file operation log is not recorded for smart devices (agents).
Number of non-file operation logs
This is the total number of all events excluding file operation executed at one client and smart devices (agents) for each day. A non-file operation log refers to the all items in the "Operation Log Type" contained in the table below except for the items marked as "File Operation Log".
Operation Log Type | Selectable | Number of obtained logs |
---|---|---|
Application Startup Log | Yes | The number of times an application has been started [Example] |
Application Termination log | Yes | The number of times an application has been terminated. [Example] |
Window Title Obtaining log | Yes | The number of times an active window has been switched. [Example] |
E-mail Sending Log | Yes | The number of E-mails that have been sent. [Example] |
E-mail receiving log | Yes | Number of emails that have been received. [Example] |
E-mail Sending Suspension Log | Yes | The number of times E-mail sending to unauthorized domains has been suspended. [Example] |
Command Operation Log | Yes | The number of times the command is executed in the command prompt. [Example] |
Device Configuration Change Log | Yes | Number of times the drive configuration has been changed + number of times USB devices have been connected + number of times media have been connected [Example] - The count is "1" when a network drive has been added as the Z drive. - The count is "2" when a USB flash memory is connected and F drive is added. - The count is "1" when a USB web camera is connected (without adding a drive). - The count is "3" when a USB card reader and SD card are connected, and G drive is added. |
Printing Operation Log | Yes | The number of times printing has been used. [Example] |
File Export Log | Yes | Number of exported files [Example] |
File Operation Log | Yes | The number of times file operations have occurred. [Example] |
Linkage Application Log | Yes | The number of times logs are sent by linkage applications. [Example] |
Logon/Logoff Log | Yes | The number of times logon/logoff Windows system/the number of times the computer has been started or shut down/the number of times the computer sleeps or returns/the number of times it is connected to or disconnected from the virtual environment. [Example] The count is "1" when having logged onto a windows system once. |
Environment change log | Yes | Number of times an IP address is changed + number of times the emergency procedure is performed or canceled. [Example] - The count is "1" when an IP address is changed. - The count is "1" when an emergency procedure is performed. - The count is "1" when an emergency procedure is canceled. |
PrintScreen Key Operation Log | Yes | The number of times the PrintScreen key is pressed. [Example] The count is "1" when the PrintScreen key is pressed once. |
Web Operation Log | Yes | The number of times the web upload or web download has been performed. [Example]
|
FTP Operation Log | Yes | The number of times FTP upload or FTP download has been performed. [Example]
|
Clipboard Operation Log(Virtual Environment) | Yes | The number of times a clipboard operation has occurred. [Example] The count is "2" when clipboard is used for copying from the virtual terminal to the physical terminal once. |
Web Access Log (Smart Device) | Yes | Log indicating Web accessed from standard Android browser "Android Browser" [Example] The count is "1" when home page is accessed from "Android Browser". |
SD Card Mount/Unmount Log (Smart Device) | Yes | The number of times the SD card was mounted/unmounted [Example]
|
SIM Card Mount/Unmount Log (Smart Device) | Yes | The number of times the SIM card was mounted/unmounted [Example]
|
Wi-Fi Connection Log (Smart Device) | Yes | The number of times Wi-Fi connection was established [Example] The count is "1" when a smart device gets connected to Wi-Fi |
Bluetooth connection log (smart device) | Yes | The number of times Bluetooth connection was established [Example] The count is "1" when a smart device gets connected to Bluetooth |
A log of incoming and outgoing calls (smart device) | Yes | The number of calls made and received [Example]
|
Application usage log (smart device) | Yes | The number of times an application was used [Example] The count is "1" when the application is used on a smart device. |
Application configuration change log (smart device) | Yes | The number of times an application was installed/uninstalled [Example]
|
Prohibition log | No | The number of times a logon prohibited group has been logged on. [Example] |
The number of times a startup prohibited applications has been started. [Example] | ||
The number of times a Disabled PrintScreen Key is pressed. [Example] | ||
The number of times printing via a Printing Prohibited Application has been performed. [Example] | ||
The number of times the prohibited file has been added to E-mail for sending and saving. [Example] | ||
The number of times the prohibited URL has been accessed or the number of times uploading to or downloading from a prohibited Web server has occurred. [Example]
| ||
The number of times the prohibited FTP server has been accessed [Example] | ||
The number of times the prohibited clipboard has been used [Example] The count is "1" when the prohibited clipboard has been used once. | ||
The number of times a smart device established Wi-Fi connection with a prohibited access point when the Wi-Fi connection to the access points is prohibited for the smart device [Example] | ||
The number of times a smart device established pairing with a prohibited Bluetooth device when pairing with a Bluetooth device was prohibited. [Example] | ||
The number of times a smart device used a prohibited application. [Example] | ||
Others (configuration change log) | No | The number of times policy configuration has been changed via the Management Console. [Example] |
The "Operation Log Type" for which "Yes" is mentioned in the "Selectable" column can be set from Log Collection Operation of Windows of the Management Console.
The "Operation Log Type" for which "(Smart Device)" is mentioned in the "Selectable" column can be set from Log Collection Operation of Android of the Management Console.
Estimating Database Capacity
The method of estimating the database capacity is shown in the following table. Estimate and compare the number of the clients (CTs) and number of smart devices (agents), number of months for saving operation logs, number of non-file operation logs, number of file operation logs and required database capacity that are recorded in the following. In addition, the number of months for saving operation logs is in proportion with the database capacity. (For example: when setting a doubled "Number of months to save operation logs", the database capacity should also be calculated in double.)
Number of the clients (CTs) +Number of smart devices (Agent) | 100 | 500 |
Number of months to save operation logs | 1 month | 1 month |
Number of file operation logs | 500 | 500 |
Number of non-file operation logs | 500 | 500 |
Database capacity | 11,497 MB | 48,724 MB |
Number of the clients (CTs)+ Number of smart devices (Agent) | 100 | 500 |
Number of months to save operation logs | 1 month | 1 month |
Number of file operation logs | 1000 | 1000 |
Number of non-file operation logs | 1000 | 1000 |
Database capacity | 20,092 MB | 94,393 MB |
Estimating the capacity of screen capture data
This section describes how to estimate the capacity of screen capture data. The following is the standard of capacity estimation for screen capture data.
1 piece of screen capture data: 150 KB (when the image resolution of client (CT) is XGA)
Example of capacity estimation
Number of clients (CTs): 1000
The number of times for 1 client (CT) to collect screen capture data per day (prediction value): 2
Storage period for screen capture data: 90 days
Estimation result
1000 (number of the clients (CTs)) x 2 (capture times/day) x 90 (days to save) x 150 KB = 26 GB
Data capacity of backup original file
This section describes data capacity of backup original files.
The size of the backup original file will be the size of the exported files, plus the size of the sent emails and the received emails.
When exporting 10 MB files from the client (CT), the 10 MB files will be saved to the folder for saving attached data of the Management Server.
When exporting 10 MB files from the client (CT), the 10 MB files will be saved to the log saving directory of the client.
Capacity of clipboard original data
This section describes the capacity of original data when the clipboard is used. The total value of Example 1), Example 2) and Example 3) is the capacity of clipboard original data. Clipboard original data will be imported to the client (CT) in virtual and physical environment.
Image data at 1 operation: 150 KB (when the image resolution of client (CT) is XGA)
Example of capacity estimation
Number of clients (CTs): 1000
The number of times for 1 client (CT) to copy image data per day (prediction value): 2
Storage period: 90 days
Estimation result
1000 (number of clients (CTs)) x 2 (times of clipboard operation per day) x 90 (days to save) x 150 KB x 2 (collect in virtual/physical environment) = 52 GB
Text data at 1 operation: 1 KB
Examples of capacity estimation
Number of clients (CTs): 1000
The number of times for 1 client (CT) to copy text data per day (prediction value): 2
Storage period: 90 days
Estimation result
1000 (number of clients (CTs)) x 2 (times of clipboard operation per day) x 90 (days to save) x 1 KB x 2 (collect in virtual/physical environment) = 352 MB
File path at 1 operation: 80 bytes
Example of capacity estimation
Number of the clients (CTs): 1000
Frequency for each client (CT) to copy files per day (estimated value): 2
Storage period: 90 days
Estimation result
1000 (number of clients (CTs)) x 2 (times of clipboard operation per day) x 90 (days to save) x 80 bytes x 2 (collect in virtual/physical) = 28 MB
Estimating database capacity
The standard for estimating the database capacity is shown in the following table. Estimate and compare the number of the clients (CTs) expected for operation, number of months to save operation logs, number of non-file operation logs, number of file operation logs and required database capacity that are recorded in the following.
If there are multiple Log Analyzer Servers, it is necessary to estimate the database capacity of each server.
Number of clients (CTs) | 100 | 100 |
Number of months to save operation logs | 3 months | 6 months |
Number of file operation logs | 500 | 500 |
Number of non-file operation logs | 500 | 500 |
Database capacity | 22,933 MB | 38,898 MB |
Number of clients (CTs) | 500 | 500 |
Number of months to save operation logs | 3 months | 6 months |
Number of file operation logs | 1000 | 1000 |
Number of non-file operation logs | 1000 | 1000 |
Database capacity | 213,513 MB | 373,158 MB |
Estimating temporary disk capacity required for sending log data
This section describes how to estimate the disk capacity required for temporary workspace on the Management Server when sending log files from the Management Server to the Log Analyzer Server.
The following information is required when estimating temporary disk capacity
Number of clients (CTs) of Systemwalker Desktop Keeper
Number of file operation logs per day
Number of non-file operation logs per day
The method of estimating the temporary disk capacity required for each Management Server is shown below.
Temporary disk capacity= (A) capacity of operation log information x number of clients x (B) number of days to output
(A) Capacity of operation log information
Capacity of operation log is the capacity of operation log information obtained from one client (CT) per day
The formula for calculating the capacity of operation log information is shown below.
Capacity of operation log information capacity= average record length x (number of non-file operation logs+ number of file operation logs)
(B) Number of days to output
The number of days to output is supposed to be 1.
Average record length: 400 bytes
Number of non-file operation logs: 1000
Number of file operation logs: 500
Number of clients: 500
Estimation results
Temporary disk capacity = 400 bytes x (1000+ 500) x 500 x 1 day ~= 280[MB]