Re: migrating a pv to another - concurrent vg

Title: RE: migrating a pv to another - concurrent vg

solution:

(0)root@sbe18950 620# migratelp poms1Data1a/1390 dlmfdrv10
migratelp: Mirror copy 1 of logical partition 1390 of logical volume
        poms1Data1a migrated to physical partition 637 of dlmfdrv10.


_____________________________________________
From:   Van Koll Holger, IT-SDL-SEE-MIE-UAH 
Sent:   Wednesday, January 25, 2006 5:03 PM
To:     'IBM AIX Discussion List'
Subject:        migrating a pv to another - concurrent vg

Hello,

I need to migrate hdisk19 to hdisk10. However, they contain the same LV. So, lv xx is "striped" between hdisk19 and hdisk10.

So, migratepv of course does not work.
(0)root@sbe18950 605# migratepv dlmfdrv19 dlmfdrv10
0516-1244 migratepv: Destination physical volume dlmfdrv10 contains
        partitions of the logical volume poms1Data1a.
0516-812 migratepv: Warning, migratepv did not completely succeed;
        all physical partitions have not been moved off the PV.

In these cases I always used lmigratepp. It can be a lot of work as you have to move every single pp, but it always worked.

So I tried it (the variables v/pvi19/pvi10 are set correctly!) and it gave

(0)root@sbe18950 603# lmigratepp -g $v -p $pvi19 -n 257 -P $pvi10 -N 636
0516-090 lmigratepp: This node unable to get configuration lock for this
concurrent volume group.

Its the first time that I have problems with lmigratepp. This is a enhanced concurrent VG. I am not sure if I already used lmigratepp on a e.c. VG.

To me it looks that you cannot use lmigratepp on a e.c. VG.

Are there other ways? I thought about reorgvg, but that gives few control.

If there is no other way, I will add disks, mirror the LV (thats on hdisk10+19) to them, drop the old primary copy and re-mirror on hdisk10.

Regs,

Holger