<?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 Snapvault compression on tertiary? in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Snapvault-compression-on-tertiary/m-p/128915#M28012</link>
    <description>&lt;P&gt;Been running a snapmirror / snapvault cascade in my environment for years since 7-mode.&amp;nbsp; (Primary --&amp;gt; snapmirrored Secondary --&amp;gt; SnapVaulted Tertiary).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When we were on 7-mode, I was able to enable deduplication on the primary (and thus the secondary), and seperately enable compression on the tertiary.&amp;nbsp; This used to yield good space savings.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now that we're on CDOT 8.2.2, I'd like to enable compression on the tertiary, but after reading this, I'm not so sure:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;"If the secondary volume has additional compression enabled, storage efficiency is not preserved.&amp;nbsp; Storage efficiency on all data transfers in SnapVault relationships is not preserved when the secondary volume has additional compression enabled. Because of the loss of storage efficiency, a warning message is displayed when you enable compression on a SnapVault secondary volume.&amp;nbsp; After you enable compression on the secondary volume, you can never have storage-efficient transfers."&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There is no mention of tertiary volumes and compression on CDOT that I can find.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On the System Manager gui, the tertiary volume only offers the ability to enable storage efficiency (not checked by default) or not.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Try to enable compression on the tertiary volume via command line and I get this stern warning:&lt;/P&gt;&lt;P&gt;::&amp;gt; volume efficiency modify -vserver&amp;nbsp;vservername -volume&amp;nbsp;tertiaryvolume&amp;nbsp;-compression true&lt;/P&gt;&lt;P&gt;Warning: Enabling compression on a secondary volume is strongly discouraged. If compression is enabled on a secondary volume, storage efficiency present on the source will not be&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; preserved during replication. The destination system needs to run offline storage efficiency scanner (compression and dedupe) to achieve storage savings. Additional&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; compression savings on the destination comes at a cost of extra computation resources. In environments where there is a lot of shared data present on the source, (e.g.,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; virtualized environments employing file clones), data inflation during transfer may lead to failed backups due to lack of space on the secondary volume.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So compression is not an option on a snapvault tertiary volume?&amp;nbsp; Anyone tried this on a CDOT system?&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 15:20:41 GMT</pubDate>
    <dc:creator>mikesicarup</dc:creator>
    <dc:date>2025-06-04T15:20:41Z</dc:date>
    <item>
      <title>Snapvault compression on tertiary?</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Snapvault-compression-on-tertiary/m-p/128915#M28012</link>
      <description>&lt;P&gt;Been running a snapmirror / snapvault cascade in my environment for years since 7-mode.&amp;nbsp; (Primary --&amp;gt; snapmirrored Secondary --&amp;gt; SnapVaulted Tertiary).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When we were on 7-mode, I was able to enable deduplication on the primary (and thus the secondary), and seperately enable compression on the tertiary.&amp;nbsp; This used to yield good space savings.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now that we're on CDOT 8.2.2, I'd like to enable compression on the tertiary, but after reading this, I'm not so sure:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;"If the secondary volume has additional compression enabled, storage efficiency is not preserved.&amp;nbsp; Storage efficiency on all data transfers in SnapVault relationships is not preserved when the secondary volume has additional compression enabled. Because of the loss of storage efficiency, a warning message is displayed when you enable compression on a SnapVault secondary volume.&amp;nbsp; After you enable compression on the secondary volume, you can never have storage-efficient transfers."&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There is no mention of tertiary volumes and compression on CDOT that I can find.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On the System Manager gui, the tertiary volume only offers the ability to enable storage efficiency (not checked by default) or not.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Try to enable compression on the tertiary volume via command line and I get this stern warning:&lt;/P&gt;&lt;P&gt;::&amp;gt; volume efficiency modify -vserver&amp;nbsp;vservername -volume&amp;nbsp;tertiaryvolume&amp;nbsp;-compression true&lt;/P&gt;&lt;P&gt;Warning: Enabling compression on a secondary volume is strongly discouraged. If compression is enabled on a secondary volume, storage efficiency present on the source will not be&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; preserved during replication. The destination system needs to run offline storage efficiency scanner (compression and dedupe) to achieve storage savings. Additional&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; compression savings on the destination comes at a cost of extra computation resources. In environments where there is a lot of shared data present on the source, (e.g.,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; virtualized environments employing file clones), data inflation during transfer may lead to failed backups due to lack of space on the secondary volume.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So compression is not an option on a snapvault tertiary volume?&amp;nbsp; Anyone tried this on a CDOT system?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 15:20:41 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Snapvault-compression-on-tertiary/m-p/128915#M28012</guid>
      <dc:creator>mikesicarup</dc:creator>
      <dc:date>2025-06-04T15:20:41Z</dc:date>
    </item>
  </channel>
</rss>

