Before You Begin

Be aware of the following requirements and restrictions before configuring this feature:

• The nodes on which HA-SAM will be configured must be running the same version of Oracle Solaris OS and Oracle Solaris Cluster. Mixed versions of Oracle Solaris OS or Oracle Solaris Cluster software are not supported. No operating system other than Oracle Solaris is supported.

• The nodes in the cluster running HA-SAM must have the same type of architecture: SPARC or x64. Mixed architectures are not supported.

• No more than two nodes can be configured.

• Only active-passive configurations are supported, not active-active.

• Active I/O to HA-SAM file systems is supported only on the active node of an HA-SAM file system.

• Only shared QFS file systems are supported. Both ma and ms type file systems are supported. Stand-alone QFS environments are not supported.

• No software volume managers are supported with this configuration.

• Within the HA-SAM environment, the nosam mount option must be specified for any non-HA-SAM QFS file systems.

• The HA-SAM resource, QFS file systems, and HAStoragePlus file systems must all be configured within the same resource group. A separate Oracle Solaris Cluster resource group must be created for non-HA-SAM file systems.

• When using the SUNW.hasam resource type, you cannot specify the bg mount option in the /etc/vfstab file.

• Fibre tape drives are required. Tape drives must be visible to all systems through the fibre fabric, but should not be configured as SAM-QFS shared drives.

• Disk volumes for disk archiving must be visible to all nodes.

• The active metadata server and potential metadata server must not be configured as a SAM-Remote client or server.

• The SAM-QFS catalog and stager directory must be in the default location: /var/opt/SUNWsamfs/. If it is any other location, the cluster nodes will not be able to locate it.

• Before configuring HA-SAM, verify that all SAM-QFS archiving operations are working correctly on the required nodes in the cluster.

• Only highly available (HA) agents are supported; no scalable agents are supported.

• Oracle database software is not supported with this configuration, but the HA-SAM agent is supported as an RMAN target for Oracle backups.

• Voluntary failover forces a failover after 5 minutes in order to avoid problems with other potential HA agents.

• During voluntary failover, active archiving and staging times-out and terminates after less than 5 minutes.

• During failover, all SAM-QFS file systems must be failed over in order to avoid complications with the recycler that could result in loss of data.

• StorageTek network attached tape libraries are supported but not ADIC or Sony 8400 PetaSite Series automated tape libraries.

• HA-SAM environments cannot be managed by the SAM-QFS Manager browser interface.

• During involuntary failover, error messages for idled tape drives may be seen in the /var/adm/messages log file. These messages can safely be ignored. They simply indicate that HA-SAM did not have time to idle the drives before failover.

• After failover, volumes in the catalog may be marked with the E flag. This can occur when the software is unable to write the correct label at the end of a tape. To clear this error, see How to Clear Media Errors in Sun Storage Archive Manager 5.3 Configuration and Administration Guide.

How to Confirm the Catalog and Stager Symbolic Links

In order to configure for high availability, the SAM-QFS catalog and stager queues must be in an HAStoragePlus file system. During the software installation process symbolic links should have been created from /var/opt/SUNWsamfs to the shared HAStoragePlus file system. This must be confirmed before continuing with the configuration process.

1. Verify that the /var/opt/SUNWsamfs/catalog and /var/opt/SUNWsamfs/stager contain a symbolic link to the HAStoragePlus mount point.
2. View the catalog and stager files.

   # ls -l /var/opt/SUNWsamfs/catalog /var/opt/SUNWsamfs/stager

3. Verify that the output shows symbolic links similar to the following example.

   lrwxrwxrwx 1 root other 19 Sep 30 11:05
   /var/opt/SUNWsamfs/catalog -> /sam_shared/catalog
   lrwxrwxrwx 1 root other 18 Sep 30 11:05
   /var/opt/SUNWsamfs/stager -> /sam_shared/stager

   • If the symbolic links exist, proceed toHow to Configure SAM-QFS Archiving in an Oracle Solaris Cluster Environment.
   • If the links do not exist, proceed to the next step.
4. Copy any existing SAM-QFS catalog information to a temporary location.
5. Delete the existing catalog and stager files from their current location.

   # rm -rf /var/opt/SUNWsamfs/catalog /var/opt/SUNWsamfs/stager

6. Create the /var/opt/SUNWsamfs/catalog and /var/opt/SUNWsamfs/stager symbolic links to the HAStoragePlus mount point.

   The following example is for an HAStoragePlus file system mounted at /sam_shared.

   # ln -s /sam_shared/catalog /var/opt/SUNWsamfs/catalog
   # ln -s /sam_shared/stager /var/opt/SUNWsamfs/stager

7. Copy the catalog information saved in Step 3 to the new shared catalog.

   # cp -rp /var/tmp/catalog/* /var/opt/SUNWsamfs/catalog

How to Configure SAM-QFS Archiving in an Oracle Solaris Cluster Environment

In this example procedure, two file systems are configured: qfs1 and qfs2.

1. Create an HA-SAM resource group.

   # clresourcegroup create -n scnode-A,scnode-B SAM-HA

2. Create and configure the SUNW.qfs resource.

   # clresource create -g SAM-HA -t SUNW.qfs 
   -x QFSFileSystem=/global/qfs1,/global/qfs2 qfs-res

3. Create and configure a SAM-QFS shared resource.

   # clresource create -g SAM-HA -t SUNW.HAStoragePlus 
   -x FilesystemMountPoints=/sam_shared -x AffinityOn=TRUE sam-hastp

4. Create the HA-SAM resource type.

   # clresourcetype register SUNW.hasam

5. Create and configure the SUNW.hasam resource.

   # clresource create -g SAM-HA -t SUNW.hasam -x QFSName=qfs1,qfs2 
   -x CatalogFileSystem=/sam_shared sam-ha

6. Create dependencies between resources within the resource group.

   # clresource set -p Resource_dependencies=sam-hastp qfs-ha
   # clresource set -p Resource_dependencies=qfs-ha sam-ha

7. Bring the resource group online.

   # clresourcegroup manage SAM-HA
   # clresourcegroup online -eM SAM-HA

   ---

   Note - The Sun QFS file systems must be mounted before bringing the resource group online.

   ---

8. Ensure that the resource group is functional on all configured nodes.

   # clresourcegroup switch -n scnode-B SAM-HA
   # clresourcegroup switch -n scnode-A SAM-HA