HP Serviceguard manual Use of a Lock Disk as the Cluster Lock, Lock Disk Operation

Page 16

Arbitration for Data Integrity in Serviceguard Clusters

Use of a Lock Disk as the Cluster Lock

Use of a Lock Disk as the Cluster Lock

The cluster lock disk (used only in HP-UX clusters) is a disk that can be written to by all members of the cluster. When a node obtains the cluster lock, this disk is marked so that other nodes will recognize the lock as “taken.” This mark will survive an off-on power cycle of the disk device unlike SCSI disk reservations. A lock disk may be used for clusters of up to four nodes.

The lock is created in a special area on a particular LVM physical volume. The cluster lock volume group and physical volume names are identified in the cluster configuration file.

The lock disk is not dedicated for use as the cluster lock; thus, it can be employed as part of a normal volume group with user data on it. The usable space on the disk is not impacted; the lock disk takes no space away from the disk’s volume group. Further, the activation of the volume group on one node does not affect the ability of another node to acquire the cluster lock.

The lock area on the disk is not mirrored, even though the physical volume may be a part of a volume group that contains mirrored logical volumes.

The operation of the lock disk is shown in Figure 5. The node that acquires the lock (in this case node 2) continues running in the cluster. The other node halts.

Figure 5

Lock Disk Operation

16

Image 16
Contents Arbitration For Data Integrity Serviceguard Clusters Manufacturing Part Number B3936-90078 JulyLegal Notices Arbitration for Data Integrity in Serviceguard Clusters Cluster Membership Concepts MembershipCluster Membership Concepts Quorum Split-BrainTie-Breaking No Arbitration-Multiple Paths To Arbitrate or Not to ArbitrateMultiple Heartbeat Failures No Arbitration-Multiple Media Single Node FailureMultiple Paths with Different Media Additional Multiple Paths with Different MediaNo Arbitration-Risks Cluster Startup How Serviceguard Uses ArbitrationStartup and Re-Formation Cluster Quorum and Cluster Locking Dynamic Cluster Re-FormationCluster Lock No Cluster Lock Lock Requirements Use of a Lock Disk as the Cluster Lock Lock Disk OperationSingle Cluster Lock Dual Cluster LockUse of a Lock LUN as the Cluster Lock Oot Irror Lock LUN OperationUse of a Quorum Server as the Cluster Lock Quorum Server OperationSetting up the Quorum Server Running the Quorum ServerSpecifying a Quorum Server Quorum Server Status and StateViewing Quorum Server Status and State Viewing Quorum Server System DataUse of Arbitrator Nodes Use of Arbitrator NodeExtended Distance Clusters Arbitration in Disaster-Tolerant ClustersMetropolitan Clusters Arbitrator Nodes Quorum ServerContinental Clusters Use of Dual Lock Disks in Extended Distance ClustersDisk area is not mirrored Arbitration for Data Integrity in Serviceguard Clusters Summary Arbitration Advantages Disadvantages ModeComparison of Different Arbitration Methods Arbitration for Data Integrity in Serviceguard Clusters Summary
Related manuals
Manual 407 pages 39.81 Kb