Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
Operating System - Tru64 Unix
cancel
Showing results for 
Search instead for 
Did you mean: 

Joining disk groups with LSM.

Christof Schoeman
Frequent Advisor

Joining disk groups with LSM.

Hi

My customer wants to know if there is similar functionality in LSM, as the bit extracted from the Veritas Volume Manager V3.5 Administrator's Guide below (sorry about the formatting).

He needs to perform a similar task on systems containing HUGE storage subsystems, and the LSM way of "Moving Disks and Volumes between Disk Groups" would take forever, not to mention the risk of making mistakes.

Any advice you may have how this can be accomplished, shall be greatly appreciated.

-------------------------------------

Joining Disk Groups
-------------------
To remove all VxVM objects from an imported source disk group to an
imported target disk group, use the following command:

# vxdg [-o override|verify] join sourcedg targetdg

Note You cannot specify rootdg as the source disk group for a join
operation.

For example, the following output from vxprint shows the contents of
the disk group rootdg and dg1:

# vxprint
Disk group: rootdg
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg rootdg rootdg - - - - - -
dm disk01 c0t1d0 - 17678493 - - - -
dm disk02 c1t97d0 - 17678493 - - - -
dm disk03 c1t112d0 - 17678493 - - - -
dm disk04 c1t114d0 - 17678493 - - - -
dm disk07 c1t99d0 - 17678493 - - - -
dm disk08 c1t100d0 - 17678493 - - - -

Disk group: dg1
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg dg1 dg1 - - - - - -
dm disk05 c1t96d0 - 17678493 - - - -
dm disk06 c1t98d0 - 17678493 - - - -
v vol1 fsgen ENABLED 2048 - ACTIVE - -
pl vol1-01 vol1 ENABLED 3591 - ACTIVE - -
sd disk01-01 vol1-01 ENABLED 3591 0 - - -
pl vol1-02 vol1 ENABLED 3591 - ACTIVE - -
sd disk05-01 vol1-02 ENABLED 3591 0 - - -

The following command joins disk group dg1 to rootdg:

# vxdg join dg1 rootdg

The moved volumes are initially disabled following the join. 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 join shows that disk group dg1 has
been removed:

# vxprint
Disk group: rootdg
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg rootdg rootdg - - - - - -
dm disk01 c0t1d0 - 17678493 - - - -
dm disk02 c1t97d0 - 17678493 - - - -
dm disk03 c1t112d0 - 17678493 - - - -
dm disk04 c1t114d0 - 17678493 - - - -
dm disk05 c1t96d0 - 17678493 - - - -
dm disk06 c1t98d0 - 17678493 - - - -
dm disk07 c1t99d0 - 17678493 - - - -
dm disk08 c1t100d0 - 17678493 - - - -
v vol1 fsgen ENABLED 2048 - ACTIVE - -
pl vol1-01 vol1 ENABLED 3591 - ACTIVE - -
sd disk01-01 vol1-01 ENABLED 3591 0 - - -
pl vol1-02 vol1 ENABLED 3591 - ACTIVE - -
sd disk05-01 vol1-02 ENABLED 3591 0 - - -
2 REPLIES
Ralf Puchner
Honored Contributor

Re: Joining disk groups with LSM.

##############################################
(22) Move a Disk Group Between Systems
##############################################

o Example is moving an entire diskgroup to another system.
- voldg deport
- voldisk rm rz8 rz17 rz19
o Physically move the disks to the new system
- voldisk define
- voldg import
- volrecover -g -sb

what is so difficult on this procedure?
Scripting is also possible!
Help() { FirstReadManual(urgently); Go_to_it;; }
Alet Barnard
Occasional Advisor

Re: Joining disk groups with LSM.

Thanks for the feedback Ralf

The question was not how to move diskgroups between systems.
We would like to know if there is a simple way to move disks between diskgroups (on the same system) while retaining the underlying objects (volumes, plexes and subdisks).

Thanks again.
Alet