Migrate lock disk to another storage EMC.

[Vitorxx]

Hi guys, I have a plan to migrate all my VG's and packages to other storage EMC, but I still have some doubts about the disk lock.

Here the scenario:

2 nodes and 1 package.

HP-UX 11 v1

Service Guard 11.16

Here my procedure, but I am not sure if it is the best away to follow. If you can give your opinions I appreciate that.

1-     halt the cluster

2-      pvcreate /dev/rdsk/cxxtxdx (New disk from new EMC storage).

3-      vgchange -a y /dev/vglock

4-      vgextend /dev/vglock /dev/dsk/cxxtxdx (New disk from new EMC storage).

5-      vgreduce /dev/vglock /dev/dsk/cxxtxdx (Old disk from old EMC storage)

6-      vgchange -a n /dev/vglock

7-      vgexport –p –v –s -m /tmp/vglock.maps /dev/vglock

8-      scp –p /tmp/vglock.maps  node2:/tmp/

9-      on node2, vgexport /dev/vglock

10-    on node2, mknod c 64 0xXX0000 /dev/vglock/group

11-   on node2, vgimport –v –s –m /tmp/vglock.maps /dev/vglock.

12-    cmcheckconf –v –C Cluster.ascii      ---  cmapplyconf –v –C Cluster.ascii  (Update the cluster binary file)

13-    vgchange -a n vglock  (deactivate the lock VG, and start the cluster)

[rariasn]

Hi:

Use of an LVM Lock Disk as the Cluster Lock.

A lock disk may be used for clusters up to and including four nodes in size. The cluster lock disk is a special area on an LVM disk located in a volume group that is shareable by all nodes in the cluster. When a node

obtains the cluster lock, this area is marked so that other nodes will recognize the lock as “taken.”

The lock disk is not dedicated for use as the cluster lock; the disk can be employed as part of a normal volume group with user data on it. The cluster lock volume group and physical volume names are identified in

the cluster configuration file.

http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c02056246/c02056246.pdf

Cluster.Ascii:

FIRST_CLUSTER_LOCK_VG           /dev/vgapp1

NODE_NAME node1
FIRST_CLUSTER_LOCK_PV /dev/dsk/xxxxxxx

NODE_NAME  node2
FIRST_CLUSTER_LOCK_PV /dev/dsk/zzzzzz

Apply new configuration.

rgs,

[pradeep m]

To add to.. 

Make sure you are updating the latest cluster configuration ascii file with the new Lock disk details.

Use the cmgetconf command to get the current cluster configuration from the cluster binary. 

Example:

To generate the cluster configuration file for clusterA, and store the information in clusterA.conf, do the following:

# cmgetconf -c clusterA clusterA.conf

Update the Cluster Lock VG and PV entries in ClusterA.conf and then run cmapplyconf to reapply the cluster binary.