moving cluster lock disk using cminitlock

[Peter Scherer]

I have to move the cluster lock disk to a new disk because of reorganisation and I don??t want to stop the whole cluster.
I found some hits that this can be done with the command cminitlock.
From the description I don??t understand:
Does this command change the cluster configuration?
Is it necessary to execute this command an all cluster nodes?

Can somebody answer this questions?

Thanks for help
Peter

[melvyn burnard]

you CANNOT use the unsupported cminitlock command to CHANGE your cluster lock disc.
You will have to change your ascii file, halt the cluster, and re-apply the binary to do this.

[Sanjay_6]

Hi Peter,

Try this link,

http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062922248

Hope this helps.

Regds

[Ashwani Kashyap]

I don't think you can do so that way .
YOu will have to halt the cluster , modufy the cluster ascii file , create and distribute the binary files to all node and then start the cluster.

[Peter Scherer]

Does this mean, cminitlock restores only the cluster lock structure to the disk, but doesn??t change the cluster config to use a different path for the disk?

[RAC_1]

I do not know if use of cminitlock is supported or unsupported way.
We changed it in ascii file reapplied the config, thenrestarted the cluster to check for any errors.

But we used cminitlock command (with preview option )to check if it has been changed.

I would recommand
change in ascii file
do cmcheckconf
if OK do
cmapplyconf

Regards,

[melvyn burnard · Accepted solution]

cminitlock is used to restore trhe cluster lock information to an already existing disc, and NOT to change it. It does nothing to the cluster ascii or binary file, hence you cannot use it to do what you wish to do.

[Carsten Krege]

Yes, Peter, the cminitlock tool only re-initializes the cluster lock structures when they got lost.

This can happen if the cluster lock broke and you don't have a valid vgcfgbackup file that contains the cluster lock information, i.e. no vgcfgbackup has been issued after the last cmapplyconf. If you then try to vgcfgrestore with the old file, the replaced disk won't have the cluster lock structures on it.

There was also a problem ("failed to release volume group" messages in syslog) that caused the cluster lock structures not to be written to disk after a cmapplyconf, sometimes causing that the cluster lock did not work. Also here the cminitlock was useful to reinitialize the data structures (This problem was fixed in

A.11.09 --> PHSS_24850
A.11.12 --> PHSS_24537
A.11.13 --> PHSS_24678 .)

Summarized: In only these two specific cases, cminitlock will be useful. You cannot move the clusterlock to a different disk using this unsupported tool.

Carste

[Duncan Edmonstone]

See my thread here on this subject, which *might* work for you... I haven't had a chance to try it yet.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=260487

HTH

Duncan