<?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: CIFS Migration in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/CIFS-Migration/m-p/47867#M4369</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CIFS protocol is a session oriented protocol so I believe it is impossible to do it with out down time. In our migration we used DSM so mapping was done by administrators instead of users.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For LUN mapping, :&lt;/P&gt;&lt;P&gt;Unmap the initiators.&lt;/P&gt;&lt;P&gt;run snapmirror update.(to guaranty that no data will be missing)&lt;/P&gt;&lt;P&gt;online the new volume &lt;/P&gt;&lt;P&gt;map the initiators to the new LUNs&lt;/P&gt;&lt;P&gt;Release snapmirror relation to get rid of the un-needed snapmirror snapshot.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 05 Nov 2012 12:52:57 GMT</pubDate>
    <dc:creator>ahmada</dc:creator>
    <dc:date>2012-11-05T12:52:57Z</dc:date>
    <item>
      <title>CIFS Migration</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/CIFS-Migration/m-p/47862#M4368</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have successfully moved all the volumes along with their Qtree from our old NetApp to the new one , would you guys please let&amp;nbsp; me know:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. What is the next step to configure the New CIFS server in order to make changes invisible for hosts and users so they can continue using the CIFS via new NetApp without changing any mapping and etc. ( I know I have to make some changes in CIFSSetup.cfg&amp;nbsp; and other CIFS config files but dont know the exact process)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. for mapping mirrored LUNs from new NetApp to servers and un mapping the old LUNs&amp;nbsp; , what is the best practice.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:15:56 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/CIFS-Migration/m-p/47862#M4368</guid>
      <dc:creator>ALENDPR_NETAPP</dc:creator>
      <dc:date>2025-06-05T06:15:56Z</dc:date>
    </item>
    <item>
      <title>Re: CIFS Migration</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/CIFS-Migration/m-p/47867#M4369</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CIFS protocol is a session oriented protocol so I believe it is impossible to do it with out down time. In our migration we used DSM so mapping was done by administrators instead of users.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For LUN mapping, :&lt;/P&gt;&lt;P&gt;Unmap the initiators.&lt;/P&gt;&lt;P&gt;run snapmirror update.(to guaranty that no data will be missing)&lt;/P&gt;&lt;P&gt;online the new volume &lt;/P&gt;&lt;P&gt;map the initiators to the new LUNs&lt;/P&gt;&lt;P&gt;Release snapmirror relation to get rid of the un-needed snapmirror snapshot.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Nov 2012 12:52:57 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/CIFS-Migration/m-p/47867#M4369</guid>
      <dc:creator>ahmada</dc:creator>
      <dc:date>2012-11-05T12:52:57Z</dc:date>
    </item>
  </channel>
</rss>

