<?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: Qtree migration in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Qtree-migration/m-p/15237#M1389</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I doubt it, but just in case, what protocols are you using to access this qtree?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 19 May 2009 12:57:36 GMT</pubDate>
    <dc:creator>adamfox</dc:creator>
    <dc:date>2009-05-19T12:57:36Z</dc:date>
    <item>
      <title>Qtree migration</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Qtree-migration/m-p/15233#M1388</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there a easy way to migrate an existing qtree to a new volume and without disruption?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Terrence&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:27:53 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Qtree-migration/m-p/15233#M1388</guid>
      <dc:creator>tatlee</dc:creator>
      <dc:date>2025-06-05T07:27:53Z</dc:date>
    </item>
    <item>
      <title>Re: Qtree migration</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Qtree-migration/m-p/15237#M1389</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I doubt it, but just in case, what protocols are you using to access this qtree?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 May 2009 12:57:36 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Qtree-migration/m-p/15237#M1389</guid>
      <dc:creator>adamfox</dc:creator>
      <dc:date>2009-05-19T12:57:36Z</dc:date>
    </item>
    <item>
      <title>Re: Qtree migration</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Qtree-migration/m-p/15241#M1390</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you are using snapmirror, I would check out the snapmirror migrate command.&amp;nbsp; I've heard both that qtree migration works live, and also that the qtree's need to be remounted.&lt;/P&gt;&lt;P&gt;filer1&amp;gt; man snapmirror&lt;/P&gt;&lt;P&gt;gives a lot of information about the migrate command.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Philip Arnason&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 May 2009 14:55:23 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Qtree-migration/m-p/15241#M1390</guid>
      <dc:creator>philiparnason</dc:creator>
      <dc:date>2009-05-19T14:55:23Z</dc:date>
    </item>
    <item>
      <title>Re: Qtree migration</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Qtree-migration/m-p/15246#M1391</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok, we're assuming NAS here..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You would have to remount the qtree after the move.&amp;nbsp; By my definition, that's disruptive.&amp;nbsp; The issue is that with qtree snapmirror, the inode #s will change.&amp;nbsp; There is also the issue of the FSID that would cause an issue as well.&amp;nbsp; You can't have the same FSID for 2 volumes on the same controller or within an HA pair.&amp;nbsp; That is also a comonent of the file handle.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 May 2009 15:17:56 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Qtree-migration/m-p/15246#M1391</guid>
      <dc:creator>adamfox</dc:creator>
      <dc:date>2009-05-19T15:17:56Z</dc:date>
    </item>
    <item>
      <title>Re: Qtree migration</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Qtree-migration/m-p/15251#M1392</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Adam. Seems this is the easiest way. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Terrence Lee&lt;/P&gt;&lt;P&gt;NetApp Global Services&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NetApp&lt;/P&gt;&lt;P&gt;852.3605.7700 Main&lt;/P&gt;&lt;P&gt;852.9181.8824 Mobile Phone&lt;/P&gt;&lt;P&gt;terrence.lee@netapp.com&lt;/P&gt;&lt;P&gt;Learn how: netapp.com/guarantee&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 May 2009 02:42:30 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Qtree-migration/m-p/15251#M1392</guid>
      <dc:creator>tatlee</dc:creator>
      <dc:date>2009-05-20T02:42:30Z</dc:date>
    </item>
    <item>
      <title>Re: Qtree migration</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Qtree-migration/m-p/15255#M1393</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Great...thanks for the info. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Terrence Lee&lt;/P&gt;&lt;P&gt;NetApp Global Services&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NetApp&lt;/P&gt;&lt;P&gt;852.3605.7700 Main&lt;/P&gt;&lt;P&gt;852.9181.8824 Mobile Phone&lt;/P&gt;&lt;P&gt;terrence.lee@netapp.com&lt;/P&gt;&lt;P&gt;Learn how: netapp.com/guarantee&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 May 2009 02:49:30 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Qtree-migration/m-p/15255#M1393</guid>
      <dc:creator>tatlee</dc:creator>
      <dc:date>2009-05-20T02:49:30Z</dc:date>
    </item>
  </channel>
</rss>

