< Previous  | TOC | Index | Next  >

Moving objects between disk groups

To move a self-contained set of VxVM objects from an imported source disk group to an imported target disk group, use the following command:

# vxdg [-o expand] [-o override|verify] move sourcedg targetdg \

object ...

The -o expand option ensures that the objects that are actually moved include all other disks containing subdisks that are associated with the specified objects or with objects that they contain.

The default behavior of vxdg when moving licensed disks in an EMC array is to perform an EMC disk compatibility check for each disk involved in the move. If the compatibility checks succeed, the move takes place. vxdg then checks again to ensure that the configuration has not changed since it performed the compatibility check. If the configuration has changed, vxdg attempts to perform the entire move again.

The -o override option enables the move to take place without any EMC checking.

The -o verify option returns the access names of the disks that would be moved but does not perform the move.

  Note   The -o override and -o verify options require a valid EMC license.

For example, the following output from vxprint shows the contents of disk groups rootdg and mydg:

# vxprint

Disk group: rootdg

TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0

dg rootdg rootdg - - - - - -

dm rootdg02 c1t97d0s2 - 17678493 - - - -

dm rootdg03 c1t112d0s2 - 17678493 - - - -

dm rootdg04 c1t114d0s2 - 17678493 - - - -

dm rootdg06 c1t98d0s2 - 17678493 - - - -

Disk group: mydg

TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0

dg mydg mydg - - - - - -

dm mydg01 c0t1d0s2 - 17678493 - - - -

dm mydg05 c1t96d0s2 - 17678493 - - - -

dm mydg07 c1t99d0s2 - 17678493 - - - -

dm mydg08 c1t100d0s2 - 17678493 - - - -

v vol1 fsgen ENABLED 2048 - ACTIVE - -

pl vol1-01 vol1 ENABLED 3591 - ACTIVE - -

sd mydg01-01 vol1-01 ENABLED 3591 0 - - -

pl vol1-02 vol1 ENABLED 3591 - ACTIVE - -

sd mydg05-01 vol1-02 ENABLED 3591 0 - - -

The following command moves the self-contained set of objects implied by specifying disk mydg01 from disk group mydg to rootdg:

# vxdg -o expand move mydg rootdg mydg01

The moved volumes are initially disabled following the move. Use the following commands to recover and restart the volumes in the target disk group:

# vxrecover -g targetdg -m [volume ...]

# vxvol -g targetdg startall

The output from vxprint after the move shows that not only mydg01 but also volume vol1 and mydg05 have moved to rootdg, leaving only mydg07 and mydg08 in disk group mydg:

# vxprint

Disk group: rootdg

TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0

dg rootdg rootdg - - - - - -

dm mydg01 c0t1d0s2 - 17678493 - - - -

dm rootdg02 c1t97d0s2 - 17678493 - - - -

dm rootdg03 c1t112d0s2 - 17678493 - - - -

dm rootdg04 c1t114d0s2 - 17678493 - - - -

dm mydg05 c1t96d0s2 - 17678493 - - - -

dm rootdg06 c1t98d0s2 - 17678493 - - - -

v vol1 fsgen ENABLED 2048 - ACTIVE - -

pl vol1-01 vol1 ENABLED 3591 - ACTIVE - -

sd mydg01-01 vol1-01 ENABLED 3591 0 - - -

pl vol1-02 vol1 ENABLED 3591 - ACTIVE - -

sd mydg05-01 vol1-02 ENABLED 3591 0 - - -

Disk group: mydg

TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0

dg mydg mydg - - - - - -

dm mydg07 c1t99d0s2 - 17678493 - - - -

dm mydg08 c1t100d0s2 - 17678493 - - - -

The following commands would also achieve the same result:

# vxdg move mydg rootdg mydg01 mydg05

# vxdg move mydg rootdg vol1

See "Moving objects between shared disk groups" on page 430.