<?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: Are Snapmirror Destinations always thick? in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Are-Snapmirror-Destinations-always-thick/m-p/122213#M26196</link>
    <description>&lt;P&gt;Just set space gurantee and fractional reserve on destination using "volume modify".&lt;/P&gt;</description>
    <pubDate>Thu, 11 Aug 2016 13:08:31 GMT</pubDate>
    <dc:creator>aborzenkov</dc:creator>
    <dc:date>2016-08-11T13:08:31Z</dc:date>
    <item>
      <title>Are Snapmirror Destinations always thick?</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Are-Snapmirror-Destinations-always-thick/m-p/122211#M26195</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;i created a thin 3 TB volume on Snapmirror Source. There is no data in this volume so "aggr show" did not show decreasing available space.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then I replicated this volume to Snapmirror Destination Filer (both cDot 8.3.1p1). Available aggr space on destination filer decreased there about 3 TB. "volume show-footprint" shows 3 TB at parameter "Volume guarantee". If I increase the volmes size at source filer this parameter automatically increases too and aggregates space is decreasing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this normal? Are Snapmirror Destination Volumes always thick or can i make them thin somehow?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 19:34:06 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Are-Snapmirror-Destinations-always-thick/m-p/122211#M26195</guid>
      <dc:creator>netrz</dc:creator>
      <dc:date>2025-06-04T19:34:06Z</dc:date>
    </item>
    <item>
      <title>Re: Are Snapmirror Destinations always thick?</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Are-Snapmirror-Destinations-always-thick/m-p/122213#M26196</link>
      <description>&lt;P&gt;Just set space gurantee and fractional reserve on destination using "volume modify".&lt;/P&gt;</description>
      <pubDate>Thu, 11 Aug 2016 13:08:31 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Are-Snapmirror-Destinations-always-thick/m-p/122213#M26196</guid>
      <dc:creator>aborzenkov</dc:creator>
      <dc:date>2016-08-11T13:08:31Z</dc:date>
    </item>
    <item>
      <title>Re: Are Snapmirror Destinations always thick?</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Are-Snapmirror-Destinations-always-thick/m-p/122221#M26199</link>
      <description>&lt;P&gt;I set space guarantee to none. This reduced aggregate usage. I did not change fractional reserve, since we are not using LUNs there and I think frctionla reserve is mainly related to LUNs.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Aug 2016 14:00:10 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Are-Snapmirror-Destinations-always-thick/m-p/122221#M26199</guid>
      <dc:creator>netrz</dc:creator>
      <dc:date>2016-08-11T14:00:10Z</dc:date>
    </item>
  </channel>
</rss>

