2 Monitoring File System Operations

Correctly configured Oracle HSM file systems need little administrative intervention, however you will need to monitor each system for abnormalities. In general, you monitor two things:

  • Availability — The system can lose core functionality when key components such as a host system, network interface, file system, or storage subsystem become unavailable. The administrative interfaces and logs display availability alerts.

  • Utilization — Even when the system is functioning normally, excessive usage can strain resources and hinder the archiving process. Monitor usage trends and rates to prevent usage issues.

Oracle HSM provides the following monitoring interfaces:

Oracle HSM Manager

Oracle HSM Manager is a browser-based GUI that lets administrators monitor and control all aspects of file-system operations. The GUI is available in for releases 6.1.3 and below. Refer to the help system for more information on the GUI.

samu

The samu operator utility is a text-based, menu-driven configuration and management interface that you launch from the command line. It helps monitor Oracle HSM devices, file system activity, and error messages.

The samu utility is in some respects similar to the UNIX vi editor. You select displays, set display options, navigate within and between displays, enter commands, refresh displays, and quit the utility using similar control key sequences. The last line of each display window displays error messages. Displays refresh automatically unless an error occurs, in which case the display halts until the operator takes further action. When desired, you can take snapshots of display windows for later reference.

The h command opens help screens that list all of the keyboard short cuts, commands. and parameters. You can also consult the samu man page and the Oracle Hierarchical Storage Manager and StorageTek QFS samuCommand Reference in the Oracle HSM Customer Documentation Library (http://docs.oracle.com/en/storage/#sw) for additional information.

The following is a typical samu monitoring display:

Archiver status                  samu      5.4     12:24:10 Mar 19 2014
 
sam-archiverd: Waiting for resources
 
sam-arfind:  samma1 mounted at /samma1
Files waiting to start 0    schedule 70,524    archiving 0
Monitoring file system activity.
 
sam-arfind:  DISKVOL1 mounted at /diskvols/DISKVOL1
Files waiting to start 0    schedule 0    archiving 0
Monitoring file system activity. 

                           samu on samqfshost1

Log and Trace Files

The Oracle HSM software performs comprehensive logging and, when configured, tracing. So you may wish to monitor the following files, particularly when problems arise:

  • /var/adm/messages

  • /var/adm/sam-log

  • /var/opt/SUNWsamfs/trace/ (holds trace files for the daemons and processes)

  • /var/opt/SUNWsamfs/devlog/ (holds logs for the devices configured in the /etc/opt/SUNWsamfs/mcf file)

  • /var/opt/SUNWsamfs/archiver.log

  • /var/opt/SUNWsamfs/stager.log

  • /var/opt/SUNWsamfs/recycler.log

  • additional archiving logs specific to file systems (if configured).

For information on configuring logging and tracing, see the Oracle Hierarchical Storage Manager and StorageTek QFS Installation and Configuration Guide in the Oracle HSM Customer Documentation Library (http://docs.oracle.com/en/storage/#sw).