<?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 VTL Post Process Deduplication in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/VTL-Post-Process-Deduplication/m-p/68898#M9357</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Greetings and salutations. Does anyone out there have any experiences to share regarding situations where you have had issues with getting the post process completed? I am seeing that at around 70-75% of capacity, we start seeing warnings of space usage. At about 80-85% the VTL will start behaving erratically, like take the drives offline in an attempt to self-preserve. If we fill up space too fast, it can't catch up on the post process, and we have to essentially stop all backups and restores to let it finish uninterrupted. I also wondered how this VTL handles cleanup of expired, re-labled volumes. There is no indication that that is happening, like you see with volumes actually having been written to, and seen in the post process job. I also have seen that if the post process job does not finish in the window, the FSB job will not kick off to reflect any savings from the dedup process. I also think I have observed the following caveat - if you want to run backups or restores during your post process window, then out-of-band dedup is not the right product to get. Any comments out there are greatly appreciated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 07:12:55 GMT</pubDate>
    <dc:creator>bruce_breidall</dc:creator>
    <dc:date>2025-06-05T07:12:55Z</dc:date>
    <item>
      <title>VTL Post Process Deduplication</title>
      <link>https://community.netapp.com/t5/Data-Protection/VTL-Post-Process-Deduplication/m-p/68898#M9357</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Greetings and salutations. Does anyone out there have any experiences to share regarding situations where you have had issues with getting the post process completed? I am seeing that at around 70-75% of capacity, we start seeing warnings of space usage. At about 80-85% the VTL will start behaving erratically, like take the drives offline in an attempt to self-preserve. If we fill up space too fast, it can't catch up on the post process, and we have to essentially stop all backups and restores to let it finish uninterrupted. I also wondered how this VTL handles cleanup of expired, re-labled volumes. There is no indication that that is happening, like you see with volumes actually having been written to, and seen in the post process job. I also have seen that if the post process job does not finish in the window, the FSB job will not kick off to reflect any savings from the dedup process. I also think I have observed the following caveat - if you want to run backups or restores during your post process window, then out-of-band dedup is not the right product to get. Any comments out there are greatly appreciated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:12:55 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/VTL-Post-Process-Deduplication/m-p/68898#M9357</guid>
      <dc:creator>bruce_breidall</dc:creator>
      <dc:date>2025-06-05T07:12:55Z</dc:date>
    </item>
    <item>
      <title>Re: VTL Post Process Deduplication</title>
      <link>https://community.netapp.com/t5/Data-Protection/VTL-Post-Process-Deduplication/m-p/68903#M9358</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Bruce,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;as you possibly know, VTL &amp;amp; DeDup is a sensitive topic. I strongly recommend you to get in touch with NetApp professional service regarding your issues and a possible solution. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Jul 2010 19:25:24 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/VTL-Post-Process-Deduplication/m-p/68903#M9358</guid>
      <dc:creator>thomas_glodde</dc:creator>
      <dc:date>2010-07-01T19:25:24Z</dc:date>
    </item>
    <item>
      <title>Re: VTL Post Process Deduplication</title>
      <link>https://community.netapp.com/t5/Data-Protection/VTL-Post-Process-Deduplication/m-p/68908#M9359</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sensitive is an undestatement. How about criminal, would that be a better word?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have cases open, but get very little or no quality help, which is why I am trying this forum. Thanks for your response.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Jul 2010 20:14:55 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/VTL-Post-Process-Deduplication/m-p/68908#M9359</guid>
      <dc:creator>bruce_breidall</dc:creator>
      <dc:date>2010-07-01T20:14:55Z</dc:date>
    </item>
    <item>
      <title>Re: VTL Post Process Deduplication</title>
      <link>https://community.netapp.com/t5/Data-Protection/VTL-Post-Process-Deduplication/m-p/68913#M9360</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;NetApps product policy is none of my concern to discuss here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I recommend you to escalate these things with your favorite NetApp sales representative instead of customer support only. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Jul 2010 11:52:34 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/VTL-Post-Process-Deduplication/m-p/68913#M9360</guid>
      <dc:creator>thomas_glodde</dc:creator>
      <dc:date>2010-07-02T11:52:34Z</dc:date>
    </item>
  </channel>
</rss>

