Veritas Volume Manager 5.1 SP1 Administrator"s Guide (5900-1506, April 2011)

Warning: Before moving volumes between disk groups, stop all applications that
are accessing the volumes, and unmount all file systems that are configured on
these volumes.
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.
See the Veritas Volume Manager Troubleshooting Guide.
Limitations of disk group split and join
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.
See “Upgrading the disk group version” on page 264.
■ 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.
See “Setting the automatic recovery of volumes” on page 224.
■ 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.
Creating and administering disk groups
Reorganizing the contents of disk groups
254