Using StorageTek Libraries with HA-SAM

If you are using StorageTek libraries in an HA-SAM environment, the STK daemons need to be notified to use a forced dismount instead of a normal dismount in the case of an involuntary failover. To accomplish this, the /var/run/hasam_running file is created on the active Oracle Solaris Cluster node when the HA-SAM resource is brought online. This is a zero-byte file with root permissions. If this file is detected on a node, sam-stkd and sam-stk_helper use force_media to dismount the tape on the drive. This action allows the successful initialization of the library and the drives after an involuntary failover. The hasam_running file is deleted when a SAM-QFS resource is brought offline on a node.

In order to ensure the correct failover behavior for StorageTek libraries, make sure the /var/run/hasam_running is not deleted if found on an Oracle Solaris Cluster node that has an HA-SAM resource online.