<?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: SnapProtect, SnapVault secondary volume size in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/SnapProtect-SnapVault-secondary-volume-size/m-p/108315#M4126</link>
    <description>&lt;DIV class="lia-message-body lia-component-body"&gt;&lt;DIV class="lia-message-body-content"&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class="lia-message-tags lia-component-tags"&gt;Right, I can see that SP creates a destination volume set to 70TB grow-shrink mode.&lt;/DIV&gt;&lt;DIV class="lia-message-tags lia-component-tags"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="lia-message-tags lia-component-tags"&gt;Though, after the first backup the volume is downsized and the backups after that stop with volume full errors without further autosizing.&lt;/DIV&gt;&lt;DIV class="lia-message-tags lia-component-tags"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="lia-message-tags lia-component-tags"&gt;Maybe I missed some setting!?&lt;/DIV&gt;</description>
    <pubDate>Fri, 07 Aug 2015 07:44:04 GMT</pubDate>
    <dc:creator>schmitz_peter</dc:creator>
    <dc:date>2015-08-07T07:44:04Z</dc:date>
    <item>
      <title>SnapProtect, SnapVault secondary volume size</title>
      <link>https://community.netapp.com/t5/Data-Protection/SnapProtect-SnapVault-secondary-volume-size/m-p/108256#M4124</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;in the old world, when I used SnapVault via Protection manager, the destination volume would have been resized by dfpm.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are in the process of migrating our backup to SnapProtect.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How are secondary volume sizes handled? Do I have to resize manually, or is this done by SP?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for any info&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 23:36:07 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SnapProtect-SnapVault-secondary-volume-size/m-p/108256#M4124</guid>
      <dc:creator>schmitz_peter</dc:creator>
      <dc:date>2025-06-04T23:36:07Z</dc:date>
    </item>
    <item>
      <title>Re: SnapProtect, SnapVault secondary volume size</title>
      <link>https://community.netapp.com/t5/Data-Protection/SnapProtect-SnapVault-secondary-volume-size/m-p/108302#M4125</link>
      <description>&lt;P&gt;SnapProtect works with DFM to handle the provisioning / re-sizing of the vault targets.&lt;/P&gt;</description>
      <pubDate>Thu, 06 Aug 2015 22:31:36 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SnapProtect-SnapVault-secondary-volume-size/m-p/108302#M4125</guid>
      <dc:creator>rwelshman</dc:creator>
      <dc:date>2015-08-06T22:31:36Z</dc:date>
    </item>
    <item>
      <title>Re: SnapProtect, SnapVault secondary volume size</title>
      <link>https://community.netapp.com/t5/Data-Protection/SnapProtect-SnapVault-secondary-volume-size/m-p/108315#M4126</link>
      <description>&lt;DIV class="lia-message-body lia-component-body"&gt;&lt;DIV class="lia-message-body-content"&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class="lia-message-tags lia-component-tags"&gt;Right, I can see that SP creates a destination volume set to 70TB grow-shrink mode.&lt;/DIV&gt;&lt;DIV class="lia-message-tags lia-component-tags"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="lia-message-tags lia-component-tags"&gt;Though, after the first backup the volume is downsized and the backups after that stop with volume full errors without further autosizing.&lt;/DIV&gt;&lt;DIV class="lia-message-tags lia-component-tags"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="lia-message-tags lia-component-tags"&gt;Maybe I missed some setting!?&lt;/DIV&gt;</description>
      <pubDate>Fri, 07 Aug 2015 07:44:04 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SnapProtect-SnapVault-secondary-volume-size/m-p/108315#M4126</guid>
      <dc:creator>schmitz_peter</dc:creator>
      <dc:date>2015-08-07T07:44:04Z</dc:date>
    </item>
    <item>
      <title>Re: SnapProtect, SnapVault secondary volume size</title>
      <link>https://community.netapp.com/t5/Data-Protection/SnapProtect-SnapVault-secondary-volume-size/m-p/108358#M4127</link>
      <description>&lt;P&gt;Do you see anything on the vault logs about volume resize attempts? I had a look at the provisioning policy in use at my shop but there doesn't seem to be a setting to enable or disable resizing.&lt;/P&gt;</description>
      <pubDate>Fri, 07 Aug 2015 22:02:10 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SnapProtect-SnapVault-secondary-volume-size/m-p/108358#M4127</guid>
      <dc:creator>rwelshman</dc:creator>
      <dc:date>2015-08-07T22:02:10Z</dc:date>
    </item>
    <item>
      <title>Re: SnapProtect, SnapVault secondary volume size</title>
      <link>https://community.netapp.com/t5/Data-Protection/SnapProtect-SnapVault-secondary-volume-size/m-p/108410#M4128</link>
      <description>&lt;P&gt;You might try changing the "Autosize Grow Threshold Percentage:" and the "-Autosize Increment (for flexvols only):" settings for the volume.&lt;/P&gt;&lt;P&gt;I set mine to Grow at 85% and in increments of 100GB. &amp;nbsp;The defaults were not working for me. &amp;nbsp;It seems the volume would fill up faster than it could trigger an autosize.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;gt;&amp;nbsp;vol modify -volume &amp;lt;volume_name&amp;gt; -autosize-increment 100GB&lt;/P&gt;&lt;P&gt;&amp;gt; vol modify -volume &lt;SPAN&gt;&amp;lt;volume_name&amp;gt;&lt;/SPAN&gt;&amp;nbsp;-autosize-grow-threshold-percent 85&lt;/P&gt;</description>
      <pubDate>Mon, 10 Aug 2015 15:06:42 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SnapProtect-SnapVault-secondary-volume-size/m-p/108410#M4128</guid>
      <dc:creator>jcwms1971</dc:creator>
      <dc:date>2015-08-10T15:06:42Z</dc:date>
    </item>
    <item>
      <title>Re: SnapProtect, SnapVault secondary volume size</title>
      <link>https://community.netapp.com/t5/Data-Protection/SnapProtect-SnapVault-secondary-volume-size/m-p/108452#M4129</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;all I could find was a message in SP's job manager (No space left on device):&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3748 a30 07/23 03:07:30 2201 Scheduler Set pending cause [DataFabric Manager Backup Job id [9abdbbcbe8f6ed2e:-454c5e88:14eb8365c1b:-22e0] did not complete successfully for Dataset id [9cbbf396-4214-4295-8727-50999bfad63a:app_type=OCUM,type=storage_service_subscription,uuid=5e7a97ce-a169-4028-808a-0dec2b713315], Source Copy [7]. DFM Job Status = [Transfer operation for relationship 'qbit_svm:qbit_vol_008_nfs_vmwa_vmw-&amp;gt;qbit_svm_bkp:CC_qspcomserv_SP_5_Copy_8_qbit_svm_qbit_vol_008_nfs_vmwa_vmw_Backup' ended unsuccessfully. [Data ONTAP reported] Transfer failed. (Volume access error (No space left on device)).].]::Client [qspagent01] Application [AuxCopy] Message Id [419430437] RCID [0] ReservationId [0]. Level [0] flags [0] id [0] overwrite [0] append [1] CustId[0].&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;No mention of resizing, though...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;At the moment I am trying to figure out how to get snapvault logs from the filer...&lt;/P&gt;</description>
      <pubDate>Tue, 11 Aug 2015 07:56:21 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SnapProtect-SnapVault-secondary-volume-size/m-p/108452#M4129</guid>
      <dc:creator>schmitz_peter</dc:creator>
      <dc:date>2015-08-11T07:56:21Z</dc:date>
    </item>
  </channel>
</rss>

