<?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 Repair Storage Node in StoreVirtual Storage</title>
    <link>https://community.hpe.com/t5/storevirtual-storage/repair-storage-node/m-p/4693091#M1576</link>
    <description>Hi guys we are going to be receiving a replacement storage node soon. How do I go about swapping out the entire device and minimize the time it takes to resync the data to the new storage node.&lt;BR /&gt;&lt;BR /&gt;There are currently 4 nodes in this particular cluster.&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
    <pubDate>Wed, 29 Sep 2010 18:50:26 GMT</pubDate>
    <dc:creator>darren cooper</dc:creator>
    <dc:date>2010-09-29T18:50:26Z</dc:date>
    <item>
      <title>Repair Storage Node</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/repair-storage-node/m-p/4693091#M1576</link>
      <description>Hi guys we are going to be receiving a replacement storage node soon. How do I go about swapping out the entire device and minimize the time it takes to resync the data to the new storage node.&lt;BR /&gt;&lt;BR /&gt;There are currently 4 nodes in this particular cluster.&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Wed, 29 Sep 2010 18:50:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/repair-storage-node/m-p/4693091#M1576</guid>
      <dc:creator>darren cooper</dc:creator>
      <dc:date>2010-09-29T18:50:26Z</dc:date>
    </item>
    <item>
      <title>Re: Repair Storage Node</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/repair-storage-node/m-p/4693092#M1577</link>
      <description>Be sure all your volumes are Network RAID 10 or better (2-way replication).&lt;BR /&gt;&lt;BR /&gt;STOP the manager on the node to be replaced&lt;BR /&gt;&lt;BR /&gt;Right click on the node to be replaced: select "Repair Storage Node"&lt;BR /&gt;select "This is a storage node problem"&lt;BR /&gt;&lt;BR /&gt;(This leaves a "ghost" of the old node rather than REMOVING the node, to prevent your cluster from re-striping)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Put the New Storage Node into your rack, cable up etc, power on and give it the IP address and hostname of the old node from the console, configure your network load balancing if required.&lt;BR /&gt;&lt;BR /&gt;In the CMC right click on your cluster and "Edit Cluster" &lt;BR /&gt;Use the "Exchange Node" function.  This should cause only 1 restripe of your data.  If you "remove node" and then add the new one back in you will have 2 seperate re-stripe events.&lt;BR /&gt;&lt;BR /&gt;As always it may behoove you to review these steps with official HP LeftHand support... Good opportunity to make use of those support contracts, and I always find the folks in Boulder quite helpful!</description>
      <pubDate>Thu, 30 Sep 2010 00:41:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/repair-storage-node/m-p/4693092#M1577</guid>
      <dc:creator>teledata</dc:creator>
      <dc:date>2010-09-30T00:41:22Z</dc:date>
    </item>
  </channel>
</rss>

