<?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: vol copy and deduplication in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/vol-copy-and-deduplication/m-p/57133#M13449</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Richard,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That's great. Thanks for the quick reply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ben. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 14 Jun 2010 20:29:47 GMT</pubDate>
    <dc:creator>benknights</dc:creator>
    <dc:date>2010-06-14T20:29:47Z</dc:date>
    <item>
      <title>vol copy and deduplication</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/vol-copy-and-deduplication/m-p/57123#M13447</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;One of my customers is looking to perform some data migrations. These will be within the same filer. The question they have is as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;‘If the source volume has 500GB of dedupe savings, should I account for this when I create the new destination volume, i.e. add an additional 500GB of space on top of the used space requirements? I will enable dedupe on the destination volume once the data has been migrated but initially I am assuming that we'll lose the dedupe savings.’&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;They intend to use ‘vol copy’ as they want to copy over their snapshots as well as the data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ben.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:13:32 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/vol-copy-and-deduplication/m-p/57123#M13447</guid>
      <dc:creator>benknights</dc:creator>
      <dc:date>2025-06-05T07:13:32Z</dc:date>
    </item>
    <item>
      <title>Re: vol copy and deduplication</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/vol-copy-and-deduplication/m-p/57129#M13448</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ben,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Having just performed 100 vol copy migrations on a lab system with dedupe enabled volumes here’s a few answers based on firsthand experience.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Destination volume was the almost the same size (+1%) as the source volume (some copies failed first time as the destination volume seems to need a little more free space – probably for the snapshot created by the vol copy operation).&lt;/P&gt;&lt;P&gt;Vol copy process maintains the de-duped state of the source volume on the destination volume so no need to run sis start –s on destination volume&lt;/P&gt;&lt;P&gt;Vol copy process maintains the de-dupe scheduling of the source volume on the destination volume so no need to run sis config on destination volume&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Richard&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jun 2010 19:42:35 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/vol-copy-and-deduplication/m-p/57129#M13448</guid>
      <dc:creator>RichardSopp</dc:creator>
      <dc:date>2010-06-14T19:42:35Z</dc:date>
    </item>
    <item>
      <title>Re: vol copy and deduplication</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/vol-copy-and-deduplication/m-p/57133#M13449</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Richard,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That's great. Thanks for the quick reply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ben. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jun 2010 20:29:47 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/vol-copy-and-deduplication/m-p/57133#M13449</guid>
      <dc:creator>benknights</dc:creator>
      <dc:date>2010-06-14T20:29:47Z</dc:date>
    </item>
    <item>
      <title>Re: vol copy and deduplication</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/vol-copy-and-deduplication/m-p/57137#M13451</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Remember, starting with Data ONTAP 7.3, some of the deduplication metadata&lt;/P&gt;&lt;P&gt;files do not get copied by the vol copy command, because they are located&lt;/P&gt;&lt;P&gt;outside of the volume in the aggregate.   The data will indeed retain the&lt;/P&gt;&lt;P&gt;space savings, and the deduplication process will continue for any new data&lt;/P&gt;&lt;P&gt;written to the destination volume.  The deduplication process obtains space&lt;/P&gt;&lt;P&gt;savings for the new data only and does not deduplicate between the new data&lt;/P&gt;&lt;P&gt;and the pre-existing (copied) data. To run deduplication for all the data in&lt;/P&gt;&lt;P&gt;the cloned volume (and thus obtain higher space savings), use the sis start&lt;/P&gt;&lt;P&gt;-s command.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Jun 2010 07:23:05 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/vol-copy-and-deduplication/m-p/57137#M13451</guid>
      <dc:creator>calvarez</dc:creator>
      <dc:date>2010-06-15T07:23:05Z</dc:date>
    </item>
  </channel>
</rss>

