<?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: Vax CI in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/vax-ci/m-p/3003782#M242</link>
    <description>The VAX CI can be considered the grand daddy of the SAN, but there are differences. &lt;BR /&gt;&lt;BR /&gt;The VAX CI provides access to storage, but only to members of the cluster, whereas, a SAN can offer access to any member of the network.&lt;BR /&gt;&lt;BR /&gt;Depending on the hardware, SAN throughput may be faster.&lt;BR /&gt;&lt;BR /&gt;Generally, all data in the VAX CI can be shared with all nodes of the cluster. The distributed lock manager handles conflicts and prevents corruption. In a SAN, generally data is not shared and is usually accessed by only one system at a time.&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;Marty</description>
    <pubDate>Fri, 20 Jun 2003 20:01:10 GMT</pubDate>
    <dc:creator>Martin Johnson</dc:creator>
    <dc:date>2003-06-20T20:01:10Z</dc:date>
    <item>
      <title>Vax CI</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vax-ci/m-p/3003781#M241</link>
      <description>It has been years since I've worked on Vaxes and the question was posed to me as followed:&lt;BR /&gt;&lt;BR /&gt;Is the VAX CI considered a SAN (Storage Area Network) as we now it today? If not can you elaborate the differences?</description>
      <pubDate>Fri, 20 Jun 2003 19:04:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vax-ci/m-p/3003781#M241</guid>
      <dc:creator>Phillip Bruce_2</dc:creator>
      <dc:date>2003-06-20T19:04:13Z</dc:date>
    </item>
    <item>
      <title>Re: Vax CI</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vax-ci/m-p/3003782#M242</link>
      <description>The VAX CI can be considered the grand daddy of the SAN, but there are differences. &lt;BR /&gt;&lt;BR /&gt;The VAX CI provides access to storage, but only to members of the cluster, whereas, a SAN can offer access to any member of the network.&lt;BR /&gt;&lt;BR /&gt;Depending on the hardware, SAN throughput may be faster.&lt;BR /&gt;&lt;BR /&gt;Generally, all data in the VAX CI can be shared with all nodes of the cluster. The distributed lock manager handles conflicts and prevents corruption. In a SAN, generally data is not shared and is usually accessed by only one system at a time.&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;Marty</description>
      <pubDate>Fri, 20 Jun 2003 20:01:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vax-ci/m-p/3003782#M242</guid>
      <dc:creator>Martin Johnson</dc:creator>
      <dc:date>2003-06-20T20:01:10Z</dc:date>
    </item>
    <item>
      <title>Re: Vax CI</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vax-ci/m-p/3003783#M243</link>
      <description>Thanks for the comments, I do appreciate that. I have to agree with you after going thru the documents. I'm quite supprise by how much I have forgotten about the Vax Cluster CI.&lt;BR /&gt;&lt;BR /&gt;If memory servers me correctly, The star coupler was nothing but a hughe tranformer interconnect. The HSC controllers I worked with back then were the HSC 70 (I think) and they had 4 RA60's attached along with a mirror in which they called it shadowing back then.&lt;BR /&gt;&lt;BR /&gt;Is there any detail documentation that explains the Fiber Channel protocols to the CI. It seems to me unlike in a true SAN today you have all the  FC layers from 0 to 4. Fiber Channel Interfaces came out much later after I left the Vax world to the Unix side.&lt;BR /&gt;&lt;BR /&gt;In my opinion, DEC should never sold out. The Vax systems were way ahead of it's time. &lt;BR /&gt;&lt;BR /&gt;BTW, did get a notification that anyone replied  to me question. Please be sure to email me at pbbruce@mindspring.com</description>
      <pubDate>Sat, 21 Jun 2003 15:56:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vax-ci/m-p/3003783#M243</guid>
      <dc:creator>Phillip Bruce_2</dc:creator>
      <dc:date>2003-06-21T15:56:23Z</dc:date>
    </item>
    <item>
      <title>Re: Vax CI</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vax-ci/m-p/3003784#M244</link>
      <description>Have you or anyone ever replicated the Data over the WAN with a VAX? If so, would you mind sharing your thoughts on that?</description>
      <pubDate>Sat, 21 Jun 2003 20:55:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vax-ci/m-p/3003784#M244</guid>
      <dc:creator>Phillip Bruce_2</dc:creator>
      <dc:date>2003-06-21T20:55:22Z</dc:date>
    </item>
    <item>
      <title>Re: Vax CI</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vax-ci/m-p/3003785#M245</link>
      <description>Hi, &lt;BR /&gt;&lt;BR /&gt;A CI Cluster or Hardware cluster can server disks to any and all nodes connected to the Star Coupler, no matter they are in a VMS cluster or not. Pretty much like a SAN.&lt;BR /&gt;&lt;BR /&gt;Like a SAN, we can have redundant Path of each of the disks/controllers/Tape drives etc.&lt;BR /&gt;&lt;BR /&gt;Unlike a SAN, disk resource level zoning cannot be implimented on the Star Coupler (like one can do on a SAN Switch/Director)&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Vinit Adya</description>
      <pubDate>Mon, 23 Jun 2003 13:53:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vax-ci/m-p/3003785#M245</guid>
      <dc:creator>Vinit Adya</dc:creator>
      <dc:date>2003-06-23T13:53:53Z</dc:date>
    </item>
    <item>
      <title>Re: Vax CI</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vax-ci/m-p/3003786#M246</link>
      <description>&amp;gt; Have you or anyone ever replicated the Data over the WAN with a VAX? If so, would you mind sharing your thoughts on that? &amp;lt;&lt;BR /&gt;&lt;BR /&gt;There are at least hundreds of sites which have used Host-Based Volume Shadowing to replicate (shadow, mirror) disks between clustered VAX systems at two sites.&lt;BR /&gt;&lt;BR /&gt;Such a VAXcluster setup saved Credit Lyonnais from losing their data during a fire in Paris in 1996.  More recently, Commerzbank survived the 9/11 attacks thanks to a VMS disaster-tolerant cluster based on Alphas (see &lt;A href="http://h71000.www7.hp.com/openvms/brochures/commerzbank/commerzbank.pdf)," target="_blank"&gt;http://h71000.www7.hp.com/openvms/brochures/commerzbank/commerzbank.pdf),&lt;/A&gt; although I know of others who also survived who used VAX systems in their DT clusters.&lt;BR /&gt;&lt;BR /&gt;I managed a disaster-tolerant VAXcluster with sites 130 miles apart at E*Trade a few years back.&lt;BR /&gt;&lt;BR /&gt;See my DECUS presentations on "Using OpenVMS Clusters for Disaster Tolerance" at &lt;A href="http://www2.openvms.org/kparris/" target="_blank"&gt;http://www2.openvms.org/kparris/&lt;/A&gt; and &lt;A href="http://www.geocities.com/keithparris/" target="_blank"&gt;http://www.geocities.com/keithparris/&lt;/A&gt; for more information.</description>
      <pubDate>Wed, 30 Jul 2003 21:40:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vax-ci/m-p/3003786#M246</guid>
      <dc:creator>Keith Parris</dc:creator>
      <dc:date>2003-07-30T21:40:37Z</dc:date>
    </item>
  </channel>
</rss>

