VERITAS Volume Manager 3.5 Administrator's Guide (September 2004)

Chapter 4 156
If the system crashes or a hardware subsystem fails, VxVM attempts to
complete or reverse an incomplete disk group reconfiguration when the
system is restarted or the hardware subsystem is repaired, depending on
how far the reconfiguration had progressed. If one of the disk groups is
no longer available because it has been imported by another host or
because it no longer exists, you must recover the disk group manually as
described in the section “Recovery from Incomplete Disk Group Moves”
in the chapter “Recovery from Hardware Failure” of the VERITAS
Volume Manager Troubleshooting Guide.
The disk group move, split and join feature has the following limitations:
• Disk groups involved in a move, split or join must be version 90 or
greater. See “Upgrading a Disk Group” on page 170 for more
information on disk group versions.
• The reconfiguration must involve an integral number of physical
disks.
• Objects to be moved must not contain open volumes.
• Moved volumes are initially disabled following a disk group 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.