topic Re: VG in exclusive mode in Operating System - HP-UX

VG in exclusive mode

Muhammad Bilal Attique — Mon, 05 Nov 2007 05:33:06 GMT

Dears
we started our cluster using cmruncl but it fails to start and showed message node failure. we start the node and start the package it started and start the database and sap application. but it is showing the VGs in exlcusive mode
VG Status available, exclusive
is it harmfull or not and how it will be in normal position

Re: VG in exclusive mode

Anshumali — Mon, 05 Nov 2007 06:08:50 GMT

what your cmviewcl says?

VG status is ideal as per SG. It has to activated by cluster and status is same you mentioned.

Re: VG in exclusive mode

Muhammad Bilal Attique — Mon, 05 Nov 2007 06:27:08 GMT

the cviewcl showed the failure of primary node. but when we give command cmrunnod manually it starts the node and when we give the command cmrunpkg it starts the package but vgs in exclusive mode.

Re: VG in exclusive mode

Anshumali — Mon, 05 Nov 2007 06:29:40 GMT

Thats ok, primary requirement.

Anshu

Re: VG in exclusive mode

Muhammad Bilal Attique — Tue, 06 Nov 2007 05:01:30 GMT

Any one please help on this issue

Re: VG in exclusive mode

Stephen Doud — Thu, 08 Nov 2007 09:03:30 GMT

Volume groups that are controlled by Serviceguard are modified a bit when cmapplyconf is used to create the cluster.
Cmapplyconf touches the LVM disks' VGRA (volume group reserve area - metadata) and installs the cluster ID label and changes the activation mode field from "standard" to "exclusive". This provides a measure of security for the data on the disk, since the disk is shared between servers. You wouldn't want multiple servers to activate the VG at the same time and write to it at the same time, or corruption would occur. To prevent this, the 'exclusive mode' label is fixed in the VGRA. That means that vgdisplay SHOULD show 'active, exclusive' when run on the node where the VG is activated.

Now, the package startup failure has clues. Look in the package control log to see what they are. Also check the syslog.log at the same timestamp - to see if any additional messages related to the package startup failure are there. Report both back to this forum, or open a software case with HP for assistance if this is critical.