<?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 NFS SnapMirror Disaster Recovery in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/NFS-SnapMirror-Disaster-Recovery/m-p/89937#M7422</link>
    <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are running two VMware clusters on two NetApp filers using SnapMirror async replication an VMware SRM.&lt;/P&gt;&lt;P&gt;As NetApp supports NFS as native protocol we want to use this as the prinicipal means to supply the home directories for Linux clients.&lt;/P&gt;&lt;P&gt;Is it possible to use a "floating" IP address between the NetApp filers that is switched (automatically) from the protected to the recovery filer at a failover so the virtual machines can use the same NFS mount commands irrespective of the location they are booted on?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;TIA,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;</description>
    <pubDate>Thu, 05 Jun 2025 05:28:15 GMT</pubDate>
    <dc:creator>lsopvw</dc:creator>
    <dc:date>2025-06-05T05:28:15Z</dc:date>
    <item>
      <title>NFS SnapMirror Disaster Recovery</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/NFS-SnapMirror-Disaster-Recovery/m-p/89937#M7422</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are running two VMware clusters on two NetApp filers using SnapMirror async replication an VMware SRM.&lt;/P&gt;&lt;P&gt;As NetApp supports NFS as native protocol we want to use this as the prinicipal means to supply the home directories for Linux clients.&lt;/P&gt;&lt;P&gt;Is it possible to use a "floating" IP address between the NetApp filers that is switched (automatically) from the protected to the recovery filer at a failover so the virtual machines can use the same NFS mount commands irrespective of the location they are booted on?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;TIA,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jun 2025 05:28:15 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/NFS-SnapMirror-Disaster-Recovery/m-p/89937#M7422</guid>
      <dc:creator>lsopvw</dc:creator>
      <dc:date>2025-06-05T05:28:15Z</dc:date>
    </item>
    <item>
      <title>Re: NFS SnapMirror Disaster Recovery</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/NFS-SnapMirror-Disaster-Recovery/m-p/90313#M7435</link>
      <description>&lt;P&gt;What I can think about the "Floating IP" is the HA failover in Data ONTAP 7 mode and Logical Interface Failover in ClusterMode. Another DR technique is the metrocluster. But none of them seems to fit into your requirements, unfortunately.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What about letting the clients mount the NFS exports using the storage system's hostname - instead of IP address, and changing the DNS entry for that hostname during the DR operations or something like that?&lt;/P&gt;</description>
      <pubDate>Tue, 30 Sep 2014 06:26:40 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/NFS-SnapMirror-Disaster-Recovery/m-p/90313#M7435</guid>
      <dc:creator>georgevj</dc:creator>
      <dc:date>2014-09-30T06:26:40Z</dc:date>
    </item>
  </channel>
</rss>

