2.2.1 Hardware

Windows

Item		Requirement	Remarks
CPU		For x86 Intel(R) Pentium III 1GHz or higher For x64 Intel(R) Xeon(R) processor or higher
Available disk space	Installation directory	350MB
Available disk space	Variable file storage directory	350MB + the space required for the log	Refer to "2.2.1.2 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. (+ 900MB ()) : When using agent for Agentless Monitoring management functions (Proxy Manager)

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 log	Refer to "2.2.1.2 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. (+ 600MB ()) : When using agent for Agentless Monitoring management functions (Proxy Manager)

Linux

Item		Requirement	Remarks
CPU		For x86 Intel(R) Pentium III 1GHz or higher For x64 64 bit Intel(R) Xeon(R) processor (EM64T) or higher
Available disk space	Installation directory	300MB
	Definition file storage directory	50MB
	Variable file storage directory	100MB+ the space required for the log	Refer to "2.2.1.2 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. (+ 600MB ()) : When using agent for Agentless Monitoring management functions (Proxy Manager)

Agents require disk space for a log to temporarily hold the data that is collected.

The size of this log depends on the number of instances of the resources being managed.

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.

Determine the retention period, taking the usable disk size and the usage of log data into account.

Procedure for estimating the log data

Estimate the number of records acquired in one collection.
Log data
Use the estimating log data table below to calculate the number of number of log data records acquired in one collection (TR). First multiply the number of instances of resources to be managed by the log data coefficient shown in the table for the resource. Next add together the results of these calculations for all of the resources to obtain TR.
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

2.2.1 Hardware

2.2.1.1 Hardware requirements

2.2.1.2 How to estimate the amount of space required for the log data ("Troubleshoot" directory)