MC/Service guard how to update the nodes for the vg changes .

[ramkumar]

Hi
we have implemented 2 node cluster. in our environment the Vg are keep on extending as the database is growing continuously . here at the point i am having few questions kinly help me out.

1.Incase if vgs which are part of a package is extended in an active node whether we have to extend the vg in the stand by node or not.

2. If so how to do it automatically . Is there
any inbuild cluster utility or we have to write
our own script to export and import the map file from one node to other node .

Ramkumar

[Suraj_2]

Hi Ram

1)If VGs are extended, then there is no need of extending the same in adoptive nodes. But you have to import the same.
Before importing , note down the existing minor device no. Then while imporing use the same no..

2)No idea.. ..

Hope this helps

Rgds
Suraj

[bhavin asokan]

hi,

for the first question

Adding or removing a physical volume to/from a cluster volume group.

Perform the Re-Import VG Procedure below from all other cluster nodes. Make sure
that the new physical volume is visible in ioscan and accessible through its device
special files. The command insf â Cdisk may be needed to create that files.

The following steps are needed to perform the re-import of an LVM cluster VG. We assume that a cluster volume group vg01 with minor number 0x010000 needs to be re-imported.

â ¢ Steps for the node that has the VG active:
1. Create a mapfile:
node1# vgexport â v â p â s â m /tmp/vg01.map vg01
Warning messages indicating that the VG is active should be ignored.
2. Copy mapfile to each other node (rcp, ftp, etc.)
node1# rcp /tmp/vg01.map node2:/tmp/vg01.map
...
â ¢ Steps to be performed on each other node:
3. Note VG minor number and permissions/ownership:
node2# ll /dev/vg01
total 12
drwxr-xr-x 2 root root 1024 Apr 16 12:04 ./
dr-xr-xr-x 19 bin bin 5120 Jun 20 06:44 ../
crw-r----- 1 root sys 64 0x010000 Apr 4 13:32 group
brw-r----- 1 root sys 64 0x010001 Apr 4 13:32 lvol1
crw-r----- 1 root sys 64 0x010001 Apr 4 13:32 rlvol1
4. Export the VG:
node2# vgexport vg01
5. Re-create VG directory:
node2# mkdir /dev/vg01
6. Re-create VG group special file, use minor number noted above.
node2# mknod /dev/vg01/group c 64 0x010000
7. Run vgimport using the copied mapfile:
node2# vgimport â v â s â m /tmp/vg01.map vg01
Messages indicating that no backup for this VG may exist

[bhavin asokan]

hi,
the above display is not proper.procedure attached.

regds

[G. Vrijhoeven · Accepted solution]

H Ramkumar,

1. When you extend an existing lvol there is no need to replicate it to other nodes. If you add a new lvol you need to replicate it.

2. I do not know how your server config looks like. We created a script that automates it, but that only works if you have an XP1024.
What we did was.
Get a list of all nodes that belong to cluster ( cmviewcl)
Get a list of all mount points that belong to cluster ( bdf | grep vgname | awk '{ print $NF}')
Get the ldevs that belong to the volumegroup
(xpinfo)
log in on all other nodes and do a vgexport && recreate devicefiles ( xpinfo ) && vgimport && mkdir && chown

HTH,

Gideon