Release Notes

hp StorageWorks File System Extender Release Notes 15
3 Recommendations
This chapter includes recommendations that help improving performance and minimizing problems in the
FSE implementation. It contains the following sections:
• General recommendations, page 15
• Linux-specific recommendations, page 17
• Windows-specific recommendations, page 18
General recommendations
Keeping the FSC and HSMDB journals small
The journals of File System Catalog (FSC) and Hierarchical Storage Manager (HSMDB) can grow quite
large with daily FSE usage. However, they are truncated every time the FSE implementation is backed up
successfully. By backing up the FSE implementation regularly, the size of the journals remains acceptable.
Linux specific
FSC journals are located on the system that hosts an integrated FSE system or an FSE server in the directory
HSM journals are located on the system that hosts an integrated FSE system or an FSE client in the directory
Windows specific
FSC journals are located on the system that hosts an integrated FSE system or an FSE server in the directory
HSM journals are located on the system that hosts an integrated FSE system or an FSE client in the directory
Handling old FSE log, debug and disk buffer files
If tracing of the FSE implementation is enabled, FSE log and debug files can grow quite big through daily
FSE use. The FSE disk buffer files can also occupy a significant amount of disk space if they are
accidentally left on disk.
Linux specific
To prevent the disk from being filled up, HP recommends that you execute the fse_cleantmp.sh script
regularly. Use the crontab command to schedule the script.
fse_cleantmp.sh performs two different tasks:
• It archives FSE log and debug files older than the defined number of days set for the archiving task.
• It deletes archives older than the defined number of days set for the removal task. Originals of the
archived files are always deleted unless they are currently used by an FSE process or are meant to be
used later. FSE disk buffer files are handled in the same manner.
Windows specific
If you are concerned with excessive growth of FSE debug files, consider allocating a dedicated disk
partition/volume to a file system, which can then be mounted to %InstallPath%\var\log\debug.
Shortening the termination delay for FSE commands
FSE uses CORBA technology and its omniORB implementation for its internal interprocess communication.
omniORB also prepares and initializes the environment in which FSE processes is run, and cleans up the
environment after the processes are terminated. This takes time.
/var/opt/fse/part/PartitionName/fsc/journal
/var/opt/fse/part/PartitionName/hsm/journal
%InstallPath%\var\part\PartitionName\fsc\journal
%InstallPath%\var\part\PartitionName\hsm\journal