<?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 SMVI initiated SnapMirror update vs. Scheduled Updates in VMware Solutions Discussions</title>
    <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/SMVI-initiated-SnapMirror-update-vs-Scheduled-Updates/m-p/118769#M8609</link>
    <description>&lt;P&gt;Is there a difference in the way a SnapMirror update initiated by SMVI works vs. the way it works if you schedule an update? &amp;nbsp;We upgraded to VSC 6.0 from 4.2 and due to the way the NFS lif's were using the same IP addresses between sites (I didn't do it... promise) &amp;nbsp;we can no longer have SMVI initiate the snap mirror updates. (known issue with 6.0 that is not scheduled to be fixed).&lt;BR /&gt;&lt;BR /&gt;In order to get around this while the vlans for data are redesigned i set up schedules for each job. &amp;nbsp;The Ops team is telling me that it seems like the snaps are quite a bit bigger now. &amp;nbsp; I just wanted to check to see if that's something that is expected or if we need to start digging into that more from the VM side.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are snapping daily and the updates kick off about 10 min after the SMVI job starts.&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 21:13:08 GMT</pubDate>
    <dc:creator>dnchance</dc:creator>
    <dc:date>2025-06-04T21:13:08Z</dc:date>
    <item>
      <title>SMVI initiated SnapMirror update vs. Scheduled Updates</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/SMVI-initiated-SnapMirror-update-vs-Scheduled-Updates/m-p/118769#M8609</link>
      <description>&lt;P&gt;Is there a difference in the way a SnapMirror update initiated by SMVI works vs. the way it works if you schedule an update? &amp;nbsp;We upgraded to VSC 6.0 from 4.2 and due to the way the NFS lif's were using the same IP addresses between sites (I didn't do it... promise) &amp;nbsp;we can no longer have SMVI initiate the snap mirror updates. (known issue with 6.0 that is not scheduled to be fixed).&lt;BR /&gt;&lt;BR /&gt;In order to get around this while the vlans for data are redesigned i set up schedules for each job. &amp;nbsp;The Ops team is telling me that it seems like the snaps are quite a bit bigger now. &amp;nbsp; I just wanted to check to see if that's something that is expected or if we need to start digging into that more from the VM side.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are snapping daily and the updates kick off about 10 min after the SMVI job starts.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 21:13:08 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/SMVI-initiated-SnapMirror-update-vs-Scheduled-Updates/m-p/118769#M8609</guid>
      <dc:creator>dnchance</dc:creator>
      <dc:date>2025-06-04T21:13:08Z</dc:date>
    </item>
  </channel>
</rss>

