Skip Navigation Links | |
Exit Print View | |
Using Sun QFS and Sun Storage Archive Manager With Oracle Solaris Cluster Sun QFS and Sun Storage Archive Manager 5.3 Information Library |
1. Using SAM-QFS With Oracle Solaris Cluster
2. Requirements for Using SAM-QFS With Oracle Solaris Cluster
3. Configuring Sun QFS Local Failover File Systems With Oracle Solaris Cluster
4. Configuring Sun QFS Shared File Systems With Oracle Solaris Cluster
5. Configuring SAM-QFS Archiving in an Oracle Solaris Cluster Environment (HA-SAM)
How to Confirm the Catalog and Stager Symbolic Links
How to Configure SAM-QFS Archiving in an Oracle Solaris Cluster Environment
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.