Symantec logo

Disk groups

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.

Checking whether a configuration database is too full (vxse_dg1)

To check whether the disk group configuration database has become too full, run rule vxse_dg1.

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 156.

Checking disk group configuration copies and logs (vxse_dg2)

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 vxse_dg2.

Checking "on disk config" size (vxse_dg3)

To check whether a disk group has the correct "on disk config" size, run rule vxse_dg3.

Checking the version number of disk groups (vxse_dg4)

To check the version number of a disk group, run rule vxse_dg4.

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 194.

Checking the number of configuration copies in a disk group (vxse_dg5)

To find out whether a disk group has only a single VxVM configured disk, run rule vxse_dg5.

See "Creating and administering disk groups" on page 151.

Checking for non-imported disk groups (vxse_dg6)

To check for disk groups that are visible to VxVM but not imported, run rule vxse_dg6.

See "Importing a disk group" on page 160.

Checking for initialized VM disks that are not in a disk group (vxse_disk)

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 157.

Checking volume redundancy (vxse_redundancy)

To check whether a volume is redundant, run rule vxse_redundancy.

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 257.

Checking states of plexes and volumes (vxse_volplex)

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 216.

See "Starting a volume" on page 256.

See the Veritas Volume Manager Troubleshooting Guide.