<?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: XCP isync nodata option impact? in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/XCP-isync-nodata-option-impact/m-p/454943#M14043</link>
    <description>&lt;P&gt;Hello Paul,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-&amp;nbsp;&lt;SPAN&gt;&lt;SPAN class=""&gt;No data means, it will only check the file modify time, attributes and&amp;nbsp;wont check the actual data.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;- You can use&amp;nbsp;sync instead of isync&amp;nbsp;because it will create index and compare data next time you resume sync.&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;- Since the xcp sync does not scan the actual data ever and instead it looks into the database (index) that XCP maintains, we dont have a -nodata option with XCP sync.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;-&amp;nbsp;It compares the SRC and DST via the database (index) that it maintains.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;- Matching KB:&amp;nbsp;&lt;A href="https://kb.netapp.com/on-prem/ontap/da/XCP/XCP-KBs/What_is_xcp_isync" target="_blank" rel="noopener"&gt;https://kb.netapp.com/on-prem/ontap/da/XCP/XCP-KBs/What_is_xcp_isync&lt;/A&gt;&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope my answers help.&lt;/P&gt;</description>
    <pubDate>Tue, 10 Sep 2024 06:14:12 GMT</pubDate>
    <dc:creator>ChLokesh</dc:creator>
    <dc:date>2024-09-10T06:14:12Z</dc:date>
    <item>
      <title>XCP isync nodata option impact?</title>
      <link>https://community.netapp.com/t5/Data-Protection/XCP-isync-nodata-option-impact/m-p/454454#M14037</link>
      <description>&lt;P&gt;What is the impact of using the "-nodata" option when running an "isync"?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For example, we had a partial copy of source data on a destination NetApp volume (a previously failed XCP copy due to stability issues on the source non-NetApp storage box. We had to use a different source box so couldn't reuse the previous copy catalog ID). We needed to establish a new catalog of the current state along with resuming the copy operation, so we opted to use isync rather than deleting all destination data and starting a fresh copy. (we're talking 250Tb over a 1Gb network link... ancient hardware with no option to improve the speed)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Due to the slow 1Gb link, iSync was taking a long time because XCP was reading in all data over the 1Gb link from the source so it could do a byte-for-byte check. Things drastically improved when we used the -nodata option, but what impact could using this have on the isync process besides being faster? What are we loosing out on?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The source data is live so changes can occur during each XCP run. Once the isync finishes I plan to use "sync" with the new catalog ID. Would this be ok?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why does sync not have a -nodata option compared to isync? How does a sync check if a source file has changed without reading the whole file into the XCP server to do a byte-for-byte comparison?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;Paul.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Aug 2024 13:32:24 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/XCP-isync-nodata-option-impact/m-p/454454#M14037</guid>
      <dc:creator>Paul3</dc:creator>
      <dc:date>2024-08-13T13:32:24Z</dc:date>
    </item>
    <item>
      <title>Re: XCP isync nodata option impact?</title>
      <link>https://community.netapp.com/t5/Data-Protection/XCP-isync-nodata-option-impact/m-p/454943#M14043</link>
      <description>&lt;P&gt;Hello Paul,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-&amp;nbsp;&lt;SPAN&gt;&lt;SPAN class=""&gt;No data means, it will only check the file modify time, attributes and&amp;nbsp;wont check the actual data.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;- You can use&amp;nbsp;sync instead of isync&amp;nbsp;because it will create index and compare data next time you resume sync.&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;- Since the xcp sync does not scan the actual data ever and instead it looks into the database (index) that XCP maintains, we dont have a -nodata option with XCP sync.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;-&amp;nbsp;It compares the SRC and DST via the database (index) that it maintains.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;- Matching KB:&amp;nbsp;&lt;A href="https://kb.netapp.com/on-prem/ontap/da/XCP/XCP-KBs/What_is_xcp_isync" target="_blank" rel="noopener"&gt;https://kb.netapp.com/on-prem/ontap/da/XCP/XCP-KBs/What_is_xcp_isync&lt;/A&gt;&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope my answers help.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Sep 2024 06:14:12 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/XCP-isync-nodata-option-impact/m-p/454943#M14043</guid>
      <dc:creator>ChLokesh</dc:creator>
      <dc:date>2024-09-10T06:14:12Z</dc:date>
    </item>
  </channel>
</rss>

