| 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
2. Requirements for Using SAM-QFS With Oracle Solaris Cluster
Requirements for Clustered (Shared) File Systems
Requirements for Failover (Local) File Systems
Example - Verifying Devices and Device Redundancy
Analyzing the Output From the Commands
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)
Storage redundancy is achieved by maintenance of extra disk copies of data using mirroring or RAID-1, or parity across several disks using RAID-5 to enable reconstruction of data after a disk failure. When supported by the hardware, these disk configurations enable you to configure the raw devices in an Oracle Solaris Cluster environment without a volume manager. These raw devices are accessible from multiple nodes, so you can issue the format command from any node to obtain information on the disks.
Storage redundancy can also be achieved by using software to support mirroring or RAID. This method, however, is not generally suitable for concurrent access from multiple hosts. Oracle Solaris Cluster software supports mirroring of disk volumes (RAID-1 only) through its multi-owner diskset feature with Sun QFS software and Solaris Volume Manager. No other software redundancy is supported.
|