A disk controller is a device that coordinates and controls the operation of one or more disk drives and synchronizes the operation of the drives with the operation of the system as a whole. These controllers provide the storage that the cluster detects as managed disks (MDisks).
When configuring your disk controllers, ensure that you configure and manage your disk controllers and its devices for optimal performance.
The supported RAID controllers are detected by the cluster and reported by the user interfaces. The cluster can also determine which MDisks each controller has and can provide a view of MDisks filtered by controller. This view enables you to associate the MDisks with the RAID arrays that the controller presents.
| Note: The SAN Volume Controller supports RAID controllers, but it is possible to configure a controller as a non-RAID controller. RAID controllers provide redundancy at the disk level. Therefore, a single physical disk failure does not cause an MDisk failure, an MDisk group failure, or a failure in the virtual disks (VDisks) that were created from the MDisk group. |
The controller may have a local name for the RAID arrays or single disks that it is providing. However it is not possible for the nodes in the cluster to determine this name as the namespace is local to the controller. The controller will surface these disks with a unique ID, the controller LUN or LU number. This ID, along with the controller serial number or numbers (there may be more than one controller), can be used to associate the managed disks in the cluster with the RAID arrays presented by the controllers.
To prevent loss of data, virtualize only those RAID arrays that provide some form of redundancy, that is, RAID 1, RAID 10, RAID 0+1 or RAID 5. Do not use RAID 0 because a single physical disk failure might cause the failure of many VDisks.
When a disk controller system is detected on the SAN, the SAN Volume Controller attempts to recognize it using its Inquiry data. If the disk controller system is recognized as one of the explicitly supported storage models, then the SAN Volume Controller uses error recovery programs that can be tailored to the known needs of the disk controller system. If the storage controller is not recognized, then the SAN Volume Controller configures the disk controller system as a generic controller. A generic controller may or may not function correctly when addressed by a SAN Volume Controller. In any event, the SAN Volume Controller does not regard accessing a generic controller as an error condition and, consequently, does not log an error. MDisks presented by generic controllers are not eligible to be used as quorum disks.