<?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: Two Disk groups in MSA Storage</title>
    <link>https://community.hpe.com/t5/msa-storage/two-disk-groups/m-p/619475#M1949</link>
    <description>The EVA will care about the quorum disks on its own. Their existence is pretty well hidden and I have never heard that the user as any control over it - well, except for physical moving one.</description>
    <pubDate>Wed, 01 Feb 2006 02:50:01 GMT</pubDate>
    <dc:creator>Uwe Zessin</dc:creator>
    <dc:date>2006-02-01T02:50:01Z</dc:date>
    <item>
      <title>Two Disk groups</title>
      <link>https://community.hpe.com/t5/msa-storage/two-disk-groups/m-p/619472#M1946</link>
      <description>We have an EVA 5000 with two disk groups. The first disk group "Disk_Group1" contains Disks of 72GB size 60 disks) with Vdisks0 and vdisk1 and vdisk5. The other disk group "Disk_Group2" contains 22 of 136GB disks.&lt;BR /&gt;
The level of protection for the first disk group (72GB HD) is two while the level of protection of the second disk group (136GB) is one.&lt;BR /&gt;
&lt;BR /&gt;
I want to replace the 72GB Hardisks with new 136GB disks so I can increase the space I have for the hosts connected with Disk_Group1.&lt;BR /&gt;
&lt;BR /&gt;
The steps I will be doing is to ungroup one 72GB disk at a time, locate that disk, and remove it physically, then insert a 136GB disk physically into the enclosure, then Group it with disk group1. &lt;BR /&gt;
Wait for the leveling process to finish and start the process again.&lt;BR /&gt;
&lt;BR /&gt;
Is there any thing else that I have to do other than the above steps? Is there  a better way to do it?&lt;BR /&gt;
&lt;BR /&gt;
Iyad</description>
      <pubDate>Wed, 01 Feb 2006 01:40:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/two-disk-groups/m-p/619472#M1946</guid>
      <dc:creator>CA1367821</dc:creator>
      <dc:date>2006-02-01T01:40:20Z</dc:date>
    </item>
    <item>
      <title>Re: Two Disk groups</title>
      <link>https://community.hpe.com/t5/msa-storage/two-disk-groups/m-p/619473#M1947</link>
      <description>I would group at least two new disks (in two different enclosures) at a time. After everything has finished, I suggest you check the RSS state of your disk group.</description>
      <pubDate>Wed, 01 Feb 2006 02:24:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/two-disk-groups/m-p/619473#M1947</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2006-02-01T02:24:10Z</dc:date>
    </item>
    <item>
      <title>Re: Two Disk groups</title>
      <link>https://community.hpe.com/t5/msa-storage/two-disk-groups/m-p/619474#M1948</link>
      <description>Am I going to be able to change also the quorum disks in the default Disk group? Is there any other measures to be taken for these Quorum disks?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance for your time.&lt;BR /&gt;&lt;BR /&gt;Iyad</description>
      <pubDate>Wed, 01 Feb 2006 02:45:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/two-disk-groups/m-p/619474#M1948</guid>
      <dc:creator>CA1367821</dc:creator>
      <dc:date>2006-02-01T02:45:50Z</dc:date>
    </item>
    <item>
      <title>Re: Two Disk groups</title>
      <link>https://community.hpe.com/t5/msa-storage/two-disk-groups/m-p/619475#M1949</link>
      <description>The EVA will care about the quorum disks on its own. Their existence is pretty well hidden and I have never heard that the user as any control over it - well, except for physical moving one.</description>
      <pubDate>Wed, 01 Feb 2006 02:50:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/two-disk-groups/m-p/619475#M1949</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2006-02-01T02:50:01Z</dc:date>
    </item>
  </channel>
</rss>

