<?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 SnapCenter 2.0 - Can not protect new volume &amp;quot;not available for backup&amp;quot; in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/SnapCenter-2-0-Can-not-protect-new-volume-quot-not-available-for-backup-quot/m-p/132071#M11427</link>
    <description>&lt;P&gt;Hello, I wanted to protect a new volume "vol2" using SnapCenter with the policy to backup to AltaVault but the newly created volume (that was a splitted clone from vol1) doesn't show unprotected (gray).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Before I was playing around with protecting vol1 to AltaVault and deleted, but delete operation failed with blocked snapshot. So I decided to create new volume and try to protect it.&lt;/P&gt;&lt;P&gt;Its Playground only to test SC operation and make myself more familiar with it.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Even if I remove the old relationship from Altavault, FAS it did not refresh in SnapCenter.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a way to force SnapCenter to resync it's information about Resources?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;regards Frank&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 14:56:33 GMT</pubDate>
    <dc:creator>F_SCHUBERT</dc:creator>
    <dc:date>2025-06-04T14:56:33Z</dc:date>
    <item>
      <title>SnapCenter 2.0 - Can not protect new volume "not available for backup"</title>
      <link>https://community.netapp.com/t5/Data-Protection/SnapCenter-2-0-Can-not-protect-new-volume-quot-not-available-for-backup-quot/m-p/132071#M11427</link>
      <description>&lt;P&gt;Hello, I wanted to protect a new volume "vol2" using SnapCenter with the policy to backup to AltaVault but the newly created volume (that was a splitted clone from vol1) doesn't show unprotected (gray).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Before I was playing around with protecting vol1 to AltaVault and deleted, but delete operation failed with blocked snapshot. So I decided to create new volume and try to protect it.&lt;/P&gt;&lt;P&gt;Its Playground only to test SC operation and make myself more familiar with it.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Even if I remove the old relationship from Altavault, FAS it did not refresh in SnapCenter.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a way to force SnapCenter to resync it's information about Resources?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;regards Frank&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 14:56:33 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SnapCenter-2-0-Can-not-protect-new-volume-quot-not-available-for-backup-quot/m-p/132071#M11427</guid>
      <dc:creator>F_SCHUBERT</dc:creator>
      <dc:date>2025-06-04T14:56:33Z</dc:date>
    </item>
    <item>
      <title>Re: SnapCenter 2.0 - Can not protect new volume "not available for backup"</title>
      <link>https://community.netapp.com/t5/Data-Protection/SnapCenter-2-0-Can-not-protect-new-volume-quot-not-available-for-backup-quot/m-p/132073#M11428</link>
      <description>&lt;P&gt;Found out that after mounting volume to new junction-path volume did appear in resources tab "gray" and I could protect it.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2017 15:01:09 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SnapCenter-2-0-Can-not-protect-new-volume-quot-not-available-for-backup-quot/m-p/132073#M11428</guid>
      <dc:creator>F_SCHUBERT</dc:creator>
      <dc:date>2017-06-20T15:01:09Z</dc:date>
    </item>
  </channel>
</rss>

