Warnings, Files on cms, Authors – HP Matrix Operating Environment Software User Manual

Page 143: Release version, See also

Name Available History Percent Valid
node01.co.com 01/17/06 05:30 pm - 01/19/06 10:10 am 100.00%
node02.com 12/18/05 05:00 pm - 01/20/06 01:05 pm 99.96%
billing3 12/10/05 05:00 pm - 01/20/06 01:05 pm 100.00%
node03.com.OTHER 01/15/06 03:05 pm - 01/18/06 12:55 pm 82.83%
cimserver 01/17/06 05:30 pm - 01/19/06 10:10 am 99.78%

Import profile data from the file /tmp/nonIDWorkloadFile.txt for the profile with profileID
nonIDWorkload

capprofile -i -p nonIDWorkload < /tmp/nonIDWorkloadFile.txt

List profile summaries for non-Insight Dynamics workloads:

# capprofile -l -p Non-ID-Workloads-Name

externalBilling2
accounting1
monitoring

WARNINGS

While the capcollect(1M) command is running, write access to profile data using the
capprofile(1M)

command may be delayed.

FILES ON CMS

/var/opt/vse/profile/bin

•

Root directory for storing collected data for both capcollect and capprofile.
Note that the format of these data files may change without notice from release to release.
The file system where these files are stored needs to be sized to hold all the daily utilization
profile data, which for each system, is about 32K per day per workload, taking into account
minimum block size of 4K.
For example, with a CMS monitoring 100 systems, each with an average of 3 workloads,
with a need to keep historical data for one year, the file system where the profile resides
must have space for (100 systems + 300 workloads) * 365 days * 32K = 4.45 Gigabytes. With
a file system that allocates storage in blocks greater than 24K, then use the larger block size.

AUTHORS

capprofile(1M) was developed by Hewlett-Packard Company.

RELEASE VERSION

capprofile(1M ) A.6.0.0.*
HP Insight Capacity Advisor software 6.0, January 2010