<?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: Simplivity relocation with high storage usage in HPE SimpliVity</title>
    <link>https://community.hpe.com/t5/hpe-simplivity/simplivity-relocation-with-high-storage-usage/m-p/7270196#M5745</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P dir="auto" style="margin: 0;"&gt;Hi BR&lt;BR /&gt;Good day&lt;BR /&gt;The task can be performed without issues, just that i believe you have to make sure the switch configuration is same as what you had on the other site.&lt;BR /&gt;Regards&lt;BR /&gt;NeetSat&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 13 Jul 2026 13:13:12 GMT</pubDate>
    <dc:creator>NeetSat</dc:creator>
    <dc:date>2026-07-13T13:13:12Z</dc:date>
    <item>
      <title>Simplivity relocation with high storage usage</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/simplivity-relocation-with-high-storage-usage/m-p/7270080#M5744</link>
      <description>&lt;P&gt;Hello Everyone&lt;/P&gt;&lt;P&gt;We are planning to relocate our 3 node cluster to different DC. Both DCs are L2 connected, network side is okay and we plan to do live-relocation. Shutdown one node, move it to other DC, wait for cluster to sync changes and then same with others. We plan for about 2 hour downtime per node.&lt;/P&gt;&lt;P&gt;One thing im concerned is cluster on high storage usage (one node 85%, others below 80%). I know in vSAN there is a timer where node can be offline, after it expires vSAN rebuilds missing components which would then significantly increase storage usage. AFAIK theres no such thing in Simplivity and we should be good to go as long the downed node returns back to cluster. Is that true?&lt;/P&gt;&lt;P&gt;BR&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jul 2026 05:34:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/simplivity-relocation-with-high-storage-usage/m-p/7270080#M5744</guid>
      <dc:creator>steez</dc:creator>
      <dc:date>2026-07-16T05:34:03Z</dc:date>
    </item>
    <item>
      <title>Re: Simplivity relocation with high storage usage</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/simplivity-relocation-with-high-storage-usage/m-p/7270196#M5745</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P dir="auto" style="margin: 0;"&gt;Hi BR&lt;BR /&gt;Good day&lt;BR /&gt;The task can be performed without issues, just that i believe you have to make sure the switch configuration is same as what you had on the other site.&lt;BR /&gt;Regards&lt;BR /&gt;NeetSat&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Jul 2026 13:13:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/simplivity-relocation-with-high-storage-usage/m-p/7270196#M5745</guid>
      <dc:creator>NeetSat</dc:creator>
      <dc:date>2026-07-13T13:13:12Z</dc:date>
    </item>
    <item>
      <title>Re: Simplivity relocation with high storage usage</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/simplivity-relocation-with-high-storage-usage/m-p/7270423#M5748</link>
      <description>&lt;P&gt;Thank you&amp;nbsp;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/2125258"&gt;@NeetSat&lt;/a&gt;&amp;nbsp;for your input. Can confirm - relocation can be done without issues. Each server was out for 1-2 hours, then came back online, OVC turned on and resynced VM changes.&lt;/P&gt;</description>
      <pubDate>Mon, 20 Jul 2026 12:29:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/simplivity-relocation-with-high-storage-usage/m-p/7270423#M5748</guid>
      <dc:creator>steez</dc:creator>
      <dc:date>2026-07-20T12:29:31Z</dc:date>
    </item>
  </channel>
</rss>

