Windows
Item | Requirement | Remarks | |
|---|---|---|---|
CPU |
| ||
Available disk space | Installation directory | 350MB | |
Variable file storage directory | 350MB + the space required for database + the space required for archive files (+ the space required for logs (*)) *: This requirement applies when Agent functions are used on an Enterprise Manager. | Refer to "2.4.1.2 Estimating the size of the performance database/archive file" for the formula for estimating the required size of the database and archive files. Refer to "2.4.1.3 How to estimate the amount of space required for the log data "Troubleshoot" directory" for the formula for estimating the required size of logs. Note Only the NTFS file system is supported. | |
Available memory space | 200MB min. | ||
Solaris
Item | Requirement | Remarks | |
|---|---|---|---|
CPU | SPARC64 600MHz or higher | ||
Available disk space | Installation directory | 300MB | |
Definition file storage directory | 50MB | ||
Variable file storage directory | 100MB + the space required for the database + the space required for archive files (+ space required for logs (*)) *: This requirement applies when Agent functions are used on an Enterprise Manager. | Refer to "2.4.1.2 Estimating the size of the performance database/archive file" for the formula for estimating the required size of the database and archive files. Refer to "2.4.1.3 How to estimate the amount of space required for the log data "Troubleshoot" directory" for the formula for estimating the required size of logs. | |
Available memory space | 300MB min. | ||
Linux
Item | Requirement | Remarks | |
|---|---|---|---|
CPU |
| ||
Available disk space | Installation directory | 300MB | |
Definition file storage directory | 50MB | ||
Variable file storage directory | 100MB + the space required for the database + the space required for archive files (+ space required for logs (*)) *: This requirement applies when Agent functions are used on an Enterprise Manager. | Refer to "2.4.1.2 Estimating the size of the performance database/archive file" for the formula for estimating the required size of the database and archive files. Refer to "2.4.1.3 How to estimate the amount of space required for the log data "Troubleshoot" directory" for the formula for estimating the required size of logs. | |
Available memory space | 200MB min. | ||
Enterprise Managers require disk space for performance database/archive file
The size of this database depends on the number of Agents/Proxy Managers and on the number of instances of the resources being managed.
Enterprise Managers store only the information displayed in the Summary view, and so Enterprise Managers require less disk space for each Agent/Proxy Manager than Managers. . On the other hand, disk space is required for all of the Agents and Proxy Managers under all of the Managers.
Use the following procedure to make an estimate:
Point
The storage location of the performance database and the archive files can be changed in order to distribute the disk I/O and disk size.
Refer to "6.6.1 Changing the PDB/Archive File Storage Location" for details.
Procedure for estimating the size of the performance database/archive file
Estimate the space necessary for each Agent/Proxy Manager to be managed.
Estimate of number of records acquired in one collection
Using the table below for estimating summary data, get the overall total of the number of summary data records acquired in one collection (MR) by multiplying the number of instances of resources to be managed by the summary data record coefficient.
Point
For example, to estimate the amount of data required to manage a server with Symfoware Server installed, determine the totals for each resource shown in the "OS (Windows)" and "Symfoware Server" rows of the following table by multiplying the number of instances by the corresponding coefficient, and then add up these totals.
Calculate the volume used with the following formula from the number of records in one collection.
Volume of the performance database (PDB)
Summary data [KB] = (MR * 50[KB]) * Summary data retention period[days]
Point
Default retention times are as follows:
Summary data : 3[days]
Archive size
Archive size [MB] = (MR * 45[KB]) * 4[days]
Add up the result of the calculations for all Agents/Proxy Managers. The result of this is the space necessary for the performance database and archive files on the Manager.
Summary data estimation
Managed resource | Instance | Summary data Coefficient |
|---|---|---|
OS <Agent for Agent-based Monitoring> | 1 (fixed value) | 30 |
OS <Agent for Agentless Monitoring> | 1 (fixed value) | 6 |
VMware ESX/ESXi | 1 (fixed value) | 6 |
Number of guests | 6 | |
VMware vCenter | Number of clusters | 4 |
Number of resource pools | 8 | |
Hyper-V <Agent for Agent-based Monitoring> | 1 (fixed value) | 10 |
Number of guests | 10 | |
Hyper-V <Agent for Agent-based Monitoring> | 1 (fixed value) | 8 |
Number of guests | 2 | |
Red Hat virtualization function (KVM) <Agent for Agent-based Monitoring> | Number of guests | 10 |
Red Hat virtualization function (KVM) <Agent for Agent-based Monitoring> | 1 (fixed value) | 6 |
Number of guests | 6 | |
Red Hat virtualization function (Xen) <Agent for Agent-based Monitoring> | Number of guests | 10 |
Red Hat virtualization function (Xen) <Agent for Agent-based Monitoring> | 1 (fixed value) | 6 |
Number of guests | 6 | |
Solaris container <Agent for Agent-based Monitoring> | Number of zones | 10 |
Solaris container <Agent for Agentless Monitoring> | Number of zones | 2 |
Solaris container (Solaris 10) <Agent for Agent-based Monitoring> | Number of zones | 10 |
Service operational management | Number of operational monitoring targets | 10 |
End user response management | Number of Browser Agents * number of monitored URLs | 1 |
Web transaction management | Number of services | 2 |
Interstage Application Server (EJB application) | Number of applications * number of methods * number of processes * number of threads | 2 |
Interstage Application Server (CORBA application) | Number of applications * number of operations * number of processes * number of threads | 2 |
Interstage Application Server (transaction application) | Number of applications * number of operations * number of processes | 2 |
Interstage Application Server (IJServer) | Number of Work Units | 2 |
Interstage Application Server (IJServer cluster) | Number of Server Instances | 2 |
Interstage Business Application Server /Application Framework Suite | Number of target servers | 2 |
Interstage Service Integrator | Number of sequences | 10 |
Number of queues | 10 | |
Oracle WebLigic Server | Number of management servers + number of managed servers | 2 |
Microsoft .NET Server | Number of instances | 10 |
SAP | Number of SAP instances | 8 |
Symfoware Server | Number of RDB systems | 2 |
Number of RDB systems * number of processes connected | 2 | |
Oracle Database | Number of instances (SIDs) | 4 |
Microsoft SQL Server | Number of instances | 10 |
Systemwalker Operation Manager | 1 (fixed value) | 4 |
Systemwalker Resource Coordinator(Network) | Number of network interfaces | 4 |
Systemwalker Resource Coordinator(Storage) ETERNUS SF Storage Cruiser | Number of RAID groups | 4 |
ServerView Resource Orchestrator | Number of VM pools | 2 |
Number of storage pools | 2 | |
Number of network pools | 2 | |
Number of server pools | 2 | |
Number of address pools | 2 | |
User Data | Amount of data stored in PDB in 10 minutes | 1 |
Space for the log that temporarily stores collected data is required when using Agent functions on an Enterprise Manager.
The space needed for log data depends on the number of resources instances to be managed and the retention period.
Use the following procedure to make an estimate:
Point
Log data (Troubleshoot) contains more detailed operating system information collected at 1-minute intervals than the information stored in the Manager database, which is collected at 10-minute intervals. Use this information when it is necessary to check more detailed information.
For this reason, decide the retention period after taking into account the available disk size and also what the purpose of the data is.
Procedure for estimating the amount of space required for the log data
Estimate the number of records acquired in one collection.
Using the table below for estimating log data, get the overall total of the number of log data records acquired in one collection (TR) by multiplying the number of instances of resources to be managed by the log data coefficient.
Use the following formulas to calculate the amount of space required from the number of records obtained in a single collection operation.
Log data[MB] = (TR * 0.5[MB]) * (Retention period + 1)[days]
Log data estimation
Point
Log data (Troubleshoot) requires the retention period plus one additional day because it also holds the data that is being stored on any given day. The default retention period for log data is 7 days.
Managed resource | Instance | Log data coefficient |
|---|---|---|
Windows | 1 (fixed value) | 2 |
Number of CPUs | 2 | |
Number of logical drives | 2 | |
Number of physical drives | 1 | |
Number of processes | 1 | |
Number of network interfaces | 1 | |
Number of page files | 2 | |
Solaris | 1 (fixed value) | 13 |
Number of CPUs | 2 | |
Number of cores | 1 | |
Number of (mounted) logical disks | 1 | |
Number of physical disks (partitions) | 1 | |
Number of processes | 1 | |
Number of network interfaces | 1 | |
Number of zones | 1 | |
Linux | 1 (fixed value) | 11 |
Number of CPUs | 3 | |
Number of (mounted) logical disks | 1 | |
Number of physical disks (partitions) | 2 | |
Number of processes | 1 | |
Number of network interfaces | 1 |
