Consider the following general guidelines when you configure your disks with volume manager software:
Software RAID – Oracle Solaris Cluster software does not support software RAID 5.
Mirrored multihost disks – You must mirror all multihost disks across disk expansion units. See Guidelines for Mirroring Multihost Disks for guidelines on mirroring multihost disks. You do not need to use software mirroring if the storage device provides hardware RAID as well as redundant paths to devices.
Mirrored root – Mirroring the ZFS root pool ensures high availability, but such mirroring is not required. See Mirroring Guidelines for guidelines to help determine whether to mirror the ZFS root pool.
Node lists – To ensure high availability of a device group, make its node lists of potential masters and its failback policy identical to any associated resource group. Or, if a scalable resource group uses more nodes than its associated device group, make the scalable resource group's node list a superset of the device group's node list. See the resource group planning information in the Oracle Solaris Cluster Data Services Planning and Administration Guide for information about node lists.
Multihost disks – You must connect, or port, all devices that are used to construct a device group to all of the nodes that are configured in the node list for that device group. Solaris Volume Manager software can automatically check for this connection at the time that devices are added to a disk set.
Hot-spare disks – You can use hot-spare disks to increase availability, but hot spare disks are not required.
See your volume manager software documentation for disk layout recommendations and any additional restrictions.