<?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: EVA VDisk Question in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/eva-vdisk-question/m-p/4796912#M49519</link>
    <description>vRAID1 *is* RAID-10 everywhere else. The span is across all the physical disks *in* the selected disk group.&lt;BR /&gt;&lt;BR /&gt;-----&lt;BR /&gt;Don't forget to rate the usefulness/quality of *all* responses to (not just this but *all* of) your question(s).</description>
    <pubDate>Thu, 09 Jun 2011 10:44:48 GMT</pubDate>
    <dc:creator>Sheldon Smith</dc:creator>
    <dc:date>2011-06-09T10:44:48Z</dc:date>
    <item>
      <title>EVA VDisk Question</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva-vdisk-question/m-p/4796907#M49514</link>
      <description>I need to setup storage space on our SAN for a new set of windows servers, requiring approximately 800GB of space for the system drive partitions. &lt;BR /&gt;&lt;BR /&gt;Would it be wise to split this 800GB into multiple groups? For example two 400GB VDISKS, or four 200GB VDISKS?&lt;BR /&gt;&lt;BR /&gt;I am wondering if this could help avoid downtime if a VDISK became "corrupt." However, I am not sure if just one VDISK can become corrupt at a time, or if all the VDISKS on a disk group become corrupted at once. &lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Brett</description>
      <pubDate>Wed, 08 Jun 2011 14:49:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva-vdisk-question/m-p/4796907#M49514</guid>
      <dc:creator>Brett Barton</dc:creator>
      <dc:date>2011-06-08T14:49:59Z</dc:date>
    </item>
    <item>
      <title>Re: EVA VDisk Question</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva-vdisk-question/m-p/4796908#M49515</link>
      <description>I'm not sure I understand what you're asking. You want to have an appropriately-sized VDISK for each server's system drive.</description>
      <pubDate>Thu, 09 Jun 2011 00:06:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva-vdisk-question/m-p/4796908#M49515</guid>
      <dc:creator>Sheldon Smith</dc:creator>
      <dc:date>2011-06-09T00:06:16Z</dc:date>
    </item>
    <item>
      <title>Re: EVA VDisk Question</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva-vdisk-question/m-p/4796909#M49516</link>
      <description>Never experienced a vdisk getting corrupt so may as well have one big disk? &lt;BR /&gt;&lt;BR /&gt;However, your question suggests multiple servers accessing this disk? If that's the case it's probably wiser to provide a vdisk to each and size accordingly as suggested above. Be easier to manage.</description>
      <pubDate>Thu, 09 Jun 2011 07:11:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva-vdisk-question/m-p/4796909#M49516</guid>
      <dc:creator>cjb_1</dc:creator>
      <dc:date>2011-06-09T07:11:09Z</dc:date>
    </item>
    <item>
      <title>Re: EVA VDisk Question</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva-vdisk-question/m-p/4796910#M49517</link>
      <description>Best practices don't recommend it. Use RAID 10 if you are worried about your data.</description>
      <pubDate>Thu, 09 Jun 2011 09:15:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva-vdisk-question/m-p/4796910#M49517</guid>
      <dc:creator>Azadeh</dc:creator>
      <dc:date>2011-06-09T09:15:33Z</dc:date>
    </item>
    <item>
      <title>Re: EVA VDisk Question</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva-vdisk-question/m-p/4796911#M49518</link>
      <description>No raid-10 on an eva.. The data protection is pretty good though, you'ld need multiple disk failures in specific rss's before you got worried.</description>
      <pubDate>Thu, 09 Jun 2011 09:33:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva-vdisk-question/m-p/4796911#M49518</guid>
      <dc:creator>cjb_1</dc:creator>
      <dc:date>2011-06-09T09:33:44Z</dc:date>
    </item>
    <item>
      <title>Re: EVA VDisk Question</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva-vdisk-question/m-p/4796912#M49519</link>
      <description>vRAID1 *is* RAID-10 everywhere else. The span is across all the physical disks *in* the selected disk group.&lt;BR /&gt;&lt;BR /&gt;-----&lt;BR /&gt;Don't forget to rate the usefulness/quality of *all* responses to (not just this but *all* of) your question(s).</description>
      <pubDate>Thu, 09 Jun 2011 10:44:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva-vdisk-question/m-p/4796912#M49519</guid>
      <dc:creator>Sheldon Smith</dc:creator>
      <dc:date>2011-06-09T10:44:48Z</dc:date>
    </item>
    <item>
      <title>Re: EVA VDisk Question</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva-vdisk-question/m-p/4796913#M49520</link>
      <description>Always recommended to create a single vdisk for the single server.&lt;BR /&gt;&lt;BR /&gt;If you have multiple server, yes it is good to have multiple vdisks for each server.&lt;BR /&gt;&lt;BR /&gt;Again at the same time, in cluster environment you can present the same LUN to different servers as a shared storage.&lt;BR /&gt;&lt;BR /&gt;Never think about the data corruption.&lt;BR /&gt;&lt;BR /&gt;When the Vdisk presented to the server, after that need to create physical volume, logical volume and then file system. So if data corruption happened that should be in the file system level.&lt;BR /&gt;&lt;BR /&gt;EVA virtualization came to reduce these circumstances.&lt;BR /&gt;&lt;BR /&gt;Even entire disk enclosure failure also can't make the EVA down. That's y RSS concept is great here.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 09 Jun 2011 15:20:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva-vdisk-question/m-p/4796913#M49520</guid>
      <dc:creator>SUBHAJIT KHANBARMAN_1</dc:creator>
      <dc:date>2011-06-09T15:20:23Z</dc:date>
    </item>
    <item>
      <title>Re: EVA VDisk Question</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva-vdisk-question/m-p/4796914#M49521</link>
      <description>I forgot one important detail. The LUN is presented to our ESX cluster. From there we create a datastore on the 800GB LUN. &lt;BR /&gt;&lt;BR /&gt;So my question should be should I break the 800GB into multiple VDISKs so that I dont "have all my eggs in one basket." Except, instead of eggs, they are VMWare .vmdk files.&lt;BR /&gt;&lt;BR /&gt;Sorry!</description>
      <pubDate>Fri, 10 Jun 2011 10:44:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva-vdisk-question/m-p/4796914#M49521</guid>
      <dc:creator>Brett Barton</dc:creator>
      <dc:date>2011-06-10T10:44:06Z</dc:date>
    </item>
    <item>
      <title>Re: EVA VDisk Question</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva-vdisk-question/m-p/4796915#M49522</link>
      <description>&lt;P&gt;Yes, that *is* an important detail! &lt;LI-EMOJI id="lia_slightly-smiling-face" title=":slightly_smiling_face:"&gt;&lt;/LI-EMOJI&gt;&lt;BR /&gt;&lt;BR /&gt;See the technical paper &lt;A href="http://h20195.www2.hp.com/v2/getdocument.aspx?docname=4AA1-2185ENW.pdf" target="_blank" rel="noopener"&gt;http://h20195.www2.hp.com/v2/getdocument.aspx?docname=4AA1-2185ENW.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;You may want to search for:&lt;BR /&gt;best practices EVA VMware vSphere&lt;/P&gt;</description>
      <pubDate>Fri, 18 Jun 2021 09:48:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva-vdisk-question/m-p/4796915#M49522</guid>
      <dc:creator>Sheldon Smith</dc:creator>
      <dc:date>2021-06-18T09:48:09Z</dc:date>
    </item>
    <item>
      <title>Re: EVA VDisk Question</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva-vdisk-question/m-p/5293609#M60639</link>
      <description>&lt;P&gt;Can you help me out max vdisk size we can present to single windows host?&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/189380"&gt;@Sheldon Smith&lt;/a&gt; wrote:&lt;BR /&gt;I'm not sure I understand what you're asking. You want to have an appropriately-sized VDISK for each server's system drive.&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 07 Aug 2011 15:15:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva-vdisk-question/m-p/5293609#M60639</guid>
      <dc:creator>users_storage</dc:creator>
      <dc:date>2011-08-07T15:15:10Z</dc:date>
    </item>
    <item>
      <title>Re: EVA VDisk Question</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva-vdisk-question/m-p/5312721#M60726</link>
      <description>Depends on the version of Windows. With Windows 2008, as far as I know you can present any size vdisk. However, the larger a single vdisk is, the longer actions like backup and restore will take.</description>
      <pubDate>Thu, 25 Aug 2011 21:17:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva-vdisk-question/m-p/5312721#M60726</guid>
      <dc:creator>Sheldon Smith</dc:creator>
      <dc:date>2011-08-25T21:17:25Z</dc:date>
    </item>
  </channel>
</rss>

