Extend a system with ServiceGuard+EVA storage+HP-UX 11.23

[Velda]

From Forums and books I have set up a sequence for the extention of space HP UX server uses on EVA, and which is under ServiceGuard.
But I still have some uncertain areas, and would love help with them.
--------
A sequence :
* Stop all relevant processes on both servers
* Make room on EVA and present it to both servers under SG
* Do ioscan+insf+ioscan for new disk
* Then do a pvcreate+vgextend for ALL 4 paths to EVA (we have 4 paths to EVA because of switches configuration)
* Then lvextend for all LV-s under our VG for which we want to extend the space, and my first question :
----------
Is lvextend done ONLY for a primary path to EVA disk, or it has to be done for all 4 paths for every LV?
----------
* Than we halt ServiceGuard packages on theire home nods
* Deactivate VG and activate it in a exclusive mode
* Extend the file system with extendfs (we do not have OnLine JFS), and my next question :
-----------
After extending FS, do I have to put VG in a non-exclusive mode?
-----------
* Start packages from Se4rviceGuard on theire home nodes
* Export VG
* Go to the other node do insf+ioscan+vgimport, and a question :
-----------
Is it necessary to stop VG on the second node BEFORE vgimport?
-----------
-----------
Please tell me if I have skipped something...
Best
Velda

[Duncan Edmonstone]

Velda,

>> * Stop all relevant processes on both servers


What are these processes - certainly for the VG and LV extension there's no need to stop anything?

>> Is lvextend done ONLY for a primary path to EVA disk, or it has to be done for all 4 paths for every LV?

Assuming you are mentioning a PV when you run lvextend, then any of the 4 PVs which point to the actual vdisk is fine. You only need to do it once.

>> * Extend the file system with extendfs (we do not have OnLine JFS), and my next question :

I will refrain from commenting on the sense of paying for everything needed for a cluster and then *not* buying OnlineJFS...

>> * Than we halt ServiceGuard packages on theire home nods
>> * Deactivate VG and activate it in a exclusive mode

If you have halted the SG package then the VG should already be deactivated

>> * Extend the file system with extendfs (we do not have OnLine JFS), and my next question :
>> -----------
>> After extending FS, do I have to put VG in a non-exclusive mode?

No. Just deactivate the VG again, so that when you start the package SG can reactivate the VG in exclusive mode.

>> Is it necessary to stop VG on the second node BEFORE vgimport?

No, it won't actually be active anyway (nor would you want it to be if the package is running on the other node)

HTH

Duncan

[Steven E. Protter]

Shalom Velda,

Is lvextend done ONLY for a primary path to EVA disk, or it has to be done for all 4 paths for every LV?

There is actually only 1 LUN, this should only need to be done once per actual logical volume.

After extending FS, do I have to put VG in a non-exclusive mode?
I would do this before extending the FS.

Is it necessary to stop VG on the second node BEFORE vgimport?
I would.

SEP

[Denver Osborn]

It wasn't clear from your post, but is this an active/passive or active/active cluster (ie. mcsg ext for rac)

-denver