vio server's rootvg disk migratepv

Hi

I need to do the migratepv for the rootvg disks of the vio servers ? The current rootvg disks are on DMX3 storage and the new disks will be given from VMAX. Our setup is dual vio servers with multipathing to the vio clients.

What is the command to do the migratepv for the vio rootvg disks ?

Is it the same like # migratepv (source disk hdisk#) (Destination disk hdisk#) or does vio rootvg disks has a separate command for the data to be migrated?

==========================================================================================================================
$ lspv | grep -i rootvg
hdisk0          00c7518d8e663a3c                    rootvg          active
hdisk2          00c7518d997f5771                    rootvg          active
==========================================================================================================================
$ ioslevel
1.4.1.2-FP-9.2
==========================================================================================================================
$ hostname
viocbs01
==========================================================================================================================
# lsvg -l rootvg
rootvg:
LV NAME             TYPE       LPs   PPs   PVs  LV STATE      MOUNT POINT
hd5                 boot       1     1     1    closed/syncd  N/A
hd6                 paging     8     8     1    open/syncd    N/A
paging00            paging     16    16    1    open/syncd    N/A
hd8                 jfs2log    1     1     1    open/syncd    N/A
hd4                 jfs2       8     8     2    open/syncd    /
hd2                 jfs2       64    64    2    open/syncd    /usr
hd9var              jfs2       32    32    2    open/syncd    /var
hd3                 jfs2       16    16    1    open/syncd    /tmp
hd1                 jfs2       160   160   1    open/syncd    /home
hd10opt             jfs2       32    32    2    open/syncd    /opt
lg_dumplv           sysdump    16    16    1    open/syncd    N/A

==========================================================================================================================
# bootlist -m normal -o
hdisk0 blv=hd5
==========================================================================================================================
# bootinfo -b
hdisk0
==========================================================================================================================

I'm not aware if there is such command but I recommend backups .

Can you assign new disk without removing old ones ?

Hmm funny why do you need 2 disks assigned from SAN storage
when you are not mirroring the data ?
Another problem is that this is not supported version of VIO serer
I strongly advice to upgrade to more supported version

First small checking paste output of commands
1 .go to privileged mode - because you are probably o padmin user
to gain root access run command oem_setup_env
2. Information about disks sizes bootinfo -s hdisk0; bootinfo -s hdisk2
3. volume group information lsvg rootg
4. check whats on disks lspv -l hdisk0; lspv -l hdisk2

After this you will see if you need 2 disks or just one of them

Before you will start any disruptive commends make mksysb image if you do not know how (simtty mksysb)

To move data to new disks

  1. Assign new disks to VIO server
  2. Run Config Manager to discover them in system (cfgmgr)
  3. Extend the volumegroup extendvg rootvg new_disks
  4. Mirror data to new disks (mirrorvg -s -c2 rootvg new_disks_names)
  5. Sync data between mirrors (syncvg -P 32 -v rootvg)
  6. Remove copy from old disks (unmirrorvg -c1 rootvg hdisk0 hdisk2)
  7. Remove old disks from volume group (reducevg rootvg hdisk0 hdisk2)
  8. recreate bootimages bosboot -a
  9. update bootloader bootlist

Easy :slight_smile:

Hi Gito

Thanks for your reply

The below is the output you have asked. As you said this is strange as rootvg is not mirrored :slight_smile:


# lspv -l hdisk0

hdisk0:
LV NAME               LPs   PPs   DISTRIBUTION          MOUNT POINT
lg_dumplv             16    16    00..00..00..00..16    N/A
hd4                   4     4     00..01..03..00..00    /
hd8                   1     1     00..00..01..00..00    N/A
hd9var                9     9     00..00..09..00..00    /var
hd2                   32    32    00..00..22..00..10    /usr
hd1                   160   160   53..29..02..54..22    /home
hd3                   16    16    00..16..00..00..00    /tmp
hd10opt               6     6     00..00..00..00..06    /opt
hd5                   1     1     01..00..00..00..00    N/A
paging00              16    16    00..00..16..00..00    N/A
hd6                   8     8     00..08..00..00..00    N/A

# lspv -l hdisk2

hdisk2:
LV NAME               LPs   PPs   DISTRIBUTION          MOUNT POINT
hd4                   4     4     00..02..00..02..00    /
hd9var                23    23    00..06..17..00..00    /var
hd2                   32    32    00..10..18..04..00    /usr
hd10opt               26    26    00..08..18..00..00    /opt

# lsvg -l rootvg
rootvg:
LV NAME             TYPE       LPs   PPs   PVs  LV STATE      MOUNT POINT
hd5                 boot       1     1     1    closed/syncd  N/A
hd6                 paging     8     8     1    open/syncd    N/A
paging00            paging     16    16    1    open/syncd    N/A
hd8                 jfs2log    1     1     1    open/syncd    N/A
hd4                 jfs2       8     8     2    open/syncd    /
hd2                 jfs2       64    64    2    open/syncd    /usr
hd9var              jfs2       32    32    2    open/syncd    /var
hd3                 jfs2       16    16    1    open/syncd    /tmp
hd1                 jfs2       160   160   1    open/syncd    /home
hd10opt             jfs2       32    32    2    open/syncd    /opt
lg_dumplv           sysdump    16    16    1    open/syncd    N/A

# bootlist -m normal -o
hdisk0 blv=hd5

# lslv -l hd5
hd5:N/A
PV                COPIES        IN BAND       DISTRIBUTION
hdisk0            001:000:000   100%          001:000:000:000:000
#
# bootinfo -b
hdisk0

From you output i can not see if you have 2 disks because they were very small or just someone forgot to do something.

lsvg -p rootvg
lsvg rootvg
bootinfo -s hdisk0
bootinfo -s hdisk2

If you you have those disks (and new ones) from SAN
and from the same storage device there is no reason
to mirror them on hard drive would be enough

Just assign new disk from storage and mirror data from
previous 2 to new one. and later just unmirror them from old drive.

I have wrote you a procedure in mail before.

if you go in to oem_setum_env mode you are just treating Vios like any normal AIX it should not be any problems

migratepv works for rootvg too

but you need to create a bootimage on the new disk

assuming hdisk0 for current rootvg hdisk, hdisk1 for new one:

extendvg rootvg hdisk1
migreatepv hdisk0 hdisk1
bosboot -a -d /dev/hdisk1
bootlist -m normal hdisk1
reducevg rootvg hdisk0