https://community.hpe.com/t5/operating-system-hp-ux/quorum-server/m-p/5706557#M658296 <P>The actual issue is the <EM>cluster lock</EM>: it can be either a lock disk, a lock LUN or a quorum server.</P><P>&nbsp;</P><UL><LI>A one-node cluster will not use the safety timer mechanism, and therefore won't really need a cluster lock, although with some Serviceguard versions, the configuration tools may insist on it. But if you have only one node, why set up a cluster at all?</LI><LI>A two-node cluster requires a cluster lock, otherwise both nodes will crash and reboot when the cluster heartbeat fails. This would make the cluster rather useless (it would act as a fault-sensitive rather than a fault-tolerant system).</LI><LI>A three-node cluster is strongly recommended to have a cluster lock, in case a failure happens when e.g. one of the nodes is down for scheduled maintenance.</LI><LI>For larger clusters, a cluster lock is recommended but not absolutely required. If you have more than four nodes, you cannot use a lock disk, but you can use a quorum server.</LI></UL><P>A quorum server can be used in clusters of any size. We have successfully used it with several 2-node clusters. Before Serviceguard version A.11.19 it helped in minimizing service breaks during SAN migrations, as the older Serviceguard versions did not allow reconfiguring the cluster lock while the cluster was running.</P> Fri, 29 Jun 2012 19:41:31 GMT Matti_Kurkela 2012-06-29T19:41:31Z https://community.hpe.com/t5/operating-system-hp-ux/quorum-server/m-p/5706307#M658294 <P>Hi I need help.</P><P>&nbsp;</P><P>Quorum server is required with how&nbsp;many&nbsp;nodes ( minimum ) ?</P><P>&nbsp;</P><P>TIA and best regards</P><P>Jose</P> Fri, 29 Jun 2012 14:35:21 GMT https://community.hpe.com/t5/operating-system-hp-ux/quorum-server/m-p/5706307#M658294 Jose_C_Moraes 2012-06-29T14:35:21Z https://community.hpe.com/t5/operating-system-hp-ux/quorum-server/m-p/5706313#M658295 <P>Not sure there is a minimum. I've used it with only 3 node.</P> Fri, 29 Jun 2012 14:39:28 GMT https://community.hpe.com/t5/operating-system-hp-ux/quorum-server/m-p/5706313#M658295 Ken Grabowski 2012-06-29T14:39:28Z https://community.hpe.com/t5/operating-system-hp-ux/quorum-server/m-p/5706557#M658296 <P>The actual issue is the <EM>cluster lock</EM>: it can be either a lock disk, a lock LUN or a quorum server.</P><P>&nbsp;</P><UL><LI>A one-node cluster will not use the safety timer mechanism, and therefore won't really need a cluster lock, although with some Serviceguard versions, the configuration tools may insist on it. But if you have only one node, why set up a cluster at all?</LI><LI>A two-node cluster requires a cluster lock, otherwise both nodes will crash and reboot when the cluster heartbeat fails. This would make the cluster rather useless (it would act as a fault-sensitive rather than a fault-tolerant system).</LI><LI>A three-node cluster is strongly recommended to have a cluster lock, in case a failure happens when e.g. one of the nodes is down for scheduled maintenance.</LI><LI>For larger clusters, a cluster lock is recommended but not absolutely required. If you have more than four nodes, you cannot use a lock disk, but you can use a quorum server.</LI></UL><P>A quorum server can be used in clusters of any size. We have successfully used it with several 2-node clusters. Before Serviceguard version A.11.19 it helped in minimizing service breaks during SAN migrations, as the older Serviceguard versions did not allow reconfiguring the cluster lock while the cluster was running.</P> Fri, 29 Jun 2012 19:41:31 GMT https://community.hpe.com/t5/operating-system-hp-ux/quorum-server/m-p/5706557#M658296 Matti_Kurkela 2012-06-29T19:41:31Z