topic Re: HPUX vgexport vgimport new device files in Operating System - HP-UX

HPUX vgexport vgimport new device files

scoooot — Wed, 12 Nov 2008 15:51:29 GMT

Currently I have....
- Brocade directors
- EVA4400
- rx4640 (2 node SG cluster)

I need to move the EVA connections to different ports in the same switch. I've moved the hosts already and device files remain the same. I need to move the EVA now and I'm sure, the device files will change.

This is LVM and I'm using PV-links, 4 paths to each disk.
I need to do this live.
I have dual fabrics. A and B
The EVA has 2 connections into each fabric.

Have I left out any information?

What is the best way to do this with ZERO interuption to the business? I've done this before and I know it can be done but my memory is a little challenged here. (-: I appreciate the help please.

Re: HPUX vgexport vgimport new device files

IT_2007 — Wed, 12 Nov 2008 16:49:28 GMT

You need to have map files for those volume groups so that you can re-import them and you may have to add those pv links manually.

Re: HPUX vgexport vgimport new device files

scoooot — Wed, 12 Nov 2008 20:01:43 GMT

Correct me if I'm wrong please but I assume then if I do the following I can do his live:
1) vgexport -m mapfile -s -p -v vgname
2) move EVA Fabric A ports
3) vgimport -m mapfile -v -s vgname
4) vgextend (bring new devices names into vg)
5) rmsf to clean up NOHW devices.

Repeat steps for fabric B.

Its step 3, the import, to a live active vg, I am not sure about.

Re: HPUX vgexport vgimport new device files

Johnson Punniyalingam — Thu, 13 Nov 2008 03:33:14 GMT

>> Correct me if I'm wrong please but I assume then if I do the following I can do his live:
1) vgexport -m mapfile -s -p -v vgname
2) move EVA Fabric A ports
3) vgimport -m mapfile -v -s vgname
4) vgextend (bring new devices names into vg)
5) rmsf to clean up NOHW devices.

Repeat steps for fabric B.

Its step 3, the import, to a live active vg, I am not sure about.

Preview the vgimport to check for any possible error
vgimport -pvs -m /dev/vgxx

if no error remove the preview mode

vgimport -vs -m /dev/vgxx

(nothing wrong in vgimport map file in active vg) becoz mapfile "contain the VGID and lvols)

Thanks,
Johnson

Re: HPUX vgexport vgimport new device files

Matti_Kurkela — Thu, 13 Nov 2008 04:15:27 GMT

One important piece of information was left out: Is this HP-UX 11.31 (11i v3) or older?

If it's a 11.31, the storage management has major differences to the older versions, especially if you are using the newer "Agile View" disk devices.

We have only a few 11.31 machines so far, and we haven't had to do any migrations with them yet. But based on my understanding of the 11.31 documentation, it should be able to handle the move without any change to the (new-style) device files.

The instructions given above seem to refer to HP-UX 11.23 or older. But following them on 11.31 too is not likely to cause any harm.

MK

Re: HPUX vgexport vgimport new device files

Nguyen Anh Tien — Thu, 13 Nov 2008 06:44:40 GMT

OK, this is your working plan
NOTE: you have 04 paths to each disk, right??
1, run vgremove vgname alternate path
--> to remove 02 alternate path (01 HBA)
2, Plug this FC cable to new port
3, run vgextend vgname new_alternate path
4, run #vgchange -t new alternate path
5, #vgreduce vgname 02 old alternate path
6, change the rest FC cable to new port
7, run vgextend to extend 02 alternate path
8, vgexport/vgimport to other node.
HTH

Re: HPUX vgexport vgimport new device files

scoooot — Mon, 17 Nov 2008 15:52:39 GMT

all is well, the migration is complete and not a single interuption. Thank you very much to all the assisted.