<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic cluster lock in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/4775459#M660853</link>
    <description>what is the use of cluster lock disk(can any one please explain in simple terms ) and how to set the cluster lock</description>
    <pubDate>Fri, 08 Apr 2011 16:33:04 GMT</pubDate>
    <dc:creator>newunix</dc:creator>
    <dc:date>2011-04-08T16:33:04Z</dc:date>
    <item>
      <title>cluster lock</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/4775459#M660853</link>
      <description>what is the use of cluster lock disk(can any one please explain in simple terms ) and how to set the cluster lock</description>
      <pubDate>Fri, 08 Apr 2011 16:33:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/4775459#M660853</guid>
      <dc:creator>newunix</dc:creator>
      <dc:date>2011-04-08T16:33:04Z</dc:date>
    </item>
    <item>
      <title>Re: cluster lock</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/4775460#M660854</link>
      <description>cluster lock is a tie-breaking mechanism, mandatory for clusters with size of 3 servers or less, optional for more than 3 servers big clusters.&lt;BR /&gt;&lt;BR /&gt;Its purpose is, let's say, TCP-IP network equipment died, or one server's NIC bummed out. And for simplicity, lets assume you only have 2 nodes in the cluster. &lt;BR /&gt;&lt;BR /&gt;Both servers are up and both think that the other one has died. So, they decide to form a single server cluster. Since both of them see the same storage, if both form that cluster, they may corrupt data.&lt;BR /&gt;&lt;BR /&gt;So, the cluster lock, or as it is widely known as cluster lock disks, come into action as a tie breaker. These disks are devices such that, only one of the cluster members can get a lock on them (hence the name lock). Which ever server locks this disk for its own use, forms the cluster. Other servers, who can not lock it, will say, okay, the cluster is formed somewhere else, so I am going to shut myself down and wait for help and induce a TOC (effectively shutdown -h)&lt;BR /&gt;&lt;BR /&gt;Simple enough ??</description>
      <pubDate>Fri, 08 Apr 2011 17:30:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/4775460#M660854</guid>
      <dc:creator>Mel Burslan</dc:creator>
      <dc:date>2011-04-08T17:30:49Z</dc:date>
    </item>
    <item>
      <title>Re: cluster lock</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/4775461#M660855</link>
      <description>Take a read of this document, it should explain it all&lt;BR /&gt;&lt;A href="http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c02056095/c02056095.pdf" target="_blank"&gt;http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c02056095/c02056095.pdf&lt;/A&gt;</description>
      <pubDate>Sat, 09 Apr 2011 16:56:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/4775461#M660855</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2011-04-09T16:56:51Z</dc:date>
    </item>
  </channel>
</rss>

