<?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: vfiler dr configure for alternative destination in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/vfiler-dr-configure-for-alternative-destination/m-p/2147#M212</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The volumes must be the same name on the source and target system (also the IPspace must be the same -- even if different networks the network assigned to the same IPspace name).&amp;nbsp; If you have a duplicate volume name issue on the target contorller, then we usually rename the source and target to the same unique name "vfiler_volname" for example... that can affect some shares/mounts... cifs shares will point to the new target automatically and if nfs autoexport is set it will update /etc/exports for the rename - although nfs clients will need to remount to the new target /vol/volname ... or as a workaround to not have to change the client use the "-actual" option in exports to keep the mount point name the same old volume name which points to a renamed volume.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 28 Jan 2013 02:11:45 GMT</pubDate>
    <dc:creator>scottgelb</dc:creator>
    <dc:date>2013-01-28T02:11:45Z</dc:date>
    <item>
      <title>vfiler dr configure for alternative destination</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/vfiler-dr-configure-for-alternative-destination/m-p/2142#M211</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm trying to work out if this is possible:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Filerone has a volume called 'vmware'&lt;/P&gt;&lt;P&gt;Filertwo has a volume called 'vmware_snap'&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Snapmirror is working and all good&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How can I tell the vfiler dr configure command that the volume it's looking for is vmware_snap and not vwmare?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it looks like it's -a but it doesn't work so I'm a little stumped. If it's not possible then that'll certainly answer it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vfiler dr configure [-l remote_login:remote_passwd]&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [-e interfacename:&amp;lt;ipv4-address | [ipv6-address]&amp;gt;:&amp;lt;netmask | prefixlen&amp;gt;,...]&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [-d &amp;lt;DNS-server-ipv4-address | [DNS server-ipv6-address]&amp;gt;:...]&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [-n &amp;lt;NIS-server-ipv4-address | [NIS server-ipv6-address]&amp;gt;:...]&lt;/P&gt;&lt;P&gt; &lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [-s] [-a alt-src,alt-dst]&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:11:19 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/vfiler-dr-configure-for-alternative-destination/m-p/2142#M211</guid>
      <dc:creator>GARY_WILLIAMS</dc:creator>
      <dc:date>2025-06-05T06:11:19Z</dc:date>
    </item>
    <item>
      <title>Re: vfiler dr configure for alternative destination</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/vfiler-dr-configure-for-alternative-destination/m-p/2147#M212</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The volumes must be the same name on the source and target system (also the IPspace must be the same -- even if different networks the network assigned to the same IPspace name).&amp;nbsp; If you have a duplicate volume name issue on the target contorller, then we usually rename the source and target to the same unique name "vfiler_volname" for example... that can affect some shares/mounts... cifs shares will point to the new target automatically and if nfs autoexport is set it will update /etc/exports for the rename - although nfs clients will need to remount to the new target /vol/volname ... or as a workaround to not have to change the client use the "-actual" option in exports to keep the mount point name the same old volume name which points to a renamed volume.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 28 Jan 2013 02:11:45 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/vfiler-dr-configure-for-alternative-destination/m-p/2147#M212</guid>
      <dc:creator>scottgelb</dc:creator>
      <dc:date>2013-01-28T02:11:45Z</dc:date>
    </item>
  </channel>
</rss>

