Mirroring a VxVM rootdg in integrity platform

[J. Deverel]

My VxVM knowledge is near nil on HP-UX, let alone boot disk being on this kind of volume manager.

I had to do a ignite restore last week, due to a badly corrupted volume and now I am on a single root disk, in disparate need to create a mirror volume with bootable properties.

Here is my ioscan output:

disk 1 0/4/1/0.0.0.0.0 sdisk CLAIMED DEVICE HP DG072A8B54
/dev/dsk/c1t0d0 /dev/rdsk/c1t0d0
/dev/dsk/c1t0d0s2 /dev/rdsk/c1t0d0s2
disk 2 0/4/1/0.0.0.1.0 sdisk CLAIMED DEVICE HP DG072A9BB7
/dev/dsk/c1t1d0 /dev/rdsk/c1t1d0
disk 3 0/4/1/0.0.0.2.0 sdisk CLAIMED DEVICE HP DG072A9BB7
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0 /dev/dsk/c1t2d0s1 /dev/rdsk/c1t2d0s1 /dev/dsk/c1t2d0s2 /dev/rdsk/c1t2d0s2 /dev/dsk/c1t2d0s3 /dev/rdsk/c1t2d0s3
disk 4 0/4/1/0.0.0.3.0 sdisk CLAIMED DEVICE HP DG072A8B54 /dev/dsk/c1t3d0 /dev/rdsk/c1t3d0 /dev/dsk/c1t3d0s1 /dev/rdsk/c1t3d0s1 /dev/dsk/c1t3d0s2 /dev/rdsk/c1t3d0s2 /dev/dsk/c1t3d0s3 /dev/rdsk/c1t3d0s3

here is current setboot output:

# setboot
Primary bootpath : 0/4/1/0.0.0.2.0
HA Alternate bootpath : 0/0/2/0
Alternate bootpath : 0/4/1/0.0.0.2.0


And last but not the least here is the vxprint output:
# vxprint
Disk group: rootdg

TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg rootdg rootdg - - - - - -

dm rootdg01 c1t1d0 - 71682744 - - - -
dm rootdg02 c1t0d0 - 71682744 - - - -
dm rootdg03 c1t2d0 - 71681696 - - - -
dm rootdisk01 c1t3d0s2 - 70762400 - - - -

v optvol fsgen ENABLED 6017112 - ACTIVE - -
pl optvol-01 optvol ENABLED 6017112 - ACTIVE - -
sd rootdisk01-04 optvol-01 ENABLED 6017112 0 - - -

v rootvol root ENABLED 34376360 - ACTIVE - -
pl rootvol-01 rootvol ENABLED 34376360 - ACTIVE - -
sd rootdisk01-03 rootvol-01 ENABLED 34376360 0 - - -

v standvol fsgen ENABLED 307200 - ACTIVE - -
pl standvol-01 standvol ENABLED 307200 - ACTIVE - -
sd rootdisk01-01 standvol-01 ENABLED 307200 0 - - -

v swapvol swap ENABLED 8356864 - ACTIVE - -
pl swapvol-01 swapvol ENABLED 8356864 - ACTIVE - -
sd rootdisk01-02 swapvol-01 ENABLED 8356864 0 - - -

v tmpvol fsgen ENABLED 2097152 - ACTIVE - -
pl tmpvol-01 tmpvol ENABLED 2097152 - ACTIVE - -
sd rootdisk01-05 tmpvol-01 ENABLED 2097152 0 - - -

v usrvol fsgen ENABLED 35840000 - ACTIVE - -
pl usrvol-01 usrvol ENABLED 35840000 - ACTIVE - -
sd rootdg02-01 usrvol-01 ENABLED 35840000 0 - - -

v varvol fsgen ENABLED 9076472 - ACTIVE - -
pl varvol-01 varvol ENABLED 9076472 - ACTIVE - -
sd rootdisk01-06 varvol-01 ENABLED 9076472 0 - - -


Now, if this was an LVM system, I would figure our the second disk and go with

pvcreate -b -f
vgextend
and then lvextend -m 1

but since this is VxVM and Integrity, I don't even know which disk to take as my root mirror. Looking at these outputs above, all I can say is /dev/dsk/c1t2d0 is my primary boot disk (or is it /dev/dsk/c1t2d0s2 ?)

which disk am I going to select as my mirror disk ?
after figuring out the disk
vxdisksetup cXtXdX
vxdiskadd (syntax ??)
then I need to mirror the rootvg contents onto this new drive but how ?

Thank you for all your help.

J.

[Torsten.]

Why using VxVM if you don't know it?

IMHO there are only a few people using VxVM - at least for boot.


You should consult the

Veritasâ ¢ Volume Manager 5.0. 1
Administrator's Guide
HP-UX 11i v3

guide chapter 2 - root disk mirrors from hp.com

[Torsten.]

... from here:

http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?lang=en&cc=us&contentType=SupportManual&prodTypeId=18964&prodSeriesId=4296010&docIndexId=64255

scroll down!

[J. Deverel]

Not my choice to use VxVM. Server was configured a couple of years back. Admin who did it, is no longer around. The reason why he used it was because if you use LVM, you have to pay for OnlineJFS/MirrorUX license, whereas if you use VxVM, OnlineJFS (or compatible functionality) is included in the package. So, in short, this was done in such a way, because if HP draconian licensing. I am not a big fan of VxVM on HPUX at all, let alone creating the root vg on it. But when life gives you lemons, you know, you need to learn how to make lemonade.

[Steven E. Protter]

Shalom,

This may work, though its not working very well for me.

/etc/vx/bin/vxbrk_rootmir -v -g drd_rootdg disk27
VxVM vxbrk_rootmir INFO V-5-2-4023 11:49: Checking specified disk(s) for presence and type
VxVM vxbrk_rootmir INFO V-5-2-4679 11:49: Using new-style DSF names
VxVM vxbrk_rootmir INFO V-5-2-4025 11:49: DA disk27_p2, DM rootmirr is a valid root mirror
VxVM vxbrk_rootmir INFO V-5-2-4052 11:49: Saving configuration data for later restoration
VxVM vxbrk_rootmir ERROR V-5-2-4596 More than 1 plex on DM rootmirr for optvol (optvol-02
varoptvol-02)


SEP

[Torsten.]

As said, the manual has the procedure too.

But if you are allowed to do, there are several ways to convert the root disks to LVM.

[Steven E. Protter]

Shalom,

I was in a hurry and got this from HP support which seems to work.

vxprint -g rootdg | grep ^pl | grep -F "02" | awk '{printf "vxplex -g rootdg -o
rm dis %s\n", $2}' > /tmp/rmplex.sh
vi /tmp/rmplex.sh
sh /tmp/rmplex.sh
vxprint list all
vxdisk -o alldgs list
vxprint -g rootdg
vxdg -g rootdg rmdisk rootmirr
vxprint -g rootdg

rootmirr was the name of my root mirror

Be careful. I'm very new to vxvm but thus far have not clobbered my system.

First thing I did before doing any of this is an ignite make_net_recovery backup.

SEP

[J. Deverel]

Regarding the manual, the link you provided in an earlier post, takes me to a page of VxVM related document links, but on that page I can not find a link to 5.0 reference. Only reference is for v3.1 on hpux 11i.

I am running VxVM v4.1 on HPUX 11.23 over Rx3600 series hardware.

[Torsten.]

At the middle of the page is the

"Veritas File System 4.1 Administrator's Guide (HP-UX 11i v3, February 2007)"

document.

Copy the link will not work, just search it on the page.

[Ismail Azad]

Hi,

I am extremely new to VxVM too!! Here you will see terms like "plex", "volume", and "disk group" . However, the vxrootmir command is one of the biggest advantage if any as you don't have to bother about the L.V's, label file, LVM headers {PVRA,VGSA,MCR etc}, LIF and BDRA in LVM TERMS. One command vxrootmir does all that for you.

1) Identify an available disk {search for â online invalidâ } disk

vxdisk â o alldgs list

2) Overwrite any headers in the first 1GB at the top of the new mirror

dd if=/dev/zero of=/dev/rdsk/cxtxdx bs=1048576 count=1024

3) Configure cxtxdx as the alternate VxVM boot disk {mirroring of the boot disk volumes}

/etc/vx/bin/vxrootmir -v cxtxdx

4)Determine the new boot diskâ s hardware path and add it to the appropriate boot order

ioscan â k /dev/dsk/cxtxdx {so this would be the disk you fired a dd on}

Add that new boot disk hardware path with
setboot â h
setboot â a

To set the alternate path and HAA path if the server is capable of "high availability alternate" path
Populate the HPSP partition if you want!

The boot and VxVM headers are automatically created with vxrootmir and makes your job easier and you don't have to write that 'for' script or continuosly extend the mirrors with lvextend accross all the L.Vs, again in LVM terms

I am pretty sure the efi_ls and setboot commands remain consistent and lvlnboot would be a vxvmboot here, so if you want to check your consistency on NVRAM or boot area or the contents of integrity boot disk structures, you could do that else just boot the mirror!!

Hope this helps. Please don't forget to assign points.

Regards
Ismail Azad