Re: Root disk SAN migration (135 Views)
Reply
Regular Advisor
shikhar_1
Posts: 182
Registered: ‎11-18-2010
Message 1 of 4 (289 Views)
Accepted Solution

Root disk SAN migration

Hi All,

 

We have to migrate the HP-UX server 11.31 storage from one SAN to another SAN.

 

I have one confusion as my root disk is also on SAN storage.

So whats the step we need to take for the root disk SAN migration only?

 

Please reply

Honored Contributor
Patrick Wallek
Posts: 13,777
Registered: ‎06-21-2000
Message 2 of 4 (252 Views)

Re: Root disk SAN migration

If you have MirrorDisk installed, then you can mirror your root drive from the current SAN to the new SAN, then reduce the mirror from the current SAN.

 

This can all be done online with no downtime required.

Regular Advisor
shikhar_1
Posts: 182
Registered: ‎11-18-2010
Message 3 of 4 (230 Views)

Re: Root disk SAN migration

Hi Patrick,

 

I am planning to use the below method, like taking the server in LVM maintenance mode then vgexport vg00 and then vgimport and then update Label file and BDRA.

 

1.Take the map file backup of all the vg's including vg00 on server ursdc22

/dev/vg00 <--SAN

Using the below command:
vgexport –p –v -s –m /etc/lvmconf/vg_backup_XX.map vgXX

Keep the note of manjor & minor number

ll /dev/vg*/*

Also find the vgid of root disk

To FInd VGID : xd -An -j8200 -N16 -tx  /dev/rdisk/disk8_p2 | awk '{print $3 $4}'

2. SAN to SAN migration (Storage Team will work for that)

3.After the completion of SAN migration:

Please ask the storage team to provide the new device file for root disk i.e.

/dev/disk/disk8_p2 -- Boot Disk whose lunpath hardware address is

Primary bootpath : 0/0/0/5/0/0/0.0x50060e8004eb2972.0x4000000000000000 (/dev/rdisk/disk8)

And set the path of new primary disk using setboot command:
setboot -p <New lunpath hardware address)

4. boot the server in lvm maintenance mode :


vgexport /dev/vg00
mkdir /dev/vg00
mknod /dev/vg00/group c 64 0x000000
vgimport –v –m -s /etc/lvmconf/vg_backup_00.map vg00
vgchange -a y vg00
vgdisplay -v vg00 | grep -i "PV Name"

Previous Output:

ursdc22:[root::/root]# lvlnboot -v | more
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
        /dev/disk/disk8_p2 -- Boot Disk
Boot: lvol1     on:     /dev/disk/disk8_p2
Root: lvol3     on:     /dev/disk/disk8_p2
Swap: lvol2     on:     /dev/disk/disk8_p2
Dump: lvol2     on:     /dev/disk/disk8_p2, 0

 

To be consistent, Remove the current BDRA definitions and start again in order to ensure that the BDRA and the LABEL file are consistent.

# lvrmboot -r /dev/vg00

Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf

lvlnboot -v /dev/vg00 (No output will come) Like:

lvlnboot: The Boot Data Area is empty.

Boot Definitions for Volume Group /dev/vg00:

The Boot Data Area is empty.

# lvlnboot -b /dev/vg00/lvol1

Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf

# lvlnboot -r /dev/vg00/lvol3

Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf

# lvlnboot -s /dev/vg00/lvol2

Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf

# lvlnboot -d /dev/vg00/lvol2

Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf

#

# lvlnboot -vR /dev/vg00 (To check the BDRA Information)


5. take the server in multiuser mode

reboot

 

Please suggest for the above plan.

Honored Contributor
likid0
Posts: 981
Registered: ‎03-01-2005
Message 4 of 4 (135 Views)

Re: Root disk SAN migration

just to mention, there is no need to do that procedure on 11.31 anymore, with the self healing feature, you just have to map the new lun to the server, locate the new disk in the efi shell and boot.

 

info

 

Boot Disk Configuration Self Healing

With the September 2008 release of HP-UX 11i v3, LVM support
s self healing of boot disk configurations. If the
device special file for a LVM boot disk changes because it
s hardware path changed, LVM scans for the boot disk
during the boot process. After successfully boot
ing, LVM automatically updates the /etc/lvmtab LVM
configuration file and the LVM metadata on each bootable
disk in the root volume group with the new boot
path. Future system boots will not need to scan. This
behavior is configurable, and is enabled by default.

man lvm for more info
Windows?, no thanks
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.