Disk space (Agent for Server System (Windows))
return to main contents page
return to "Application server" contents page
This section explains how to estimate the disk space requirement for Agent for Server System running on a Windows host.
Disk space requirements for the entire system
Table 1 Agent for Server System disk space requirements for the entire system (Windows)
Status of Agent
for Server System
Disk space requirements (megabytes)
Windows
Server
2008
Windows Server
2008 (when
installing Agent
for Microsoft
Exchange Server)
Windows
Server 2012
Windows Server
2012 (when
installing Agent
for Microsoft
Exchange Server)
During installation
292 312 292 312
Operating under
initial conditions*
280+ W 300+ W 280+ W 300+ W
Legend: W: Disk space requirements for the Store database (megabytes)
To determine the disk space requirements for the Store database, add up the disk space requirements calculated for the individual record types.
*The following records are set to be collected as they are in their initial condition. For the disk space requirements used by the Store database, estimate them for each record.
- File System Configuration (PD_FSC)
- IP Address Configuration (PD_IAC)
- System Configuration Detail (PD)
Agent for Platform (Windows) records:
- System Overview (PI)
- Logical Disk Overview (PI_LOGD)
- Physical Disk Overview (PI_PHYD)
Agent for Microsoft Exchange Server records:
- Database (PI_DB)
- MSExchangeIS (PI)
- MSExchangeIS Mailbox (PI_ISM)
- MSExchangeIS Public (PI_ISP)
Disk space requirements for each installation folder
Table 2 Agent for Server System disk space requirements for each installation folder (Windows)
Folder name Status of
Agent for
Server System
Disk space requirements (megabytes)
Windows
Server
2008
Windows Server
2008 (when
installing Agent
for Microsoft
Exchange Server)
Windows
Server 2012
Windows Server
2012 (when
installing Agent
for Microsoft
Exchange Server)
%SystemDrive% During
installation
122 132 122 132
%TEMP% During
installation
40 40 40 40
Installation folder for
Tuning Manager
series programs
During
installation
130 140 130 140
Operating under
initial conditions
280 + W 300 + W 280 + W 300 + W
Legend: W: Disk space requirements for the Store database (megabytes)
To determine the disk space requirements for the Store database, add up the disk space requirements calculated for the individual record types.
Disk space requirements for Store database version 1.0
All records of one record type are stored in the same file in the Store database version 1.0.
Table 3 Disk space requirements for the Store database shows the formula for estimating the amount of disk space required for the Store database version 1.0 for each record type.
Table 3 Disk space requirements for the Store database
Record type Formula for estimating disk space
requirements (bytes)
PI record type  (X1 + ..... + Xa + 3,500 xa)
PD record type  (Y1 + ..... + Yb + 700 xb)
PL record type  (Z1 + ..... + Zc + 700 xc)
Legend: X: Disk space for each record of the PI record type that collects historical data
X can be calculated by the following formula:
X = {e xf + (d + 1900) x {(e x f) / (65,250 -d) + 1} (see 1)} xg x 1.5
Y: Disk space for each record of the PD record type that collects historical data
Y can be calculated by the following formula:
Y = {e xh + (d + 1900) x {(e x f) / (65,250 -d) + 1} (see 1) x (h/f) (see 2)}x 1.5
Z: Disk space for each record of the PL record type that collects historical data
Z can be calculated by the following formula:
Z = {e xh + (d + 1900) x {(e x f) / (65,250 -d) + 1} (see 1) x (h/f) 2} x 1.5
a: Number of records of the PI record type that collect historical data 
b: Number of records of the PD record type that collect historical data 
c: Number of records of the PL record type that collect historical data
d: Size of the fixed part of each record that collects historical data (see 3)
e: Size of the variable part of each record that collects historical data (see 3)
f: Number of instances for each record that collects historical data (1 for a single instance record) (see 4)
g: Among records of the PI record type, number of stored records for each record that collects historical data (see 5)
h: Among records of the PD record type, number of stored records for each record that collects historical data (see 6)
Notes: 1. In the {(e x f) / (65,250 -d) + 1} calculation, the decimal part is discarded.
2. In the (h/f) calculation, the decimal part is discarded.
3. For details about the sizes of the fixed and variable parts of each record of Agent for RAID Map and Agent for Platform (Windows), see the chapter that describes records in the Tuning Manager Operating System Reports Reference.  
For details about the sizes of the fixed and variable parts of each record of Agent for Microsoft Exchange Server, see the chapter that describes records in the Tuning Manager Application Reports Reference.
4. For Agent for RAID Map, the number of instances for each record can be estimated by using the commands shown in Table 4 Commands for estimating the number of instances for each record (Agent for RAID Map) .
5. For records of the PI record type, the collected data is summarized automatically over a certain fixed period (hour, day, week, month, and year).  Thus, you must take into consideration the number of records to be stored over the applicable period. 
Table 9 Defaults for retention period and number of records for PI record type lists the default values for the retention period and number of records.
6. For details about the number of stored records, see the chapter that describes management of the Store database, and the section that describes the properties of the Agent Store service in the Tuning Manager Agent Administration Guide. 
Table 10 Defaults for number of stored records for each PD record type lists the default number of records be stored, for records of each PD record type.
Table 4 Commands for estimating the number of instances for each record (Agent for RAID Map)
Record name (Record ID) Command Description
File System Configuration(PD_FSC) None (The number of devices) + (the number of drive letters)
IP Address Configuration(PD_IAC) ipconfig The number of IP addresses returned by this command.
The maximum number is 32.
System Configuration Detail (PD)  None 1 (because the record has only a single instance)
For Agent for Platform (Windows), the number of instances for the records shown in Table 5 Records whose number of instances can be checked 
in the performance window (Agent for Platform (Windows)) can be estimated that corresponds to each record.based on the number of instances for the performance object
‚”o check the number of instances for the performance object, in the Performance console, use System Monitor and Performance Logs and Alerts.
Table 5 Records whose number of instances can be checked in the performance window (Agent for Platform (Windows))
Record name (Record ID) Performance object corresponding to the record Description
Logical Disk Overview(PI_LOGD) LogicalDisk Number of instances
Physical Disk Overview(PI_PHYD) PhysicalDisk Number of instances
ICMP Overview (PI_ICMP) ICMP 1 (because the record has only a single instance)
IP Overview (PI_IP) IP or IPv4 1 (because the record has only a single instance)
IP Version 6 Overview (PI_IP6) IP or IPv6 1 (because the record has only a single instance)
TCP Overview (PI_TCP) TCP or TCPv4 1 (because the record has only a single instance)
TCP Version 6 Overview(PI_TCP6) TCP or TCPv6 1 (because the record has only a single instance)
UDP Overview (PI_UDP) UDP or UDPv4 1 (because the record has only a single instance)
Network Interface OverviewPI_NETI) Network Interface Number of instances
NBT Overview (PI_NBT) NBT Connection Number of instances
WINS Server Overview(PI_WINS) WINS Server 1 (because the record has only a single instance)
Browser Overview (PI_BRSR) Browser 1 (because the record has only a single instance)
Server Work Queues Overview(PI_SVRQ) Server Work Queues Number of instances
System Overview (PI) �g_total�h instances for Redirector, Server, Cache, Memory, Objects, System, and Processor 1 (because the record has only a single instance)
Processor Overview (PI_PCSR) Processor Number of instances
Page File Detail (PD_PAGF) Paging File Number of instances
Active Server Pages (PI_ASP2) Active Server Pages 1 (because the record has only a single instance)
Process Detail (PD) Process Number of instances
Process Detail Interval (PD_PDI) Process Number of instances
Process End Detail (PD_PEND) Process Number of instances that terminate during the collection interval
Table 6 Records whose number of instances can be checked in a different window (Agent for Platform (Windows)) shows the records for which the number of instances can be estimated in a window other than the Performance console.
Table 6 Records whose number of instances can be checked in a different window(Agent for Platform (Windows))
Record name (Record ID) Window to use Description
Event Log (PD_ELOG) Administrative Tools and then Event Viewer Number of logs output during the collection interval
Device Detail (PD_DEV) System Tools, System Information, Software Environment, and then Drivers Number of registered drivers
Service Process Detail (PD_SVC) Administrative Tools and then Services Number of registered services
Application Summary (PD_APP) Administrative Tools and then Services Specified number of services
PD_APS Check the Processes tab in Windows Task Manager. Number of displayed processes. (The check box Show processes from all users must be selected.)
PD_APSI Select the host name Windows (Agent Collector service) in the Service Hierarchy window of Performance Reporter. Next, check the tree for the application name generated under the Application monitoring setting tree in Advanced application monitoring. Total number of processes or services that satisfy the MonitoringXX condition registered in each application (total number of Monitoring counts in PD_APPD record).
PD_APP2 Select the host name Windows (Agent Collector service) in the Service Hierarchy window of Performance Reporter. Next, check the Application monitoring setting tree in Advanced application monitoring. Number of applications registered in the application monitoring setting. However, if the MonitoringXX field is not None and there is no combination in which a MonitoringXX condition is specified, the application is not targeted.
PD_APPD Select the host name Windows (Agent Collector service) in the Service Hierarchy window of Performance Reporter. Then check the tree for the application name generated under the Application monitoring setting tree in Advanced application monitoring.  Total number of MonitoringXX conditions registered in each application. However, if the MonitoringXX field is None, the application is not targeted.
PD_ASVC Check Service in Management Tools. Number of registered services
The number of instances for each record for Agent for Microsoft Exchange
Server differs depending on the monitoring target.
Table 7 Number of instances for each record (Microsoft Exchange Server 2007 or later)
Record name (Record ID) Microsoft Exchange Server 2007 or 2010
Number of instances
Microsoft Exchange Server 2013 or later
Number of instances
Database (PI_DB) 1 1
Epoxy (PI_EPOX) 0 0
MSExchangeIS (PI) 1 0
MSExchangeIS Mailbox (PI_ISM) 1 0
MSExchangeIS Public (PI_ISP) 1 0
Process (PD) 2 2
Managed Store Information (PI_MSI) 0 1
Table 8 Defaults for retention period and number of records for PI record type

Data type Retention period Number of records to be stored (when collection interval is 1 minute)
Minute-by-minute 1 day*1 1,440
Hourly 7 days 168
Daily 1 year 366
Weekly 1 year 52
Monthly 1 year 12
Yearly Unlimited (years-collected) x 1
*1 If you change the retention period from the default value, the Store database size greatly increases.
Therefore, substantial processing time is necessary to convert the data model when installing the updated version.
For an estimate of the required time, see the description of �gBefore starting an upgrade or overwrite installation�hin Preparing to install or upgrade agents.
Also, twice as much capacity is temporarily required in the disk storage Store database.
Therefore, make sure that enough capacity exists.
Table 9 Defaults for number of stored records for each PD record type
Agent Record name (Record ID) Number of records to be stored
Agent for RAID Map File System Configuration
(PD_FSC)
10,000
IP Address Configuration
(PD_IAC)
1,000
tem Configuration Detail (PD) 200
Agent for Platform
(Windows)
Process Detail Interval (PD_PDI) 100,000
Other than Process Detail Interval(PD_PDI) 10,000
Agent for Microsoft
Exchange Server
Process (PD) 10,000
Disk space requirements for Store database version 2.0
All records are stored in different directories and files for each summarization unit, date, and record type in the Store database version 2.0.
The following provides estimates for the following information: the amount of disk space required for the Store database version 2.0, the number of files and directories to be created, and the number of files to be opened by the Store service.
• Disk space requirements
The amount of disk space required for the Store database equals the total amount of disk space required for each record type. 
For the PI record type, the disk space requirements equal the total amount of disk space required for each summarization unit.
The formula for estimating the disk space requirements (X) for each record type (unit: bytes) is as follows:
X = {(e + 2) xf + (d + 60) x {((e + 2) x f) / (65,250 -d) + 1} (see 1)} xa / b x (c + 1) x 1.1
a: This value differs for each record type or summarization unit. For details, see Table 11 Values set to a, b, and c.
b: This value differs for each record type or summarization unit. For details, see Table 11 Values set to a, b, and c (see 2).
c: The setting value for the retention period of historical data (see 3). 
   The units specified for this value differ for each record type or summarization unit. For details see Table 11 Values set to a, b, and c.
d: Size of the fixed part of each record that collects historical data (see 4)
e: Size of the variable part of each record that collects historical data (see 4)
f: Number of instances for each record that collects historical data (1 for a single instance record) (see 5). 
Note that if the number of instances is 2 or more, the value will be rounded up to a multiple of 4. For example, if the number of instances is 2, f will be 4. If the number of instances is 1, f will be 1.
Table 11 Values set to a, b, and c
Record type Summarization
unit
a b c
PI Minute 1,440 1 + (g - 1) / 60 (see 2) Retention period (unit:days)
Hour 24 1 + (g - 1) / 3,600 (see 2) Retention period (unit:days)
Day 7 1 + (g - 1) / 86,400 (see 2) Retention period (unit:weeks)
Week 1 1 + (g - 1) / 604,800 (see 2) Retention period (unit:weeks)
Month 1 1 + (g - 1) / 2,592,000 (see 2) Retention period (unit:months)
Year 1 1 + (g - 1) / 31,622,400 (see 2) Retention period (unit:years)
PD --- 1,440 g / 60 Retention period (unit:days)
Legend: g: The setting value for collection interval of historical data (unit: seconds)
---: Not applicable
Notes: 1. In the calculated value for {((e + 2) xf) / (65,250 - d) + 1}, discard digits after the decimal point.
2. In the calculated value for b of the PI record type, discard digits after the decimal point.
3. Table 12 Default retention period of the PI record type records and Table 13 Default retention period of the PD record type records list the default values for the retention period (for Store database version 2.0).
4. For details about the fixed part and variable part of each record, see the chapter that describes records in the Tuning Manager Operating System Reports Reference and Tuning Manager Application Reports Reference.
5. For details about the number of instances for each record, see the explanation in Disk space requirements for Store database version 1.0.
Table 12 Default retention period of the PI record type records
Data type Retention period
Minute-by-minute 1 day
Hourly 7 days
Daily 54 weeks
Weekly 54 weeks
Monthly 12
months Yearly No limit
Table 13 Default retention period of the PD record type records
Agent Record name (Record ID) Retention period(unit: days)
Agent for RAID Map File System Configuration
(PD_FSC)
7
IP Address Configuration
(PD_IAC)
7
System Configuration Detail (PD) 7
Agent for Platform (Windows)   Device Detail (PD_DEV) 2
Event Log (PD_ELOG) 31
Page File Detail (PD_PAGF) 2
Process Detail (PD) 2
Process Detail Interval (PD_PDI) 2
Process End Detail (PD_PEND) 2
Service Process Detail (PD_SVC) 2
Application Summary (PD_APP) 10
Agent for Microsoft Exchange Server Process (PD) 7
- Number of files
Following is the formula to estimate the number of files (N) to be created by the Store database:
N = 20 + 2 x (
(A11 + A12 + ... +A1m + m) + 
(A21 + A22 + ... +A2m + m) +
(A31 + A32 + ... +A3m + m) +
(A41 + A42 + ... +A4m + m) + 
(A51 + A52 + ... +A5m + m) + 
(11 x m) +
(B1 + B2 + ... +Bn + n)
 )
m: Number of records collected by the PI record type record
n: Number of records collected by the PD record type record
A11 - A1m: The setting value of the retention period for the minute-by-minute record of each record of the PI record type (unit: days)
A21 - A2m: The setting value of the retention period for the hourly record for each record of the PI record type (unit: days)
A31 - A3m: The setting value of the retention period for the daily record for each record of the PI record type (unit: weeks)
A41 - A4m: The setting value of the retention period for the weekly record for each record of the PI record type (unit: weeks)
A51 - A5m: The setting value of the retention period for the monthly record for each record of the PI record type (unit: months)
B1 - Bn: The setting value of the retention period for each PD record type record (unit: days)
- Number of directories
Following is the formula to estimate the number of directories (N) to be created by the Store database:
N = 25 + 2 x ((A1max) + (A2max) + (A3max) + (A4max) + (A5max) + 11 + (Bmax))
A1max: The maximum setting value of the retention period for the data where the summarization unit of a record collected by the PI record type is minutes (unit: days)
A2max: The maximum setting value of the retention period for the data where the summarization unit of a record collected by the PI record type is hours (unit: days)
A3max: The maximum setting value of the retention period for the data where the summarization unit of a record collected by the PI record type is days (unit: weeks)
A4max: The maximum setting value of the retention period for the data where the summarization unit of a record collected by the PI record type is weeks (unit: weeks)
A5max: The maximum setting value of the retention period for the data where the summarization unit of a record collected by the PI record type is months (unit: months)
Bmax: The maximum setting value of the retention period for each PD record type record (unit: days)
- Number of files to be opened by the Store service
Following is the formula to estimate the number of files (N) to be opened by the Store service:
N = 20 + 2 x (6 x m +n)
m: Number of records collected by the PI record type record
n: Number of records collected by the PD record type record
Disk space (Agent for Server System (UNIX))
This section explains how to estimate the disk space requirement for Agent for Server System running on a UNIX host.
Disk space requirements for the entire system
Table 14 Agent for Server System disk space requirements for the entire system (UNIX)
Status of Agent for Server System Disk space requirements (megabytes) �@
HP-UX Solaris AIX Linux
During installation 452 162 1102 202
Operating under initial conditions* 500 + W 210 + W 1150 + W 250 + W
Legend: W: Disk space requirements for the Store database (megabytes)
To determine the disk space requirements for the Store database, add up the disk space requirements calculated for the individual record types.
*The following records are set to be collected as they are in their initial condition. For the disk space requirements used by the Store database, estimate them for each record.
Agent for RAID Map records:
- �@File System Configuration (PD_FSC)
- �@IP Address Configuration (PD_IAC)
- �@System Configuration Detail (PD) 
Agent for Platform (UNIX) records:
- �@System Summary Overview (PI)
- �@Device Detail (PI_DEVD)
- �@File System Detail - Local (PD_FSL)
- �@File System Detail - Remote (PD_FSR)
Disk space requirements for each installation directory
Table 15 Disk space requirements for each installation directory
Directory name Status of Agent for Server System Disk space requirements (megabytes)
HP-UX (IPF) Solaris AIX Linux
/opt During installation 450 160 1100 200
/var During installation 2 2 2 2
/opt/jp1pc During installation 450 160 1100 200
Operating under initial conditions 500 + W 210 + W 1150 + W 250 + W
Legend: W: Disk space requirements for the Store database (megabytes)
To determine the disk space requirements for the Store database, add up the disk space requirements calculated for the individual record types.
Disk space requirements for Store database version 1.0
All records of one record type are stored in the same file in the Store database version 1.0.
Table 16 Disk space requirements for the Store database shows the formula for estimating the amount of disk space required for the Store database version 1.0 for each record type.
Record type Formula for estimating disk space requirements (bytes)
PI record type (X1 + ..... + Xa + 3,500 xa)
PD record type (Y1 + ..... + Yb + 700 xb)
PL record type (Z1 + ..... + Zc + 700 xc)
Legend: X: Disk space for each record of the PI record type that collects historical data
X can be calculated by the following formula:
X = {e xf + (d + 1900) x {(e x f) / (65,250 -d) + 1} (see 1)} xg x 1.5
Y: Disk space for each record of the PD record type that collects historical data
Y can be calculated by the following formula:
Y = {e xh + (d + 1900) x {(e x f) / (65,250 -d) + 1} (see 1) x (h/f) (see 2)}x 1.5
Z: Disk space for each record of the PL record type that collects historical data
Z can be calculated by the following formula:
Z = {e xh + (d + 1900) x {(e x f) / (65,250 -d) + 1} (see 1) x (h/f) (see 2)}x 1.5
a: Number of records of the PI record type that collect historical data 
b: Number of records of the PD record type that collect historical data 
c: Number of records of the PL record type that collect historical data
d: Size of the fixed part of each record that collects historical data (see 3)
e: Size of the variable part of each record that collects historical data (see 3)
f: Number of instances of each record that collects historical data (1 for a single instance record) (see 4)
g: Among records of the PI record type, number of stored records for each record that collects historical data (see 5)
h: Among records of the PD record type or PL record type, number of stored records for each record that collects historical data (see 6)
Notes: 1.�@In the {(e x f) / (65,250 -d) + 1} calculation, the decimal part is discarded.
2.�@In the (h/f) calculation, the decimal part is discarded.
3.�@For details about the sizes of the fixed and variable parts of each record, see the Tuning Manager Operating System Reports Reference.
4.�@For Agent for RAID Map, the number of instances for each record can be estimated by using the commands shown in Table 17 Commands for estimating the number of instances for each record (Agent for RAID Map).
5.�@For records of the PI record type, the collected data is summarized automatically over a certain fixed period (hour, day, week, month, or year). 
Thus, you must take into consideration the number of records to be stored over the applicable period. Table 19 Defaults for retention period and number of records for PI record type lists the default values for the retention period and the number of records.
6.�@For details about the number of stored records, see the chapter that describes management of the Store database, and the section that describes the properties of the Agent Store service in the Tuning Manager Agent Administration Guide. 
Table 20 Defaults for number of stored records for each PD record type lists the default number of records to be stored, for records of each PD record type.
Table 17 Commands for estimating the number of instances for each record (Agent for RAID Map)
Record name(Record ID) Command Description
HP-UX Solaris AIX Linux
File System Configuration (PD_FSC) None None None None ((number-of-DISKs-to-be- registered-in-DG1)
x (n
umber-of-FSs-to-be- mounted-to-DG1))
+...+ ((
number-of-DISKs-to-be- registered-in-DGn)
x (
number-of-FSs-to-be- mounted-in-DGn))
+ (
number-of-DISKs-not-to- be-mounted-to-FS)
+ (
number-of-FSs-not-to-be- mounted-to-DG)*
IP Address Configuration (PD_IAC) lanscan -i ifconfig interface ifconfig -a ifconfig -a ifconfig -a The number of IP addresses returned by this command. The maximum number is 32.
System Configuration Detail (PD) None None None None 1 (because the record has only a single instance)
Legend: DG: Disk group (If the number of disk groups is n, the disk groups are indicated by DG1 to DGn)
DISK: Logical device to be connected to a server
FS: File system (mount point)
*Use the following formula to estimate the number of instances for Solaris. 
  In the formula, V represents a VxVM volume, and POOL represents a ZFS pool. For example,  for a volume count of n, volumes are represented in the range from V1 to Vn.
((number-of-disks-registered-for-DG1-V1) + ... + (number-of-disks- registered-for-DG1-Vn) 
+ ... + (number-of-disks-not-registered-for-DG1-V)) + ... + ((number-of-disks-registered-for-DGn-V1) 
+ ... + (number-of-disks- registered-for-DGn-Vn) + ... + (number-of-disks-not-registered-for-DGn-V))
+ ((number-of-disks-registered-for-POOL1) �~ (number-of-file-systems- mounted-on-POOL1)) 
+ ... + ((number-of-disks-registered-for-POOLn) * (number-of-file-systems-mounted-on-POOLn)) 
+ number-of-disks-not- mounted-on-a-file-system + number-of-file-systems-not-mounted-on-DG
For Agent for Platform (UNIX), the number of instances for each record can be estimated by using the commands shown in Table 18 Commands for estimating the number of instances for each record (Agent for Platform (UNIX)).
Table 18 Commands for estimating the number of instances for each record (Agent for Platform (UNIX))
Record name(Record ID) Command Description
HP-UX Solaris AIX Linux
Application Summary (PD_APP) None None None None Number of applications registered for Application monitoring setting in the Agent Collector property.
CPU - Per Processor Detail (PI_CPUP) sar -u -M interval count sar -u interval count sar -w -P ALL interval count top -c Number of CPUs returned by this command
Device Detail(PI_DEVD) ioscan -fnC
disk
iostat -x iostat -d interval count iostat ALL For HP-UX, Solaris, and
AIX: Number of disk devices returned by this command
For Linux: Number of disk devices, excluding partitions, returned by this command
Device Summary (PI_DEVS) None None None None 1 (because the record has only a single instance)
File System Detail - Local (PD_FSL) df df df df Number of file systems without host names returned by this command
File System Detail - Remote (PD_FSR) df df df df Number of file systems with host names returned by this command
Logged Messages (PL_MESS) None None None None Number of lines written into the file specified by the Messages File property or the event file
This record cannot be used in Linux because it is not supported.
Network Interface Detail (PI_NIND) lanscan netstat -in ifconfig -a netstat -ni For HP-UX: Number of physical interfaces returned by this command + 1
For Solaris, AIX, and Linux: Number of physical interfaces returned by this command
Network Interface Summary (PI_NINS) None None None None 1 (because the record has only a single instance)
Process Detail(PD) ps -ef ps -ef ps -A ps -ef Number of processes returned by this command
Process Detail Interval (PD_PDI) ps -ef ps -ef ps -A ps -ef Number of processes returned by this command
Process Summary (PD_PDS) None None None None 1 (because the record has only a single instance)
Program Summary (PD_PGM) ps -e ps -e ps -A ps -e Number of unique CMDs displayed by this command
System Summary Overview (PI) None None None None 1 (because the record has only a single instance)
Terminal Summary (PD_TERM) ps -e ps -e ps -Af ps -e Number of unique TTYs displayed by this command
User Summary(PD_USER) ps -ef ps -ef ps -ef ps -ef Number of unique RUIDs displayed by this command
Workgroup Summary (PI_WGRP) None None None None Number of work groups specified in the work group file + 1
Table 19 Defaults for retention period and number of records for PI record type
Data type Retention period Number of records to be stored (when collection interval is 1 minute)
Minute-by-minute 1 day 1,440
Hourly 7 days 168
Daily 1 year 366
Weekly 1 year 52
Monthly 1 year 12
Yearly Unlimited (years-collected) x 1
Table 20 Defaults for number of stored records for each PD record type
Agent Record name (Record ID) Number of records to be stored
Agent for RAID Map File System Configuration
(PD_FSC)
10,000
IP Address Configuration
(PD_IAC)
1,000
System Configuration Detail (PD) 200
Agent for Platform (UNIX) Process Detail Interval (PD_PDI) 100,000
Other than Process Detail
Interval (PD_PDI)
10,000
Disk space requirements for Store database version 2.0
All records are stored in different directories and files for each summarization unit, date, and record type in the Store database version 2.0.
The following provides estimates for the following information: the amount of disk space required for the Store database version 2.0, the number of files and directories to be created, and the number of files to be opened by the Store service.
-  Disk space requirements
The amount of disk space required for the Store database equals the total amount of disk space required for each record type. For the PI record type, the disk space requirements equal the total amount of disk space required for each summarization unit.
The formula for estimating the disk space requirements (X) for each record type (unit: bytes) is as follows:
X = {(e + 2) xf + (d + 60) x {((e + 2) x f) / (65,250 -d) + 1} (see 1)} xa / b x (c + 1) x 1.1
a: This value differs for each record type or summarization unit. For details, see Table 21 Values set to a, b, and c.
b: This value differs for each record type or summarization unit. For details, see Table 21 Values set to a, b, and c (see 2).
c: The setting value for the retention period of historical data (see 3). The units specified for this value differ for each record type or summarization unit. For details see Table 21 Values set to a, b, and c.
d: Size of the fixed part of each record that collects historical data (see 4)
e: Size of the variable part of each record that collects historical data (see 4)
f: Number of instances for each record that collects historical data (1 for a single instance record) (see 5). 
Note that if the number of instances is 2 or more, the value will be rounded up to a multiple of 4. For example, if the number of instances is 2, f will be 4. If the number of instances is 1, f will be 1.
Table 21 Values set to a, b, and c
Record type Summarization unit a b c
PI Minute 1,440 1 + (g - 1) / 60 (see 2)  Retention period (unit:days)
Hour 24 1 + (g - 1) / 3,600 (see 2)  Retention period (unit:days)
Day 7 1 + (g - 1) / 86,400 (see 2)  Retention period (unit:weeks)
Week 1 1 + (g - 1) / 604,800 (see 2)  Retention period (unit:weeks)
Month 1 1 + (g - 1) / 2,592,000 (see 2)  Retention period (unit:months)
Year 1 1 + (g - 1) / 31,622,40 (see 2)  Retention period (unit:years)
PD --- 1,440 g / 60  Retention period (unit:days)
PL --- 1,440 g / 60  Retention period (unit:days)
Legend: g: The setting value for collection interval of historical data (unit: seconds)
---: Not applicable
Notes: 1. In the calculated value for {((e + 2) xf) / (65,250 - d) + 1}, discard digits after the decimal point.
2. In the calculated value for b of the PI record type, discard digits after the decimal point.
3. Table 22 Default retention period of the PI record type records, Table 23 Default retention period of the PD record type records on page 11 and Table 24 Default retention period of the PL record type records list the default values for the retention period (for Store database version 2.0).
4. For details about the fixed part and variable part of each record, see the chapter that describes records in the Tuning Manager Operating System Reports Reference.
5. For details about the number of instances for each record, see the explanation in Disk space requirements for Store database version 1.0.
 
Table 22 Default retention period of the PI record type records
Data type Retention period
Minute-by-minute 1 day
Hourly 7 days 
Daily 54 weeks 
Weekly 54 weeks 
Monthly 12 months
Yearly No limit
Table 23 Default retention period of the PD record type records
Agent Record name (Record ID) Retention period
(unit: days)
Agent for RAID Map File System Configuration
(PD_FSC)
7
IP Address Configuration (PD_IAC) 7
System Configuration Detail (PD) 7
Agent for Platform (UNIX) File System Detail - Local
(PD_FSL)
31
File System Detail - Remote
(PD_FSR)
31
Process Detail (PD) 2
Process Detail Interval (PD_PDI) 2
Process Summary (PD_PDS) 2
Program Summary (PD_PGM) 2
Terminal Summary (PD_TERM) 2
User Summary (PD_USER) 10
Application Summary (PD_APP) 10
Table 24 Default retention period of the PL record type records
Record name (Record ID) Retention period (unit: days)
Logged Messages (PL_MESS) 10
- Number of files
Following is the formula to estimate the number of files (N) to be created
 by the Store database:
  N = 20 + 2 x (
  (A11 + A12 + ... +A1m + m) + 
  (A21 + A22 + ... +A2m + m) +
  (A31 + A32 + ... +A3m + m) + 
  (A41 + A42 + ... +A4m + m) + 
  (A51 + A52 + ... +A5m + m) + 
  (11 x m) +
  (B1 + B2 + ... +Bn + n) + 
  (C1 + C2 + ... +Co + o)
  )
m: Number of records collected by the PI record type record 
n: Number of records collected by the PD record type record 
o: Number of records collected by the PL record type record
A11 - A1m: The setting value of the retention period for the minute-by-minute record of each record of the PI record type (unit: days) 
A21 - A2m: The setting value of the retention period for the hourly record for each record of the PI record type (unit: days)
A31 - A3m: The setting value of the retention period for the daily record for each record of the PI record type (unit: weeks)
A41 - A4m: The setting value of the retention period for the weekly record for each record of the PI record type (unit: weeks)
A51 - A5m: The setting value of the retention period for the monthly record for each record of the PI record type (unit: months)
B1 - Bn: The setting value of the retention period for each PD record type record (unit: days)
C1 - Co: The setting value of the retention period for each PL record type record (unit: days)
- Number of directories
Following is the formula to estimate the number of directories (N) to be created by the Store database:
N = 25 + 2 x ((A1max) + (A2max) + (A3max) + (A4max) + (A5max) + 11 + (Bmax) + (Cmax))
A1max: The maximum setting value of the retention period for the data where the summarization unit of a record collected by the PI record type is minutes (unit: days)
A2max: The maximum setting value of the retention period for the data where the summarization unit of a record collected by the PI record type is hours (unit: days)
A3max: The maximum setting value of the retention period for the data where the summarization unit of a record collected by the PI record type is days (unit: weeks)
A4max: The maximum setting value of the retention period for the data where the summarization unit of a record collected by the PI record type is weeks (unit: weeks)
A5max: The maximum setting value of the retention period for the data where the summarization unit of a record collected by the PI record type is months (unit: months)
Bmax: The maximum setting value of the retention period for each PD record type record (unit: days)
Cmax: The maximum setting value of the retention period for each PL record type record (unit: days)
- Number of files to be opened by the Store service
Following is the formula to estimate the number of files (N) to be opened by the Store service:
N = 20 + 2 x (6 x m +n +o)
m: Number of records collected by the PI record type record 
n: Number of records collected by the PD record type record 
o: Number of records collected by the PL record type record