topic Re: Serviceguard cluster storage migration in Operating System - HP-UX

Serviceguard cluster storage migration

vilius_m — Fri, 11 Apr 2025 06:31:31 GMT

Hello,

HP-UX version 11.31(Itanium), Serviceguard version 11.19.

I'm planning to do storage migration on Serviceguard 2 node cluster.
Can I use LVM commands vgextend, pvmove, vgreduce on active cluster node cluster vgs ?
Taken in consideration that cluster vgs are marked for cluster using "vgchange -c y" and activated using "vgchange -a e", another concern is cluster vg configuration on standby node - do I have to do additional config there after vgextend, pvmove, vgreduce on active node ?

Thanks,
Vilius M.

Query: Serviceguard cluster storage migration

support_s — Mon, 07 Apr 2025 03:41:31 GMT

System recommended content:

1. Managing Serviceguard A.11.20

2. Upgrading to HP Serviceguard 11.17 with Cluster Volume Manager/Cluster File Systems, December 2005

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

Re: Serviceguard cluster storage migration

georgek_1 — Tue, 08 Apr 2025 15:11:30 GMT

Hello Vilius,
You could follow the LVM commands to perfom the migration such as vgextend luns from new storage, lvextend or pvmove and vgreduce the luns from OLD storage. There is no need to deactivate or change the activation mode of any of the vg at any point of time , hence it can be performed online .

The steps mentioned above would update the vg configutation including lvmtab with new dsfs but it has to be populated to standby node manually.
You need to
1) make map file of the vg from primary node using the options
# vgexport -p -v -s -m /tmp/vg_name.map vg_name - after all the changes to VG (where you make all the changes)
2)copy the map file to standby node
3) export the current vgs from standby node - which should be okay as long as you have all the pkgs are running on primary node and the vgs are active there .
you may run # bdf / vgdisplay and confirm the same before exporting the vgs .
4) Import the vgs with map file copied from primary node , using # vgimport -v -s -N -m /tmp/vg_name.map /dev/vg_name
-N --> on assumption that you would be using agile dsf