<?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 case NetApp Log # 2003465121-Burt and case  NetApp Log # 2003456803 in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/case-NetApp-Log-2003465121-Burt-and-case-NetApp-Log-2003456803/m-p/78452#M2667</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there a way to specify the SnapMirror target so SnapCreator does not have to query the source to discover it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have &lt;SPAN style="font-family: &amp;amp;quot;Calibri&amp;amp;quot;,&amp;amp;quot;sans-serif&amp;amp;quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: &amp;amp;quot;Times New Roman&amp;amp;quot;; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"&gt;the same source and target volume names, which has exposed us to the BURT mentioned in the NetApp case LOG#2003465121. We have a globa config file with NTAP_SNAPMIRROR_UPDATE=Y.&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: &amp;amp;quot;Calibri&amp;amp;quot;,&amp;amp;quot;sans-serif&amp;amp;quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: &amp;amp;quot;Times New Roman&amp;amp;quot;; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"&gt;Can we specify the SnapMirror target for SnapCreator??&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 06:20:01 GMT</pubDate>
    <dc:creator>debpearenetapp</dc:creator>
    <dc:date>2025-06-05T06:20:01Z</dc:date>
    <item>
      <title>case NetApp Log # 2003465121-Burt and case  NetApp Log # 2003456803</title>
      <link>https://community.netapp.com/t5/Data-Protection/case-NetApp-Log-2003465121-Burt-and-case-NetApp-Log-2003456803/m-p/78452#M2667</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there a way to specify the SnapMirror target so SnapCreator does not have to query the source to discover it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have &lt;SPAN style="font-family: &amp;amp;quot;Calibri&amp;amp;quot;,&amp;amp;quot;sans-serif&amp;amp;quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: &amp;amp;quot;Times New Roman&amp;amp;quot;; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"&gt;the same source and target volume names, which has exposed us to the BURT mentioned in the NetApp case LOG#2003465121. We have a globa config file with NTAP_SNAPMIRROR_UPDATE=Y.&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: &amp;amp;quot;Calibri&amp;amp;quot;,&amp;amp;quot;sans-serif&amp;amp;quot;; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: &amp;amp;quot;Times New Roman&amp;amp;quot;; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"&gt;Can we specify the SnapMirror target for SnapCreator??&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:20:01 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/case-NetApp-Log-2003465121-Burt-and-case-NetApp-Log-2003456803/m-p/78452#M2667</guid>
      <dc:creator>debpearenetapp</dc:creator>
      <dc:date>2025-06-05T06:20:01Z</dc:date>
    </item>
    <item>
      <title>Re: case NetApp Log # 2003465121-Burt and case  NetApp Log # 2003456803</title>
      <link>https://community.netapp.com/t5/Data-Protection/case-NetApp-Log-2003465121-Burt-and-case-NetApp-Log-2003456803/m-p/78457#M2668</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No there is not&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SC will find all SM relationships automatically that exist for volume specified in SNAPMIRROR_VOLUMES and perform an update. If the relationships are using other interfaces then you would need to use SECONDARY_INTERFACES paramater to tell SC which interfaces maps the default interface so SC finds them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want more control over this use SC with Protection Manager which allows you to specify whatever you want in dataset and SC can integrate with PM nicely.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Keith&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 Aug 2012 08:19:52 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/case-NetApp-Log-2003465121-Burt-and-case-NetApp-Log-2003456803/m-p/78457#M2668</guid>
      <dc:creator>ktenzer</dc:creator>
      <dc:date>2012-08-31T08:19:52Z</dc:date>
    </item>
  </channel>
</rss>

