Expanding a shared VG

[Paulo A G Fessel]

Hello.

I have two L2000 servers running an active-active cluster configuration. There is one active VG for each machine, and now I need to vgexpand both VG's.

Problem is, given VG1 of Server 1, how to make Server 2 knows about the changes on VG1 and vice-versa? I alredy read a script that Veritas provided, and it is as follows:

Server 1:

* vgchange -a n /dev/vg1
* vgexport -p -m /tmp/mapfile /dev/vg1
* ftp /tmp/mapfile to Server 2

Server 2:

* vgimport -m /tmp/mapfile /dev/vg1 /dev/dsk/
* vgchange -a y /dev/vg1
* vgdisplay -v /dev/vg1
* vgchange -a n /dev/vg1

Is this the script? This seems logical to me, but I'm really insecure about this.

TIA,
Paulo Fessel

[Ian Kidd_1]

I usually use vgexport -pvs -m {mapfile} {vg}

You may also need to vgexport /dev/vg1 on server 2 before you vgimport the mapfile into it. If so, you would also need to recreate /dev/vg1 and the group file before you vgimport.

As for feeling insecure - I get the willies every time I have to do this. I wouldn't script it - at this level of work, I'd rather issue the commands one at a time to double-check everything (analyze messages, errors, etc).

It's not fun, but read the man pages on vgexport and vgchange. Also, for HP's take on what you are doing, look at document UXSGLVKBAN00000002. Some steps may not be necessary, depending on if you're creating new logical volumes.
http://support1.itrc.hp.com/service/cki/search.do?category=c0&mode=id&searchString=UXSGLVKBAN00000002&searchCrit=allwords&docType=EngineerNotes&search.x=71&search.y=15

I'd add a step before HP's step #6 - vgexport the volume group to be replaced to a mapfile first before vgexporting it out (my #1 rule: always have a backout).