A state database replica stores DiskSuite configuration and state information. Before you can use DiskSuite, you must create state database replicas.
At least three state database replicas should be created. The system will stay running with exactly half or more state database replicas available at any one time. The system will panic when less than half the state database replicas are available. The system will not reboot without one more than half the total state database replicas. Instead, it will go into single-user mode for administrative tasks.
Use Table 1-1 to estimate the number of state database replicas required based on the number of hard drives in your system. Adjust it to meet your needs.
Table 1-1 Estimating Number of State Database Replicas Required
In a two-drive configuration, always create two state database replicas on each drive. For example, assume you create two state database replicas on one slice and only one state database replica on the other. If the slice with two state database replicas fails, DiskSuite will not function because the remaining slice only has one state database replica. Refer to Solstice DiskSuite 4.2.1 Reference Guide for more information on the operation of state database replicas.
You can create state database replicas on either a dedicated slice, or on a slice that will be used as part of a simple metadevice, RAID5 metadevice, or trans metadevice. Refer to Solstice DiskSuite 4.2.1 Reference Guide for guidelines on planning the location of state database replicas.
The maximum number of state database replicas is 50. This also applies to replicas that are part of a diskset.