| 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 |
| 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
Task Map: Working With Oracle Solaris Cluster Software
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)
The following configuration methods are supported for use in the Oracle Solaris Cluster environment:
HA-QFS – A Sun QFS highly available local file system.
In this configuration, the Sun QFS file system is mounted locally (not shared) by a single node in the Oracle Solaris Cluster environment. If the node hosting the file sytem fails, then the Oracle Solaris Cluster software automatically re-mounts the file system on another node within the cluster. The highly available Sun QFS file system uses the SUNW.HAStoragePlus resource type, which is distributed with the Oracle Solaris Cluster product. From the Oracle Solaris Cluster perspective, this use is referred to as a failover file system.
SC-RAC - A shared QFS file system within an Oracle Solaris Cluster environment for use by the Oracle Real Application Cluster (RAC) application.
In this configuration, one of the Oracle Solaris Cluster nodes acts as the metadata server for the file system. If the metadata server fails, the Oracle Solaris Cluster software, in coordination with the RAC application, automatically moves file system operations from the failing metadata server to a different metadata server within the cluster. Because the file system data is already shared and mounted on the failover metadata server, no re-mounting of the file system is required. The shared file system configuration uses the SUNW.qfs resource type, which is distributed with the Sun QFS product. From the Oracle Solaris Cluster perspective, this use is known as a clustered file system.
SC-COTC – A shared QFS file system with failover capability where all clients accessing the data are outside the cluster.
In this configuration, two or more nodes within the Oracle Solaris Cluster handle metadata operations. A single node is the metadata provider, while additional nodes wait in a passive mode as potential metadata servers in case a failover is required.
This is a failover data service configuration, not a scalable data service. For more information, see Chapter 6, Configuring Clients Outside of the Cluster.
HA-SAM – A high availability shared archiving configuration.
In this configuration, the service is made highly available by the Oracle Solaris Cluster software moving the archiving and metadata service from an active server node to a node waiting in a passive mode. HA-SAM depends on the Sun QFS Oracle Solaris Cluster agent, and therefore this configuration must be installed with a shared file system that is mounted and managed by the Sun QFS Oracle Solaris Cluster agent. This is a failover data service configuration, not a scalable data service. For more information, see About HA-SAM.
Note - Although installing the file system in an Oracle Solaris Cluster environment improves reliability and decreases or eliminates unplanned downtime, it does not eliminate planned downtime. To maintain the health of the file system, you might still need to shut down the Sun QFS or SAM-QFS software occasionally to run the samfsck process. You will also need to shut down the software to apply software patches or updates.
|