<?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: Vdisk expansion in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/vdisk-expansion/m-p/5165547#M57453</link>
    <description>Take a look at Microsoft's KB 304736:&lt;BR /&gt;&lt;A href="http://support.microsoft.com/kb/304736" target="_blank"&gt;http://support.microsoft.com/kb/304736&lt;/A&gt;</description>
    <pubDate>Tue, 24 Mar 2009 14:46:43 GMT</pubDate>
    <dc:creator>Sheldon Smith</dc:creator>
    <dc:date>2009-03-24T14:46:43Z</dc:date>
    <item>
      <title>Vdisk expansion</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/vdisk-expansion/m-p/5165544#M57450</link>
      <description>Hi ,&lt;BR /&gt;I need to expand a vdisk presented to windows cluster server which belongs to a DR group. I have two options.&lt;BR /&gt;&lt;BR /&gt;Option 1.&lt;BR /&gt;&lt;BR /&gt;1. After shutting down the application take a snap clone of the disks.(2 disks 300GB and 75 GB)&lt;BR /&gt;&lt;BR /&gt;2. Expand the vdisk and check in the destination EVA disk size is changed or not?&lt;BR /&gt;&lt;BR /&gt;If it is not changed then delete the member disk from the DR group and add it again.&lt;BR /&gt;&lt;BR /&gt;Option 2.&lt;BR /&gt;&lt;BR /&gt;1. create new vdisk with new size, add to DR group and present it to the server, re configure the cluster.&lt;BR /&gt;&lt;BR /&gt;2 . Copy the data from old disk  to the new disk.&lt;BR /&gt;&lt;BR /&gt;3. Delte the old disk from the DR group&lt;BR /&gt;&lt;BR /&gt;Please help me to choose a better option and steps to  delete a vdisk member which is belongs to a DR group.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Anoop</description>
      <pubDate>Mon, 23 Mar 2009 16:07:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/vdisk-expansion/m-p/5165544#M57450</guid>
      <dc:creator>Anoopkumar</dc:creator>
      <dc:date>2009-03-23T16:07:08Z</dc:date>
    </item>
    <item>
      <title>Re: Vdisk expansion</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/vdisk-expansion/m-p/5165545#M57451</link>
      <description>Hi,&lt;BR /&gt;1. If the OS does not support dynamic LUN expansion, all VDISK I/O should be stopped, the VDISK should be unpresented from all hosts, else directly to the step 2&lt;BR /&gt;&lt;BR /&gt;2. VDISK removal from the DR group to which it belongs, saving the destination copy - backup copy of the data until the process has been completed, (it should be even renamed to prevent naming conflicts)&lt;BR /&gt;3. source VDISK expansion.&lt;BR /&gt;4. VDISK expansion successful finish monitoring.&lt;BR /&gt;5. VDISK readdition into the DR group from which it was removed. This starts a full copy of the now expanded VDISK. (Once the full copy has started, the VDISK is available for use).&lt;BR /&gt;6. If the VDISK was unpresented in step 1, then it should be presented back to the appropriate hosts, goto step 7, else go to the step 7 directly&lt;BR /&gt;7. I/O to the newly expanded VDISK should be resumed. The backup destination copy may be deleted once the full copy completes.&lt;BR /&gt;</description>
      <pubDate>Mon, 23 Mar 2009 16:41:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/vdisk-expansion/m-p/5165545#M57451</guid>
      <dc:creator>IBaltay</dc:creator>
      <dc:date>2009-03-23T16:41:00Z</dc:date>
    </item>
    <item>
      <title>Re: Vdisk expansion</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/vdisk-expansion/m-p/5165546#M57452</link>
      <description>Anoop,&lt;BR /&gt;&lt;BR /&gt;MSCS clustering (W2K+) does support disk expansion.&lt;BR /&gt;&lt;BR /&gt;If you follow MSCS best practice and have a single partition per Vdisk/LUN, then simply expand the vdisk (using CV or SSSU). When the expansion is complete (at source and target within DR group), open a cmd prompt at the active node of the MSCS cluster, use diskpart to select the disk and partition in question, then expand.&lt;BR /&gt;&lt;BR /&gt;You don't even need to rescan the bus on the other nodes, as the quorum db will update the other nodes in short order.&lt;BR /&gt;&lt;BR /&gt;Have fun,&lt;BR /&gt;&lt;BR /&gt;Chris</description>
      <pubDate>Mon, 23 Mar 2009 17:03:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/vdisk-expansion/m-p/5165546#M57452</guid>
      <dc:creator>Chris Young_6</dc:creator>
      <dc:date>2009-03-23T17:03:36Z</dc:date>
    </item>
    <item>
      <title>Re: Vdisk expansion</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/vdisk-expansion/m-p/5165547#M57453</link>
      <description>Take a look at Microsoft's KB 304736:&lt;BR /&gt;&lt;A href="http://support.microsoft.com/kb/304736" target="_blank"&gt;http://support.microsoft.com/kb/304736&lt;/A&gt;</description>
      <pubDate>Tue, 24 Mar 2009 14:46:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/vdisk-expansion/m-p/5165547#M57453</guid>
      <dc:creator>Sheldon Smith</dc:creator>
      <dc:date>2009-03-24T14:46:43Z</dc:date>
    </item>
    <item>
      <title>Re: Vdisk expansion</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/vdisk-expansion/m-p/5165548#M57454</link>
      <description>Thanks</description>
      <pubDate>Wed, 30 Jun 2010 05:37:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/vdisk-expansion/m-p/5165548#M57454</guid>
      <dc:creator>Anoopkumar</dc:creator>
      <dc:date>2010-06-30T05:37:51Z</dc:date>
    </item>
  </channel>
</rss>

