LVM and VxVM
cancel
Showing results for 
Search instead for 
Did you mean: 

LVM migration to another san

 
SOLVED
Go to solution
Thomas Kaufmann
Occasional Advisor

LVM migration to another san

Hi Guys,

i´ve been lightyears away now from LVM administration, while once upon a time it was my daily doing.

So, here is the challenge: Migrate Data from "old" FC-based san to new ISCSI-based San.

-Want to do it, while DB and Application is online.

- Since Data was divided in several volume groups (different LUNs on old SAN) i want to migrate the the data into ONE Lun in the new SAN.

I know about vgextend, pvmove and so on, but one challenge is that the VG definitions are too small to hold old and new LUNs.

The other challenge is that some VGs are occopied by the DB as raw device, so a OS-Copy doesn´t work. It have to be done with LVM tools.

Any ideas, to do these challenges?

OS is 11.23

# vgdisplay -v



VG Name                     /dev/vg00inf
VG Write Access             read/write
VG Status                   available
Max LV                      255
Cur LV                      17
Open LV                     17
Max PV                      16
Cur PV                      1
Act PV                      1
Max PE per PV               12799
VGDA                        2
PE Size (Mbytes)            4
Total PE                    12799
Alloc PE                    11925
Free PE                     874
Total PVG                   0
Total Spare PVs             0
Total Spare PVs in use      0

   --- Logical volumes ---
   LV Name                     /dev/vg00inf/lvol01
   LV Status                   available/syncd
   LV Size (Mbytes)            200
   Current LE                  50
   Allocated PE                50
   Used PV                     1

   LV Name                     /dev/vg00inf/lvol02
   LV Status                   available/syncd
   LV Size (Mbytes)            2000
   Current LE                  500
   Allocated PE                500
   Used PV                     1

  ....

   --- Physical volumes ---
   PV Name                     /dev/dsk/c29t0d5
   PV Name                     /dev/dsk/c30t0d5 Alternate Link
   PV Name                     /dev/dsk/c31t0d5 Alternate Link
   PV Name                     /dev/dsk/c32t0d5 Alternate Link
   PV Status                   available
   Total PE                    12799
   Free PE                     874
   Autoswitch                  On
   Proactive Polling           On


VG Name                     /dev/vgeva01
VG Write Access             read/write
VG Status                   available
Max LV                      255
Cur LV                      67
Open LV                     67
Max PV                      16
Cur PV                      2
Act PV                      2
Max PE per PV               28159
VGDA                        4
PE Size (Mbytes)            4
Total PE                    56318
Alloc PE                    47050
Free PE                     9268
Total PVG                   0
Total Spare PVs             0
Total Spare PVs in use      0

   --- Logical volumes ---
   LV Name                     /dev/vgeva01/lvol01
   LV Status                   available/syncd
   LV Size (Mbytes)            200
   Current LE                  50
   Allocated PE                50
   Used PV                     1

   LV Name                     /dev/vgeva01/lvol02
   LV Status                   available/syncd
   LV Size (Mbytes)            2000
   Current LE                  500
   Allocated PE                500
   Used PV                     1

   ...


   --- Physical volumes ---
   PV Name                     /dev/dsk/c29t0d7
   PV Name                     /dev/dsk/c30t0d7 Alternate Link
   PV Name                     /dev/dsk/c31t0d7 Alternate Link
   PV Name                     /dev/dsk/c32t0d7 Alternate Link
   PV Status                   available
   Total PE                    28159
   Free PE                     0
   Autoswitch                  On
   Proactive Polling           On

   PV Name                     /dev/dsk/c33t0d0
   PV Status                   available
   Total PE                    28159
   Free PE                     9268
   Autoswitch                  On
   Proactive Polling           On


VG Name                     /dev/vgnetapp9
VG Write Access             read/write
VG Status                   available
Max LV                      255
Cur LV                      1
Open LV                     1
Max PV                      16
Cur PV                      1
Act PV                      1
Max PE per PV               40961
VGDA                        2
PE Size (Mbytes)            8
Total PE                    20477
Alloc PE                    20000
Free PE                     477
Total PVG                   0
Total Spare PVs             0
Total Spare PVs in use      0

   --- Logical volumes ---
   LV Name                     /dev/vgnetapp9/lvol01
   LV Status                   available/syncd
   LV Size (Mbytes)            160000
   Current LE                  20000
   Allocated PE                20000
   Used PV                     1


   --- Physical volumes ---
   PV Name                     /dev/dsk/c29t1d1
   PV Name                     /dev/dsk/c30t1d1 Alternate Link
   PV Name                     /dev/dsk/c31t1d1 Alternate Link
   PV Name                     /dev/dsk/c32t1d1 Alternate Link
   PV Status                   available
   Total PE                    20477
   Free PE                     477
   Autoswitch                  On
   Proactive Polling           On

 

Tipps and hints are welcome.

Best Regards

Thomas

2 REPLIES 2
Highlighted
PSPrakash
HPE Pro

Re: LVM migration to another san

Hello

1as you are aware , it will be bit difficult to club different LUN/VGs in old SAN into a New Single VG.IWe cannot use LVM-Mirror n such cases.
You may need to migrate offline, (take data-backup and restore to respective mounts in the New-VG.

For more assistance on this , it will be good to log case official support case with HPE.

Regards

PSP

Accept or Kudo

Thomas Kaufmann
Occasional Advisor
Solution

Re: LVM migration to another san

Hi to the guys, which read this tread,

At least i solved it with pvmove and having several LUNs on the new SAN.

In short words

-examine the VG max size of  disk size with vgdisplay -v VGNAME

- create LUNs on the new SAN with max size of VGs disk size

- extend VG with these disks

- move data from old disk LUN to new LUN with pvmove

-after all have been moved, then reduce VG with vgreduce

-after reducing, then remove LVM information from LUN with pvremove

Done

Cu Thomas