<?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: Problem with Shared storage (SAN) in ESXi Discussions</title>
    <link>https://communities.vmware.com/t5/ESXi-Discussions/Problem-with-Shared-storage-SAN/m-p/2709542#M266001</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;MSCS will not allow you tu have read/write on the same disk. Each node owns the disk at a time, not at the same time. This is the natural behavior. Store a file from the node A, then failover to node B and you should see the file over there.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 24 May 2013 11:57:42 GMT</pubDate>
    <dc:creator>marcelo_soares</dc:creator>
    <dc:date>2013-05-24T11:57:42Z</dc:date>
    <item>
      <title>Problem with Shared storage (SAN)</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Problem-with-Shared-storage-SAN/m-p/2709541#M266000</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a SAN Storage DX440 S2 system, and two ESXi 5 (two physical servers)&lt;/P&gt;&lt;P&gt;I could assign Disk to single virtual server using LUN disk created on SAN&lt;/P&gt;&lt;P&gt;However, I couldn't create a shared storage (using LUN, Raw Devices Mapping) between two or more servers. After add shared storage to two servers (A and B), I checked up and realized that the servers using separated space. I mean I created a file on shared storage through server A then checked it from B but cannot see that file. And when running the test of building Failover Cluster Microsoft it fails on the cluster disk test.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please, could you show me steps to create a Shared Storage (SAN) between servers and also quorum disk on SAN and mapping it to ESXi virtual servers ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 May 2013 08:44:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Problem-with-Shared-storage-SAN/m-p/2709541#M266000</guid>
      <dc:creator>neikel</dc:creator>
      <dc:date>2013-05-24T08:44:50Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with Shared storage (SAN)</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Problem-with-Shared-storage-SAN/m-p/2709542#M266001</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;MSCS will not allow you tu have read/write on the same disk. Each node owns the disk at a time, not at the same time. This is the natural behavior. Store a file from the node A, then failover to node B and you should see the file over there.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 May 2013 11:57:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Problem-with-Shared-storage-SAN/m-p/2709542#M266001</guid>
      <dc:creator>marcelo_soares</dc:creator>
      <dc:date>2013-05-24T11:57:42Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with Shared storage (SAN)</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Problem-with-Shared-storage-SAN/m-p/2709543#M266002</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you are trying to do a MS cluster using VMware the disks presented to windows(vm) need to be raw device mappings to the LUN's on the SAN. ESXi should not be in control of those disks.&lt;/P&gt;&lt;P&gt;Once you have done a RDM to the windows VM you can proceed to setup the cluster in windows like you normally would.&lt;/P&gt;&lt;P&gt;Keep in mind by building a MSCS limits some VMware features due to the use of RDMs. &lt;/P&gt;&lt;P&gt;Marcelo is also correct a Windows cluster will only allow on server to have control of the disks at a time to prevent corruption of the disks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 May 2013 15:17:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Problem-with-Shared-storage-SAN/m-p/2709543#M266002</guid>
      <dc:creator>Cyberfed27</dc:creator>
      <dc:date>2013-05-24T15:17:59Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with Shared storage (SAN)</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Problem-with-Shared-storage-SAN/m-p/2709544#M266003</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN class="j-post-author"&gt;&lt;STRONG&gt;&lt;SPAN class="vm-post-since font-color-meta-light"&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/SPAN&gt;Your answers is very helpful, now I passed the test of failover cluster building.&lt;/P&gt;&lt;P&gt;With your helps I focused on solving an error that made I thought I was failed on shared storage:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;H3&gt;&lt;SPAN&gt;The wrong diskette is in the drive. Insert %2 (Volume Serial Number: %3) into drive %1&lt;/SPAN&gt;&lt;/H3&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;And following some suggestions, I converted the LUN disk from MBR to GPT then everything work fine now. Hope this help somebody else.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Thank you very much &lt;SPAN class="j-post-author"&gt;&lt;STRONG&gt;Marcelo Soares &amp;amp; &lt;/STRONG&gt;&lt;/SPAN&gt;&lt;SPAN class="j-post-author"&gt;&lt;STRONG&gt;Cyberfed27&lt;SPAN class="vm-post-since font-color-meta-light"&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;SPAN class="j-post-author"&gt;&lt;STRONG&gt; &lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 May 2013 14:30:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Problem-with-Shared-storage-SAN/m-p/2709544#M266003</guid>
      <dc:creator>neikel</dc:creator>
      <dc:date>2013-05-28T14:30:49Z</dc:date>
    </item>
  </channel>
</rss>

