<?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: Rename Nimble volume and VMWare datastore in Array Setup and Networking</title>
    <link>https://community.hpe.com/t5/array-setup-and-networking/rename-nimble-volume-and-vmware-datastore/m-p/6984344#M1244</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Dan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I just tried this in a lab running on a FC connected array (vSphere 6). When you rename the volume you will get this message:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="jive-image image-1" src="https://community.hpe.com/legacyfs/online/2609_pastedImage_0.png" style="max-height: 900px; max-width: 1200px;" /&gt;&lt;/P&gt;&lt;P&gt;As per the message it will take the volume offline, rename it, then bring it back online. This process is very quick (split second) and so the VMs/ESX hosts may survive this short timeout. If you want to be extra sure though I'd recommend planning a maintenance window if you can take downtime on the VMs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once the volume is renamed the next replication update will update the downstream volume to the same name.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The renaming of the datastore doesn't cause any downtime.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It worked in my lab, but as above you may want to test first or plan a maintenance window to guarantee no impact.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jason&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 10 Nov 2015 11:42:55 GMT</pubDate>
    <dc:creator>jmonger96</dc:creator>
    <dc:date>2015-11-10T11:42:55Z</dc:date>
    <item>
      <title>Rename Nimble volume and VMWare datastore</title>
      <link>https://community.hpe.com/t5/array-setup-and-networking/rename-nimble-volume-and-vmware-datastore/m-p/6984343#M1243</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We want to re-name several volumes/datastores in our virtual environment.&amp;nbsp; We're using a Fiber Channel Nimble array (not iSCSI) and are running on VMWare v 5.0&lt;/P&gt;&lt;P&gt;Is this as simple as just renaming the volume on the Nimble array, and then renaming the datastore within vCenter?&amp;nbsp; I've read where you can run into issues with iSCSI due to the volume name being imbedded in the datastore path/icn, but was not sure if this applies to Fiber Channel implementations or not.&amp;nbsp; I suspect no, but thought I would double check.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, what impact does the rename have (if any) on replication?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Oct 2015 15:31:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-setup-and-networking/rename-nimble-volume-and-vmware-datastore/m-p/6984343#M1243</guid>
      <dc:creator>Dan_265</dc:creator>
      <dc:date>2015-10-29T15:31:43Z</dc:date>
    </item>
    <item>
      <title>Re: Rename Nimble volume and VMWare datastore</title>
      <link>https://community.hpe.com/t5/array-setup-and-networking/rename-nimble-volume-and-vmware-datastore/m-p/6984344#M1244</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Dan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I just tried this in a lab running on a FC connected array (vSphere 6). When you rename the volume you will get this message:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="jive-image image-1" src="https://community.hpe.com/legacyfs/online/2609_pastedImage_0.png" style="max-height: 900px; max-width: 1200px;" /&gt;&lt;/P&gt;&lt;P&gt;As per the message it will take the volume offline, rename it, then bring it back online. This process is very quick (split second) and so the VMs/ESX hosts may survive this short timeout. If you want to be extra sure though I'd recommend planning a maintenance window if you can take downtime on the VMs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once the volume is renamed the next replication update will update the downstream volume to the same name.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The renaming of the datastore doesn't cause any downtime.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It worked in my lab, but as above you may want to test first or plan a maintenance window to guarantee no impact.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jason&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Nov 2015 11:42:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-setup-and-networking/rename-nimble-volume-and-vmware-datastore/m-p/6984344#M1244</guid>
      <dc:creator>jmonger96</dc:creator>
      <dc:date>2015-11-10T11:42:55Z</dc:date>
    </item>
  </channel>
</rss>

