<?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 Destroy VMFS datastore in VSC 6 in VMware Solutions Discussions</title>
    <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Destroy-VMFS-datastore-in-VSC-6/m-p/108902#M8271</link>
    <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just recently getting to grips with using VSC 6 on our vSphere 6 environment and have a question as previously i have using NetApp OCUM to provision storage. Previously I have never used VSC v4 to provison new storage.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;When you destory datastore uisng VSC, I can see it removes it from vCentre and deletes the LUN however the volume still remains intact with the status as online. Is this expected behaviour? Does the admin have to remove this manually.&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;I noticed when provisioning storage using VSCwith FC LUNs, it doesnt use the initiator group created, instead it created a new initiator group with the naming as 'rcu_generated_alua'. Any reason why it does this and not use the default igroup that an admin would have created?&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;Many Thanks&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 23:29:34 GMT</pubDate>
    <dc:creator>RANJBASSI</dc:creator>
    <dc:date>2025-06-04T23:29:34Z</dc:date>
    <item>
      <title>Destroy VMFS datastore in VSC 6</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Destroy-VMFS-datastore-in-VSC-6/m-p/108902#M8271</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just recently getting to grips with using VSC 6 on our vSphere 6 environment and have a question as previously i have using NetApp OCUM to provision storage. Previously I have never used VSC v4 to provison new storage.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;When you destory datastore uisng VSC, I can see it removes it from vCentre and deletes the LUN however the volume still remains intact with the status as online. Is this expected behaviour? Does the admin have to remove this manually.&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;I noticed when provisioning storage using VSCwith FC LUNs, it doesnt use the initiator group created, instead it created a new initiator group with the naming as 'rcu_generated_alua'. Any reason why it does this and not use the default igroup that an admin would have created?&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;Many Thanks&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 23:29:34 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Destroy-VMFS-datastore-in-VSC-6/m-p/108902#M8271</guid>
      <dc:creator>RANJBASSI</dc:creator>
      <dc:date>2025-06-04T23:29:34Z</dc:date>
    </item>
    <item>
      <title>Re: Destroy VMFS datastore in VSC 6</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Destroy-VMFS-datastore-in-VSC-6/m-p/108979#M8273</link>
      <description>&lt;P&gt;Hello!&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;VSC will not delete the volumes by default. &amp;nbsp;There is a configuration you can modify to tell VSC to destroy volumes if the last LUN has been removed. &amp;nbsp;The admin guide for VSC has the steps &lt;A href="https://library.netapp.com/ecmdocs/ECMP12405914/html/GUID-3426FC13-0529-4977-8E1B-EFAE24FE43BF.html" target="_self"&gt;here&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regarding the igroup, it will only create one for each collection of hosts that the LUN is mapped to and it will be destroyed when the last LUN is removed. &amp;nbsp;I don't know for sure, but my guess is that VSC doesn't want to mistakenly "take over" an igroup that the administrator doesn't want it to...better to be safe than sorry.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;V/r,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Andrew&lt;/P&gt;</description>
      <pubDate>Sat, 22 Aug 2015 00:10:04 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Destroy-VMFS-datastore-in-VSC-6/m-p/108979#M8273</guid>
      <dc:creator>asulliva</dc:creator>
      <dc:date>2015-08-22T00:10:04Z</dc:date>
    </item>
    <item>
      <title>Re: Destroy VMFS datastore in VSC 6</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Destroy-VMFS-datastore-in-VSC-6/m-p/109042#M8278</link>
      <description>&lt;P&gt;Thanks Andrew for your reply.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I made the change as you mentioned&amp;nbsp;and can confirm you have answered my first question, making that change does indeed destory the volume as well. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However I found it doesnt delete the initiator group. You said you&amp;nbsp;wasn't sure but just for reference&amp;nbsp;I still have to delete this manually after the volume automatically been deleted via VSC destory datastore command...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Aug 2015 11:45:40 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Destroy-VMFS-datastore-in-VSC-6/m-p/109042#M8278</guid>
      <dc:creator>RANJBASSI</dc:creator>
      <dc:date>2015-08-25T11:45:40Z</dc:date>
    </item>
    <item>
      <title>Re: Destroy VMFS datastore in VSC 6</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Destroy-VMFS-datastore-in-VSC-6/m-p/109681#M8294</link>
      <description>&lt;P&gt;Is is possbile to define which initiator group to use instead of the default 'rcu_generated_alua' one the VSC creates?&amp;nbsp; I'd like to use the existing one I have already that has all my hosts/targets defined already.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Sep 2015 19:46:10 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Destroy-VMFS-datastore-in-VSC-6/m-p/109681#M8294</guid>
      <dc:creator>cfizz34</dc:creator>
      <dc:date>2015-09-10T19:46:10Z</dc:date>
    </item>
    <item>
      <title>Re: Destroy VMFS datastore in VSC 6</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Destroy-VMFS-datastore-in-VSC-6/m-p/113102#M8391</link>
      <description>&lt;P&gt;I completely agree, I dont like it creating an automatically generated one, would rather it chose one of my own defined igroup to prevent any confusion but not sure if this is possible.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I hear differently I make sure I update this post.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Nov 2015 10:52:03 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Destroy-VMFS-datastore-in-VSC-6/m-p/113102#M8391</guid>
      <dc:creator>RANJBASSI</dc:creator>
      <dc:date>2015-11-30T10:52:03Z</dc:date>
    </item>
  </channel>
</rss>

