JavaScript is required to for searching.
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
search filter icon
search icon

Document Information

Preface

1.  Using SAM-QFS With Oracle Solaris Cluster

2.  Requirements for Using SAM-QFS With Oracle Solaris Cluster

Basic Product Familiarity

Hardware Requirements

Software Requirements

Disk Device Requirements

Requirements for Clustered (Shared) File Systems

Requirements for Failover (Local) File Systems

Disk Device Redundancy

Storage Redundancy

Data Path Redundancy

Performance Considerations

Example - Verifying Devices and Device Redundancy

Determining High Availability

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)

6.  Configuring Clients Outside of the Cluster

Data Path Redundancy

Data path redundancy is achieved with multiple HBAs, which are configured from a single node. If your environment includes multiple HBAs for redundancy, be aware that the Sun QFS file systems require multipathing software like the Oracle Solaris I/O multipathing feature (MPxIO) to enable data path redundancy. For more information, see the Oracle Solaris SAN Configuration and Multipathing Guide, or see the stmsboot(1M) man page.

To determine redundancy, consult the hardware documentation for your disk controllers and disk devices. You need to know whether the disk controller or disk devices that are reported by the cldevice show command are on redundant storage. For information, see the storage controller vendor's documentation set and view the current controller configuration.