Cluster Lock - Service Guard

[Vasikaran Venkatesan]

I need to move the cluster Lock VG / PV from one storage to another. Since i am planning to use a data VG for the cluster lock VG, how do i go about it. This is a new data VG.
steps i am thinking of:
Edit the ascii.file for new LOCK VG/PV info.;
check ; vgchange -a y ; apply.
Since i am doing -a y on the VG, and have the details of VOLUME GROUP in the tail of the ascii file, will it be enough to make the VG cluster aware ?. Is there anything that i am missing ?.

Thanks,

Vasikaran

[Tim D Fulford]

Yes

You ned to re-apply the service-guard binaries
cmapplyconf -v -C /etc/cmcluster/ -p /etc/cmcluster// ....

This process will write the relavent information into the lock disk.

Regards

Tim

[Vasikaran Venkatesan]

ofcourse i am doing the cmapply.
But my question is, since i do "vgchange -a n"
on the VG, will it be still cluster aware after the cmapply ?.

Since this LockVG is a data VG also, this will be enabled all the time when the package is up, not like the normal VGLOCK, whose main purpose is to handle only Lock mechanism and stay deactivated.

[Srinivas Thokala_1]

You need to edit cluster ascii file at two places, FIRST_CLUSTER_LOCK_VG /dev/vgname
and at the end for VOLUME_GROUP /dev/vgname

If you have a spare disk, create a seperate VG as /dev/vglock rather than naming data VG as
cluster lock disk, edit cluster ascii file as above and recompile cluster binary file with cmapplyconf.

Srini

[Sridhar Bhaskarla]

Hi Vasikaran,

Halt the cluster.

Leave it activated with "vgchange -a y". cmapplyconf will take care of making it cluster aware. But make sure it is activated on the node from which you are applying the configuration.

-Sri

[Massimo Bianchi]

Hi,
a little addition to Shridar (i hope to wrote it well).

You must activate the vg with

vgchange -a e

since it's already marked as cluster aware.

After the cmapply, close it
vgchange -a n

and start newly the cluster.


HTH,
Massimo

[Bernhard Mueller]

Most important you should be aware that for this change you must stop the entire cluster with all its packages(cmhaltcl).

A vgchange -a n does not change the "cluster aware" status of a vg.

Regards,
Bernhard

[Tim D Fulford]

Im sorry my reply offended you.

Here is a manual

http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B5158-90044/B5158-90044_top.html&con=/hpux/onlinedocs/B5158-90044/00/00/48-con.html&toc=/hpux/onlinedocs/B5158-90044/00/00/48-toc.html&searchterms=cmapplyconf&queryid=20030718-031139

Tim

[Enrico P.]

Hi,

#cmhaltcl

#cp -p /etc/cmcluster/.ascii /etc/cmcluster/.ascii.old

modify the .ascii file

#vgchange -c n /dev/NEW_VG_LOCK (if it is a old vg already in cluster)

#vgchange -a y /dev/NEW_VG_LOCK (if it is a new vg)

#cmcheckconf -v -C /etc/cmcluster/.ascii

#cmapplyconf -v -C /etc/cmcluster/.ascii

#cmruncl

Enrico

[Vasikaran Venkatesan]

Thanks to all of you for the excellent information.