topic Re: mirror rootvg for migration purposes in Operating System - HP-UX

mirror rootvg for migration purposes

Geert Swillens — Fri, 12 May 2006 09:22:36 GMT

Hello experts,

I want to mirror my rootvg to a set of provided disks, and split of the mirror after reboot/verification for migration purposes...

I found the procedure to setup a mirror of the rootvg in "when good disks go bad" but I could not find this procedure for multiple volumes in the rootvg, nor the procedure change boot path and split off mirror after reboot on the newly added disks.

Can anyone provide me a full procedure on how to do this?

here's display of vg00
ec5ahn06:/root# vgdisplay -v vg00
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 20
Open LV 20
Max PV 16
Cur PV 3
Act PV 3
Max PE per PV 5000
VGDA 6
PE Size (Mbytes) 16
Total PE 3208
Alloc PE 2973
Free PE 235
Total PVG 1
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg00/lvol1
LV Status available/syncd
LV Size (Mbytes) 512
Current LE 32
Allocated PE 32
Used PV 1

LV Name /dev/vg00/lvol2
LV Status available/syncd
LV Size (Mbytes) 4096
Current LE 256
Allocated PE 256
Used PV 1

LV Name /dev/vg00/lvol3
LV Status available/syncd
LV Size (Mbytes) 512
Current LE 32
Allocated PE 32
Used PV 1

LV Name /dev/vg00/lvol4
LV Status available/syncd
LV Size (Mbytes) 8192
Current LE 512
Allocated PE 512
Used PV 1

LV Name /dev/vg00/lvol5
LV Status available/syncd
LV Size (Mbytes) 256
Current LE 16
Allocated PE 16
Used PV 1

LV Name /dev/vg00/lvol6
LV Status available/syncd
LV Size (Mbytes) 4096
Current LE 256
Allocated PE 256
Used PV 1

LV Name /dev/vg00/lvol8
LV Status available/syncd
LV Size (Mbytes) 256
Current LE 16
Allocated PE 16
Used PV 1

LV Name /dev/vg00/lvol10
LV Status available/syncd
LV Size (Mbytes) 512
Current LE 32
Allocated PE 32
Used PV 1

LV Name /dev/vg00/lvol11
LV Status available/syncd
LV Size (Mbytes) 320
Current LE 20
Allocated PE 20
Used PV 1

LV Name /dev/vg00/lvol12
LV Status available/syncd
LV Size (Mbytes) 4096
Current LE 256
Allocated PE 256
Used PV 1

LV Name /dev/vg00/lvol13
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 64
Allocated PE 64
Used PV 1

LV Name /dev/vg00/lvol14
LV Status available/syncd
LV Size (Mbytes) 2048
Current LE 128
Allocated PE 128
Used PV 1

LV Name /dev/vg00/lvol15
LV Status available/syncd
LV Size (Mbytes) 4096
Current LE 256
Allocated PE 256
Used PV 1

LV Name /dev/vg00/lvol16
LV Status available/syncd
LV Size (Mbytes) 640
Current LE 40
Allocated PE 40
Used PV 2

LV Name /dev/vg00/lvol17
LV Status available/syncd
LV Size (Mbytes) 2048
Current LE 128
Allocated PE 128
Used PV 2

LV Name /dev/vg00/lvol7
LV Status available/syncd
LV Size (Mbytes) 512
Current LE 32
Allocated PE 32
Used PV 1

LV Name /dev/vg00/lvol9
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 64
Allocated PE 64
Used PV 1

LV Name /dev/vg00/lvol18
LV Status available/syncd
LV Size (Mbytes) 8192
Current LE 512
Allocated PE 512
Used PV 1

LV Name /dev/vg00/lvol19
LV Status available/syncd
LV Size (Mbytes) 5008
Current LE 313
Allocated PE 313
Used PV 2

LV Name /dev/vg00/nsr
LV Status available/syncd
LV Size (Mbytes) 128
Current LE 8
Allocated PE 8
Used PV 1

--- Physical volumes ---
PV Name /dev/dsk/c2t15d0s2
PV Name /dev/dsk/c4t15d0s2 Alternate Link
PV Status available
Total PE 1032
Free PE 0
Autoswitch On

PV Name /dev/dsk/c2t14d6
PV Name /dev/dsk/c4t14d6 Alternate Link
PV Status available
Total PE 1088
Free PE 0
Autoswitch On

PV Name /dev/dsk/c2t14d7
PV Name /dev/dsk/c4t14d7 Alternate Link
PV Status available
Total PE 1088
Free PE 235
Autoswitch On

--- Physical volume groups ---
PVG Name DC1
PV Name /dev/dsk/c2t15d0s2
PV Name /dev/dsk/c2t14d6
PV Name /dev/dsk/c2t14d7
PV Name /dev/dsk/c4t14d6
PV Name /dev/dsk/c4t15d0s2
PV Name /dev/dsk/c4t14d7

thanks for any feedback,
regards,
Geert

Re: mirror rootvg for migration purposes

Chan 007 — Fri, 12 May 2006 09:32:42 GMT

Hi,

Just check these 3 links your problem will be solved.

Chan

Re: mirror rootvg for migration purposes

Chan 007 — Fri, 12 May 2006 09:33:58 GMT

Apologies I missed the links...

So mark the prev "0"

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=178310

http://forums1.itrc.hp.com/service/forums/bizsupport/questionanswer.do?threadId=949469

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=992638

Chan

Re: mirror rootvg for migration purposes

Asif Sharif — Fri, 12 May 2006 09:39:20 GMT

Hi,

Please find the attached document.

Regards,
Asif Sharif

Re: mirror rootvg for migration purposes

Torsten. — Fri, 12 May 2006 11:13:03 GMT

PLEASE DO *NOT* USE THE LINKS ABOVE!

The given procedure is for PA-RISC systems, but your post indicates an Integrity (Itanium based) server.

If you use the wrong procedure, you will have a mirror, but the disk is *NOT* bootable.

Use this for Itanium based Integrity systems:

http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000082066576

Good luck!

Re: mirror rootvg for migration purposes

Torsten. — Fri, 12 May 2006 11:59:26 GMT

Your disks are on an array, right?

I would do this:
- create similar LUNs for mirroring
- create a mirror for LVOL1 to 3 like described in the link I posted
- now extend your existing PVG file (/etc/lvmpvg), let's say
to PVG name DC2 (physical volume groups - see man pvg)
- lvextend your remaining LVOLs to the PVG

e.g.

# lvextend -m 1 /dev/vg00/lvol4 DC2

it's very important to mirror LVOL1,2 and 3 in this order first to the specified disk!

Re: mirror rootvg for migration purposes

Geert Swillens — Wed, 17 May 2006 08:54:39 GMT

ok, I just about get the procedure :

only one thing I'm not quite sure of,
first thing is to create system, os and service partitions, based on a partition definition file.

in the examples I find it's :

3 (i suspect the number of partitions)
EFI 500MB (EFI part)
HPUX 100% (S2 part)
HPSP 400MB (service partition)

Can the values of EFI and HPSP change? and Do they need to be the same as the disk I am mirroring?

If yes, how can I read out these values from the current boot disk?

I tried idisk /dev/cxtxdx, but that gave me too much info, without showing the total values of EFI and HPSP.

anyone any ideas?

regards,
Geert

Re: mirror rootvg for migration purposes

Enrico P. — Wed, 17 May 2006 09:10:55 GMT

Hi,

diskinfo /dev/rdsk/cxtxdxs1 (EFI)
diskinfo /dev/rdsk/cxtxdxs2 (hp-ux)
diskinfo /dev/rdsk/cxtxdxs3 (hpsp)

Enrico

Re: mirror rootvg for migration purposes

Enrico P. — Wed, 17 May 2006 09:20:33 GMT

The
EFI 500MB (EFI part)
HPSP 400MB (service partition)
are the default value.
They must be almost the default value.

For previus HPUX 11.22 the 3 line entry should look like this:

2
EFI 100MB
HPUX 100%

For HPUX 11.23 and later the 4 line entry should look like this:

3
EFI 500MB
HPUX 100% or XXXXMB
HPSP 400MB

Enrico

Re: mirror rootvg for migration purposes

Geert Swillens — Wed, 17 May 2006 09:48:01 GMT

thanks enrico,

they were in fact default.

another question :

my vg00 consists of three luns from an array :

/dev/dsk/c3t6d3s2

--- Distribution of physical volume ---
LV Name LE of LV PE for LV
/dev/vg00/lvol1 32 32
/dev/vg00/lvol2 256 256
/dev/vg00/lvol3 32 32
/dev/vg00/lvol5 4 4
/dev/vg00/lvol6 256 256
/dev/vg00/lvol7 32 32
/dev/vg00/lvol8 16 16
/dev/vg00/lvol9 64 64
/dev/vg00/lvol10 32 32
/dev/vg00/lvol11 20 20
/dev/vg00/lvol12 256 256
/dev/vg00/lvol13 64 64
/dev/vg00/lvol14 128 128
/dev/vg00/lvol15 71 71

/dev/dsk/c3t6d4

--- Distribution of physical volume ---
LV Name LE of LV PE for LV
/dev/vg00/lvol5 12 12
/dev/vg00/lvol15 185 185
/dev/vg00/lvol16 32 32
/dev/vg00/lvol17 128 128
/dev/vg00/lvol18 512 512

/dev/dsk/c3t6d5

--- Distribution of physical volume ---
LV Name LE of LV PE for LV
/dev/vg00/lvol4 512 512
/dev/vg00/lvol10 96 96

as you can see, I have LV's that cover multiple disks, lvol5 and lvol15.

how do I go about mirroring these LVOLS? Is it better I present one bigger LUN to mirror onto?

regards,
Geert

Re: mirror rootvg for migration purposes

Enrico_19 — Wed, 17 May 2006 10:00:27 GMT

Yes you can use a single bigger lun for your mirror or you can use a different disk for the filesystem that are more access and aren' t system filesystem for load balancing.

Enrico