<?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 Changing volume ownership in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Changing-volume-ownership/m-p/11419#M2630</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have an interesting situation, this is not something that I can see happening often, but it would be useful to have, for example, when a business re-organizes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to be able to move a volume from vserver1 to vserver2.&amp;nbsp; It seems to me that this should be a fairly simple thing to do.&amp;nbsp; Right?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) unmount volume from junction path on vserver1.&lt;/P&gt;&lt;P&gt;2) maybe offline the volume?&amp;nbsp; might not be needed.&lt;/P&gt;&lt;P&gt;3) vol modify to change owning vserver&lt;/P&gt;&lt;P&gt;4) mount volume on new junction path on vserver2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't see a way to do this today without using SnapMirror to migrate the data, then remove the old volume.&amp;nbsp; This would be time consuming for large volumes and impractical if the cluster doesn't have the free space.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It seems to me that this should be a simple update in VolDB to move a volume, with a few error checks to make sure the volume name is unique in the destination vserver, and that the volume is unmounted.&amp;nbsp; Export policies, CIFS shares, LUN mapping would be handled within the original owner vserver the sames as if someone deleted the volume.&amp;nbsp; The administrator would have to copy or setup new policies on the destination vserver (new owner), or maybe there can be a way to migrate that information too if requested.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thoughts?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 14 Mar 2013 21:16:47 GMT</pubDate>
    <dc:creator>waynemcc</dc:creator>
    <dc:date>2013-03-14T21:16:47Z</dc:date>
    <item>
      <title>Changing volume ownership</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Changing-volume-ownership/m-p/11419#M2630</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have an interesting situation, this is not something that I can see happening often, but it would be useful to have, for example, when a business re-organizes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to be able to move a volume from vserver1 to vserver2.&amp;nbsp; It seems to me that this should be a fairly simple thing to do.&amp;nbsp; Right?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) unmount volume from junction path on vserver1.&lt;/P&gt;&lt;P&gt;2) maybe offline the volume?&amp;nbsp; might not be needed.&lt;/P&gt;&lt;P&gt;3) vol modify to change owning vserver&lt;/P&gt;&lt;P&gt;4) mount volume on new junction path on vserver2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't see a way to do this today without using SnapMirror to migrate the data, then remove the old volume.&amp;nbsp; This would be time consuming for large volumes and impractical if the cluster doesn't have the free space.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It seems to me that this should be a simple update in VolDB to move a volume, with a few error checks to make sure the volume name is unique in the destination vserver, and that the volume is unmounted.&amp;nbsp; Export policies, CIFS shares, LUN mapping would be handled within the original owner vserver the sames as if someone deleted the volume.&amp;nbsp; The administrator would have to copy or setup new policies on the destination vserver (new owner), or maybe there can be a way to migrate that information too if requested.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thoughts?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Mar 2013 21:16:47 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Changing-volume-ownership/m-p/11419#M2630</guid>
      <dc:creator>waynemcc</dc:creator>
      <dc:date>2013-03-14T21:16:47Z</dc:date>
    </item>
    <item>
      <title>Re: Changing volume ownership</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Changing-volume-ownership/m-p/11423#M2632</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You are correct that the only way to do this is to snapmirror the volume from vserver1 to vserver2.&amp;nbsp; We do not support moving volumes between vservers like the way you describe. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P class="p1"&gt;Doug Moore&lt;/P&gt;&lt;P class="p1"&gt;Professional Services Consultant - CMET&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Mar 2013 21:26:46 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Changing-volume-ownership/m-p/11423#M2632</guid>
      <dc:creator>douglasm</dc:creator>
      <dc:date>2013-03-14T21:26:46Z</dc:date>
    </item>
    <item>
      <title>Re: Changing volume ownership</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Changing-volume-ownership/m-p/11428#M2634</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Any chance of a feature enhancement?&amp;nbsp; It doesn't seem to be a difficult thing to me.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Mar 2013 21:29:09 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Changing-volume-ownership/m-p/11428#M2634</guid>
      <dc:creator>waynemcc</dc:creator>
      <dc:date>2013-03-14T21:29:09Z</dc:date>
    </item>
    <item>
      <title>Re: Changing volume ownership</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Changing-volume-ownership/m-p/11433#M2636</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I will make the suggestion.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P class="p1" style="font-family: Arial, Helvetica, Verdana, sans-serif; color: #454545; background-color: #ffffff;"&gt;Doug Moore&lt;/P&gt;&lt;P class="p1" style="font-family: Arial, Helvetica, Verdana, sans-serif; color: #454545; background-color: #ffffff;"&gt;Professional Services Consultant - CMET&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Mar 2013 21:33:06 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Changing-volume-ownership/m-p/11433#M2636</guid>
      <dc:creator>douglasm</dc:creator>
      <dc:date>2013-03-14T21:33:06Z</dc:date>
    </item>
    <item>
      <title>Re: Changing volume ownership</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Changing-volume-ownership/m-p/11438#M2638</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;vFiler parity across the board to Vservers in a perfect world. in addition to move/reassign volumes, Vserver migrate and Vserver dr. I know these are futures but all on my wish list too. Vserver data motion too. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from my iPhone 5&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Mar 2013 04:00:44 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Changing-volume-ownership/m-p/11438#M2638</guid>
      <dc:creator>scottgelb</dc:creator>
      <dc:date>2013-03-15T04:00:44Z</dc:date>
    </item>
    <item>
      <title>Re: Changing volume ownership</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Changing-volume-ownership/m-p/11443#M2640</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hope this feature will be possible !&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Sep 2013 13:58:01 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Changing-volume-ownership/m-p/11443#M2640</guid>
      <dc:creator>POLICARD</dc:creator>
      <dc:date>2013-09-11T13:58:01Z</dc:date>
    </item>
    <item>
      <title>Re: Changing volume ownership</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Changing-volume-ownership/m-p/113991#M24203</link>
      <description>&lt;P&gt;Doug,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any idea whether Netapp has a solution yet on moving a volume from vserver1 to vserver2 without being snapmirrored?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;--Srinath&lt;/P&gt;</description>
      <pubDate>Mon, 21 Dec 2015 13:40:24 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Changing-volume-ownership/m-p/113991#M24203</guid>
      <dc:creator>SrinathATT</dc:creator>
      <dc:date>2015-12-21T13:40:24Z</dc:date>
    </item>
    <item>
      <title>Re: Changing volume ownership</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Changing-volume-ownership/m-p/114022#M24219</link>
      <description>&lt;P&gt;The feature that you are talking about is called 'Vol Rehost' and is provide with limited capability in 8.3.2 for transitioned volumes.&lt;/P&gt;&lt;P&gt;Here transitioend volumes means, volumes that are transitioned from 7-Mode to cDOT using 7MTT (Copy-Based or Copy-Free transition).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Refer to the below link for more details:&lt;/P&gt;&lt;P&gt;&lt;A href="https://library.netapp.com/ecmdocs/ECMLP2346396/html/GUID-28E0E5F7-D9E7-4628-8EDF-28B9BB6F00D4.html" target="_blank"&gt;https://library.netapp.com/ecmdocs/ECMLP2346396/html/GUID-28E0E5F7-D9E7-4628-8EDF-28B9BB6F00D4.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;About making this feature available for natively created cDOT volumes, I am sure it is in the plan for future releases.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 22 Dec 2015 08:06:22 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Changing-volume-ownership/m-p/114022#M24219</guid>
      <dc:creator>VijayaBhaskarReddy</dc:creator>
      <dc:date>2015-12-22T08:06:22Z</dc:date>
    </item>
    <item>
      <title>Re: Changing volume ownership</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Changing-volume-ownership/m-p/114095#M24245</link>
      <description>&lt;P&gt;Thank you Vijay&lt;/P&gt;</description>
      <pubDate>Thu, 24 Dec 2015 09:19:11 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Changing-volume-ownership/m-p/114095#M24245</guid>
      <dc:creator>SrinathATT</dc:creator>
      <dc:date>2015-12-24T09:19:11Z</dc:date>
    </item>
  </channel>
</rss>

