<?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 Re: METRO Cluster in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/metro-cluster/m-p/2647186#M711973</link>
    <description>Hi All,&lt;BR /&gt;&lt;BR /&gt;Thanks for the reply. I have posted my question because in our environment we want to implement Metro Cluster without using EMC or XP. I know we have AutoRaid and yes, there will be arbitrary node. I don't have more details but, I have concern that this option will AutoRaid wont work. If it is possible to make it work how it can be achieved?&lt;BR /&gt;Regards,&lt;BR /&gt;Dragana</description>
    <pubDate>Thu, 17 Jan 2002 17:05:26 GMT</pubDate>
    <dc:creator>dragana s-v</dc:creator>
    <dc:date>2002-01-17T17:05:26Z</dc:date>
    <item>
      <title>METRO Cluster</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/metro-cluster/m-p/2647183#M711970</link>
      <description>Does anyone know is software component of METRO Cluster different from regular MC-SG product? I know the addition would be interface for SAN device but rather than that is the MC-SG the same or not?</description>
      <pubDate>Thu, 17 Jan 2002 13:25:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/metro-cluster/m-p/2647183#M711970</guid>
      <dc:creator>dragana s-v</dc:creator>
      <dc:date>2002-01-17T13:25:35Z</dc:date>
    </item>
    <item>
      <title>Re: METRO Cluster</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/metro-cluster/m-p/2647184#M711971</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Overview of MetroCluster/CA  &lt;BR /&gt;&lt;BR /&gt;MetroCluster is a set of scripts that work in an MC/ServiceGuard cluster to automate failover to alternate nodes in the case of disaster in a campus or metropolitan cluster. The MetroCluster/CA template contains the following files, installed in /opt/cmcluster/toolkit/SGCA:&lt;BR /&gt;sgcapkg.cntl&lt;BR /&gt; The MetroCluster/CA control script template. This template must be customized for the specific Disk Array XP Series and HP 9000 host system configuration. Copies of this template must be customized for each separate MC/ServiceGuard package.&lt;BR /&gt; &lt;BR /&gt;Samples&lt;BR /&gt; A directory containing sample convenience shell scripts that must be edited before using. These shell scripts may help to automate some configuration tasks. These scripts are contributed, and not supported. This directory also contains sample Raid Manager configuration files and other examples.&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;Have a look at &lt;A href="http://www.docs.hp.com/hpux/onlinedocs/B7660-90006/B7660-90006.html" target="_blank"&gt;www.docs.hp.com/hpux/onlinedocs/B7660-90006/B7660-90006.html&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Jan 2002 14:56:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/metro-cluster/m-p/2647184#M711971</guid>
      <dc:creator>Uday_S_Ankolekar</dc:creator>
      <dc:date>2002-01-17T14:56:51Z</dc:date>
    </item>
    <item>
      <title>Re: METRO Cluster</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/metro-cluster/m-p/2647185#M711972</link>
      <description>Hi, &lt;BR /&gt;&lt;BR /&gt;The nodes in the metropolitan cluster are not going to be adjustant. So, there are obvious limitations to the connectivity to the Disk systems even through SAN. So, it is not possible to share the same set of disks. To achive this, you need to have two seperate disk frames that are continously sync'ed up through ESCON links. You need to use an additional software component to establish and break/resync the mirrors. XP Raid manager for XP systems or symmetrix CLI for EMC. This will  be part of your control script. You may also want to configure Arbitrator Nodes to maintain the quorum. &lt;BR /&gt;&lt;BR /&gt;I haven't done this yet but am planning to. There is good documentation out there at docs.hp.com.&lt;BR /&gt;&lt;BR /&gt;-Sri&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Jan 2002 15:28:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/metro-cluster/m-p/2647185#M711972</guid>
      <dc:creator>Sridhar Bhaskarla</dc:creator>
      <dc:date>2002-01-17T15:28:52Z</dc:date>
    </item>
    <item>
      <title>Re: METRO Cluster</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/metro-cluster/m-p/2647186#M711973</link>
      <description>Hi All,&lt;BR /&gt;&lt;BR /&gt;Thanks for the reply. I have posted my question because in our environment we want to implement Metro Cluster without using EMC or XP. I know we have AutoRaid and yes, there will be arbitrary node. I don't have more details but, I have concern that this option will AutoRaid wont work. If it is possible to make it work how it can be achieved?&lt;BR /&gt;Regards,&lt;BR /&gt;Dragana</description>
      <pubDate>Thu, 17 Jan 2002 17:05:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/metro-cluster/m-p/2647186#M711973</guid>
      <dc:creator>dragana s-v</dc:creator>
      <dc:date>2002-01-17T17:05:26Z</dc:date>
    </item>
    <item>
      <title>Re: METRO Cluster</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/metro-cluster/m-p/2647187#M711974</link>
      <description>Hi:&lt;BR /&gt;&lt;BR /&gt;I think your only practical alternative is to choose disk arrays that can continuously 'sync-up' behind the scenes like XP's or EMC. While I can at least concieve of a few techniques that might keep other arrays synced I certainly wouldn't bet the company on it. Normally, when you are looking at this sort of solution, money isn't the primary concern; reliability is. It may be that you can change the question to 'can I locate the data centers closer together but still in separate buildings so that more conventional mirroring becomes possible?'. But if the question remains a true MetroCluster, then you are going to be forced to use the high-end arrays.&lt;BR /&gt;&lt;BR /&gt;My 3 cents, Clay</description>
      <pubDate>Thu, 17 Jan 2002 17:38:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/metro-cluster/m-p/2647187#M711974</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2002-01-17T17:38:38Z</dc:date>
    </item>
    <item>
      <title>Re: METRO Cluster</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/metro-cluster/m-p/2647188#M711975</link>
      <description>There's nothing in the Autoraid disks that will support data synchronization over a network so the ability to use MC/SG will not work. This isn't a simple task at all since the concept of MC/SG is an essentially seamless transfer of an application package from one system to another, and for that to work, the same data must exist on both systems. Getting two independent disk arrays to stay in sync is a non-trivial task, especially when the sync process could severely slowdown the active server (waiting for the remote writes to complete).</description>
      <pubDate>Thu, 17 Jan 2002 18:04:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/metro-cluster/m-p/2647188#M711975</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2002-01-17T18:04:48Z</dc:date>
    </item>
    <item>
      <title>Re: METRO Cluster</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/metro-cluster/m-p/2647189#M711976</link>
      <description>Thanks a lot everyone !!!&lt;BR /&gt;&lt;BR /&gt;Dragana</description>
      <pubDate>Thu, 17 Jan 2002 18:40:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/metro-cluster/m-p/2647189#M711976</guid>
      <dc:creator>dragana s-v</dc:creator>
      <dc:date>2002-01-17T18:40:21Z</dc:date>
    </item>
  </channel>
</rss>

