Hi

we have the situation that data on one lpar on many hdisks should be
moved to another physical volumes in an other SAN box (disk
performance). So we think about using the migratepv command to move the
data. Would be the following steps correct ?

1. Attach needed new LUNs to both VIO servers
2. Map these new LUNs from both VIOs to the lpar and add them to the
volumegroup (extendvg ...)
3. Run migratepv command online to move data from old hdisk to new
hdisk (migratepv hdisk<source> hdisk<target>
4. Test if the migrated data are useable in the right manner
5. If all is ok, remove the old hdisks from the volumegroup (reducevg)

Are these steps practicable ?

Thx in advance

Friedhelm

Friedhelm Neyer wrote:
> Hi
>
> we have the situation that data on one lpar on many hdisks should be
> moved to another physical volumes in an other SAN box (disk
> performance). So we think about using the migratepv command to move the
> data. Would be the following steps correct ?
>
> 1. Attach needed new LUNs to both VIO servers
> 2. Map these new LUNs from both VIOs to the lpar and add them to the
> volumegroup (extendvg ...)
> 3. Run migratepv command online to move data from old hdisk to new
> hdisk (migratepv hdisk<source> hdisk<target>
> 4. Test if the migrated data are useable in the right manner
> 5. If all is ok, remove the old hdisks from the volumegroup (reducevg)
>
> Are these steps practicable ?
>
> Thx in advance
>
> Friedhelm

You pretty much got it. "migratepv" is pretty robust in that you won't
get a successful return on your command if something went wrong. I have
never had to test anything, because the file systems never were
unmounted while everything proceeded. If you are moving raw data
volumes, or Oracle data areas, then I would err on the side of caution
and not have them in use at the time, only because I have heard bad
things happening in the past. Somebody may chime in and alleviate these
concerns.

Hope this helps

SG