<?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: Ontap 9 Filehandle preservation in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Ontap-9-Filehandle-preservation/m-p/130525#M28404</link>
    <description>&lt;P&gt;Hi, i did read that KB article and this is all done from 9.1P1.&amp;nbsp; No migration.&amp;nbsp; Did verify that MSIDs are the same on both locations.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 26 Apr 2017 15:00:50 GMT</pubDate>
    <dc:creator>Chandlerbing03</dc:creator>
    <dc:date>2017-04-26T15:00:50Z</dc:date>
    <item>
      <title>Ontap 9 Filehandle preservation</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Ontap-9-Filehandle-preservation/m-p/130024#M28312</link>
      <description>&lt;P&gt;I read that SVM-DR relations can preserve volume MSIDs which allows NFS file handles to remain valid in a disaster recovery scenario without the need to re-mount.&amp;nbsp; I tested this with a AFFA300 running 9.1P1 and RHEL VM using NFSv3.&amp;nbsp; Confirmed the msid-preserve is set to true.&amp;nbsp; Performed a SVM DR failover from one site to another site the unix mount froze and was not able to recover unless a lazy unmount was performed.&amp;nbsp; Is there mount options that need to be added or is this only for NFSv4?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 15:12:49 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Ontap-9-Filehandle-preservation/m-p/130024#M28312</guid>
      <dc:creator>Chandlerbing03</dc:creator>
      <dc:date>2025-06-04T15:12:49Z</dc:date>
    </item>
    <item>
      <title>Re: Ontap 9 Filehandle preservation</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Ontap-9-Filehandle-preservation/m-p/130029#M28315</link>
      <description>To be sure - DR SVM was using the same IP addresses? Were they reacheable from NFS client? This may be network issue like stale ARP caches.</description>
      <pubDate>Wed, 12 Apr 2017 02:32:15 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Ontap-9-Filehandle-preservation/m-p/130029#M28315</guid>
      <dc:creator>aborzenkov</dc:creator>
      <dc:date>2017-04-12T02:32:15Z</dc:date>
    </item>
    <item>
      <title>Re: Ontap 9 Filehandle preservation</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Ontap-9-Filehandle-preservation/m-p/130042#M28319</link>
      <description>&lt;P&gt;If you've moved the SVM/Cluster from 8.3 to 9, the SVM DR relationship by default will not preserve MSIDs. New relationships created under 9.0 will however.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have instructions for upgrading the DR relationship in the first case, as well as general troubleshooting at&amp;nbsp;&lt;A href="https://kb.netapp.com/support/s/article/ka31A0000000jXPQAY/how-to-preserve-nfs-file-handles-and-volume-msids-with-svm-dr-vserver-disaster-recovery?language=en_US" target="_blank"&gt;https://kb.netapp.com/support/s/article/ka31A0000000jXPQAY/how-to-preserve-nfs-file-handles-and-volume-msids-with-svm-dr-vserver-disaster-recovery?language=en_US&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please let me know if this helps!&lt;/P&gt;</description>
      <pubDate>Wed, 12 Apr 2017 06:21:10 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Ontap-9-Filehandle-preservation/m-p/130042#M28319</guid>
      <dc:creator>AlexDawson</dc:creator>
      <dc:date>2017-04-12T06:21:10Z</dc:date>
    </item>
    <item>
      <title>Re: Ontap 9 Filehandle preservation</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Ontap-9-Filehandle-preservation/m-p/130525#M28404</link>
      <description>&lt;P&gt;Hi, i did read that KB article and this is all done from 9.1P1.&amp;nbsp; No migration.&amp;nbsp; Did verify that MSIDs are the same on both locations.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Apr 2017 15:00:50 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Ontap-9-Filehandle-preservation/m-p/130525#M28404</guid>
      <dc:creator>Chandlerbing03</dc:creator>
      <dc:date>2017-04-26T15:00:50Z</dc:date>
    </item>
    <item>
      <title>Re: Ontap 9 Filehandle preservation</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Ontap-9-Filehandle-preservation/m-p/130526#M28405</link>
      <description>&lt;P&gt;No, DR SVM is using different IP.&amp;nbsp; The VLAN is not stretched.&amp;nbsp; After DR cutover all IPs are reachable and DNS of SVM was manually changed to point to DR LIF.&amp;nbsp; Mount still hung doing a ls command.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Apr 2017 15:03:38 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Ontap-9-Filehandle-preservation/m-p/130526#M28405</guid>
      <dc:creator>Chandlerbing03</dc:creator>
      <dc:date>2017-04-26T15:03:38Z</dc:date>
    </item>
    <item>
      <title>Re: Ontap 9 Filehandle preservation</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Ontap-9-Filehandle-preservation/m-p/130532#M28407</link>
      <description>Client NFS mount is tied to specific address. There is no way to transparently migrate to different IP - client must remount. It is not related to MSID..</description>
      <pubDate>Wed, 26 Apr 2017 15:43:55 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Ontap-9-Filehandle-preservation/m-p/130532#M28407</guid>
      <dc:creator>aborzenkov</dc:creator>
      <dc:date>2017-04-26T15:43:55Z</dc:date>
    </item>
  </channel>
</rss>

