The disk group split and join feature has the following limitations:

• Disk groups involved in a move, split or join must be version 90 or greater.

• The reconfiguration must involve an integral number of physical disks.

• Objects to be moved must not contain open volumes.

• Disks cannot be moved between CDS and non-CDS compatible disk groups.

• By default, VxVM automatically recovers and starts the volumes following a disk group move, split or join. If you have turned off the automatic recovery feature, volumes are disabled after a move, split, or join. Use the vxrecover -m and vxvol startall commands to recover and restart the volumes.

• Data change objects (DCOs) and snap objects that have been dissociated by Persistent FastResync cannot be moved between disk groups.

• Veritas Volume Replicator (VVR) objects cannot be moved between disk groups.

• For a disk group move to succeed, the source disk group must contain at least one disk that can store copies of the configuration database after the move.

• For a disk group split to succeed, both the source and target disk groups must contain at least one disk that can store copies of the configuration database after the split.

• For a disk group move or join to succeed, the configuration database in the target disk group must be able to accommodate information about all the objects in the enlarged disk group.

• Splitting or moving a volume into a different disk group changes the volume's record ID.

• The operation can only be performed on the master node of a cluster if either the source disk group or the target disk group is shared.

• In a cluster environment, disk groups involved in a move or join must both be private or must both be shared.

• If a cache object or volume set that is to be split or moved uses ISP volumes, the storage pool that contains these volumes must also be specified.