<?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: SRM Configuration in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/SRM-Configuration/m-p/133827#M29268</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We tend to use storage vMotion when we're moving things around - but yes, it can be time consuming and such. &amp;nbsp;That said, usually about the time we're looking at migrating to new storage, we typically have either decided to do an ESX upgrade and/or restructure our datastores (i.e. go to a different storage design based on SLA, occupancy, etc). &amp;nbsp;The storage vMotion makes for a clean way of getting onto the "new" platform.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If that's not in the cards for you all, is it possible to join Cluster1 to Cluster3 together (as well as Cluster2 to Cluster4) and then just perform non-disruptive volume moves (as well as move your SVM root/LIF) over to the new storage? &amp;nbsp;We've done a ton of moves of VMware datastore volumes and it's gone very smoothly.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm not familiar enough with ESX and SAN storage (we're using NFS) to speak to the option 2 - it seems to imply some cut-over or something which makes me think there's potential downtime? &amp;nbsp;I'm probably not reading your description accurately and perhaps there's a way of doing this I'm not familiar with...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope that helps,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;</description>
    <pubDate>Tue, 22 Aug 2017 12:27:30 GMT</pubDate>
    <dc:creator>colsen</dc:creator>
    <dc:date>2017-08-22T12:27:30Z</dc:date>
    <item>
      <title>SRM Configuration</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/SRM-Configuration/m-p/133826#M29267</link>
      <description>&lt;P&gt;I have two ESX clusters (Cluster 1 at primary and Cluster 2 and secondary) with VM's replicating through SRM between Cluster 1 and Cluster 2. The underlying LUN's are replicated through snapmirror.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a task at hand to migrate the&amp;nbsp;VM's from Cluster 1 to Cluster 3 at primary and Cluster 2 to Cluster 4 at secondary. Which of the following will be a convenient solution -&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. Provisioning new LUN's to Cluster 3 and Cluster 4 and setting up a snapmirror relationship between them. Migrating the VM's on old cluster&amp;nbsp;to the new LUN's through storage vmotion.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. Mapping the old LUN mapped to Cluster 1 to the Cluster 3 and then unmapping it from Cluster 1 once the SRM relationship is setup again between the VM's on new clusters.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The second solution seems a little dodgy and it was suggested by someone so as to reduce time involved in storage vmotion. Sorry if the text is confusing.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 14:42:09 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/SRM-Configuration/m-p/133826#M29267</guid>
      <dc:creator>aniruddh22</dc:creator>
      <dc:date>2025-06-04T14:42:09Z</dc:date>
    </item>
    <item>
      <title>Re: SRM Configuration</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/SRM-Configuration/m-p/133827#M29268</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We tend to use storage vMotion when we're moving things around - but yes, it can be time consuming and such. &amp;nbsp;That said, usually about the time we're looking at migrating to new storage, we typically have either decided to do an ESX upgrade and/or restructure our datastores (i.e. go to a different storage design based on SLA, occupancy, etc). &amp;nbsp;The storage vMotion makes for a clean way of getting onto the "new" platform.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If that's not in the cards for you all, is it possible to join Cluster1 to Cluster3 together (as well as Cluster2 to Cluster4) and then just perform non-disruptive volume moves (as well as move your SVM root/LIF) over to the new storage? &amp;nbsp;We've done a ton of moves of VMware datastore volumes and it's gone very smoothly.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm not familiar enough with ESX and SAN storage (we're using NFS) to speak to the option 2 - it seems to imply some cut-over or something which makes me think there's potential downtime? &amp;nbsp;I'm probably not reading your description accurately and perhaps there's a way of doing this I'm not familiar with...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope that helps,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;</description>
      <pubDate>Tue, 22 Aug 2017 12:27:30 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/SRM-Configuration/m-p/133827#M29268</guid>
      <dc:creator>colsen</dc:creator>
      <dc:date>2017-08-22T12:27:30Z</dc:date>
    </item>
  </channel>
</rss>

