Disks groups are the basis of VxVM storage configuration so it is critical that the integrity and resilience of your disk groups are maintained. Storage Expert provides a number of rules that enable you to check the status of disk groups and associated objects.
To check whether the disk group configuration database has become too full, run rule
By default, this rule suggests a limit of 250 for the number of disks in a disk group. If one of your disk groups exceeds this figure, you should consider creating a new disk group. The number of objects that can be configured in a disk group is limited by the size of the private region which stores configuration information about every object in the disk group. Each disk in the disk group that has a private region stores a separate copy of this configuration database.
See "Creating a disk group" on page 180.
To check whether a disk group has too many or too few disk group configuration copies, and whether a disk group has too many or too few copies of the disk group log, run rule
To check whether a disk group has the correct "on disk config" size, run rule
To check the version number of a disk group, run rule
For optimum results, your disk groups should have the latest version number that is supported by the installed version of VxVM.
See "Upgrading a disk group" on page 218.
To find out whether a disk group has only a single VxVM configured disk, run rule
See "Creating and administering disk groups" on page 175.
To check for disk groups that are visible to VxVM but not imported, run rule
See "Importing a disk group" on page 184.
To find out whether there are any initialized disks that are not a part of any disk group, run rule
vxse_disk. This prints out a list of disks, indicating whether they are part of a disk group or unassociated.
See "Adding a disk to a disk group" on page 181.
To check whether a volume is redundant, run rule
This rule displays a list of volumes together with the number of mirrors that are associated with each volume. If
vxse_redundancy shows that a volume does not have an associated mirror, your data is at risk in the event of a disk failure, and you should rectify the situation by creating a mirror for the volume.
See "Adding a mirror to a volume" on page 281.
To check whether your disk groups contain unused objects (such as plexes and volumes), run rule
vxse_volplex. In particular, this rule notifies you if any of the following conditions exist:
See "Reattaching plexes" on page 240.
See "Starting a volume" on page 280.
See the Veritas Volume Manager Troubleshooting Guide.