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

■ 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.
Listing objects potentially affected by a move
To display the VxVM objects that would be moved for a specified list of objects,
use the following command:
# vxdg [-o expand] listmove sourcedg targetdg object ...
The following example lists the objects that would be affected by moving volume
vol1 from disk group mydg to newdg:
# vxdg listmove mydg newdg vol1
mydg01 c0t1d0 mydg05 c1t96d0 vol1 vol1-01 vol1-02 mydg01-01
mydg05-01
However, the following command produces an error because only a part of the
volume vol1 is configured on the disk mydg01:
# vxdg listmove mydg newdg mydg01
VxVM vxdg ERROR V-5-2-4597 vxdg listmove mydg newdg failed
VxVM vxdg ERROR V-5-2-3091 mydg05 : Disk not moving, but
subdisks on it are
Specifying the -o expand option, as shown below, ensures that the list of objects
to be moved includes the other disks (in this case, mydg05) that are configured in
vol1:
# vxdg -o expand listmove mydg newdg mydg01
mydg01 c0t1d0 mydg05 c1t96d0 vol1 vol1-01 vol1-02 mydg01-01 mydg05-01
Moving DCO volumes between disk groups
When you move the parent volume (such as a snapshot volume) to a different disk
group, its DCO volume must accompany it. If you use the vxassist addlog, vxmake
or vxdco commands to set up a DCO for a volume, you must ensure that the disks
that contain the plexes of the DCO volume accompany their parent volume during
255Creating and administering disk groups
Reorganizing the contents of disk groups