HP Storage Essentials SRM 6.0 User Guide for Enterprise Edition and Standard Edition SRM Software (July 2008)

HP Storage Essentials SRM 6.0 User Guide 189
Log file timestamp - A timestamp (YYMMDD-HHMMSS) is inserted into the filename at its
creation, making its origin more quickly identified. (i.e., appstorm.20071012-122025.log).
Log file sort criteria - Logfiles sort in order of their creation, based upon the timestamp in their
filename.
Log file configurable parameters - Configurable parameters for all log files are these:
• Maximum size of the logfile before it rolls over (MaxFileSize). This parameter resides in
log4j.xml and is used to limit the size of an individual log file.
• Maximum total amount of space the logfile can use (MaxTotalSize). This parameter
resides in log4j.xml is is used to limit the total size of a set of log files (e.g., all appstorm
logs).
Log file “appenders” manage the log file rollover when the MaxFileSize and MaxTotalSize
parameters are reached. These parameters can be changed for any log file by using the
appstorm.<timestamp>.log appenders at the following directory:
<management_server_install_directory>/JBossandJetty/server/appiq/conf/log4j
.xml
At the log4j.xmldirectory indicated above, change the appender values to the new desired
values:
<parem name=”MaxFileSize” value=”100MB”/> <!--Max size of a file before it is rolled over -->
<parem name=”MaxTotalSize” value=”900MB”/> <!--Max size of a all these log
files, oldest is deleted when size is exceeded -->
Example 1 (Log file rollover based on size) - Assume the appstorm.<timestamp>.log file
MaxFileSize=100MB and MaxTotalSize=900MB.
• If the size of the current appstorm.<timestamp>.log file exceeds 100MB before the next day
starts, a new appstorm.<timestamp>.log file is created.
• If any rollover occurs, and the total size of all appstorm.<timestamp>.log files exceeds 900
MB, the oldest appstorm.<timestamp>.log files are deleted until the total size is below 900
MB.
• Whenever a time-based or size-based rollover occurs, a footer is appended to the current
file, and a header is placed on the new file. These headers and footers describe why the
rollover occurred and the logfile to, or from, which it is being rolled.
Example 2 (Log file rollover based on time) - Assume a new day occurred. The current
logfile (appstorm.20071012-154625.log) would receive this footer:
****Log File Rollover due to Time****
*****Next Log
File:C:/hp/StorageEssentials/logs/appstorm.20071013-000055.log****
The next logfile (appstorm.20071013-000055.log) would receive this header:
****Log Fle ROllover due to Time****
****Previousl Log
File:C:/hp/StorageEssentiaals/logs/appstorm.2007-154625.log****