<?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 Protecting only Snapvault part of cascade is not working with on-Demand in Active IQ Unified Manager Discussions</title>
    <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Protecting-only-Snapvault-part-of-cascade-is-not-working-with-on-Demand/m-p/32825#M6808</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok, so here is a quick high level &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a VSM that is managed currently at the filer level with snapmriror.conf file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are implementing snapvault, but we are only implementing the management of the policy from the mirror to the vault&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So for example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our snapvault looks like&lt;/P&gt;&lt;P&gt;/vol/mirror/-&amp;nbsp;&amp;nbsp; /vol/sv_mirror/snapvault_qtree&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;We import this into PM dataset that we custom design a policy and schedule for it.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="http://community.netapp.com/legacyfs/online/25070_svpolicy.jpg" width="450" /&gt;&lt;/P&gt;&lt;P&gt;Our primary data volume, we select NONE because it's on a mirror and we know we can't take a snapshot of the read-only volume.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We then setup the transfer to back up and then retention.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, this works 100% on schedule, but does not work on-demand.&amp;nbsp;&amp;nbsp;&amp;nbsp; It fails, b/c protection manager is continuing to try to take a snapshot on the primary mirror.&amp;nbsp; This is frustrating b/c we tell it in the policy not to do it.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is the error from the job&lt;/P&gt;&lt;P&gt;Volume_SV: Could not create snapshot for volume 'filera:/sv_voltest_m' (274). Reason: Snapshot operation not allowed on a read-only volume&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's like there is a bug b/c we don't want it to take a snapshot on primary b/c we know it's a read only.&amp;nbsp; We just want it to do a transfer and then take a snapshot.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Am I missing something?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are running OCUM 5.2 p2&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 05:41:47 GMT</pubDate>
    <dc:creator>JGPSHNTAP</dc:creator>
    <dc:date>2025-06-05T05:41:47Z</dc:date>
    <item>
      <title>Protecting only Snapvault part of cascade is not working with on-Demand</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Protecting-only-Snapvault-part-of-cascade-is-not-working-with-on-Demand/m-p/32825#M6808</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok, so here is a quick high level &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a VSM that is managed currently at the filer level with snapmriror.conf file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are implementing snapvault, but we are only implementing the management of the policy from the mirror to the vault&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So for example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our snapvault looks like&lt;/P&gt;&lt;P&gt;/vol/mirror/-&amp;nbsp;&amp;nbsp; /vol/sv_mirror/snapvault_qtree&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;We import this into PM dataset that we custom design a policy and schedule for it.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="http://community.netapp.com/legacyfs/online/25070_svpolicy.jpg" width="450" /&gt;&lt;/P&gt;&lt;P&gt;Our primary data volume, we select NONE because it's on a mirror and we know we can't take a snapshot of the read-only volume.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We then setup the transfer to back up and then retention.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, this works 100% on schedule, but does not work on-demand.&amp;nbsp;&amp;nbsp;&amp;nbsp; It fails, b/c protection manager is continuing to try to take a snapshot on the primary mirror.&amp;nbsp; This is frustrating b/c we tell it in the policy not to do it.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is the error from the job&lt;/P&gt;&lt;P&gt;Volume_SV: Could not create snapshot for volume 'filera:/sv_voltest_m' (274). Reason: Snapshot operation not allowed on a read-only volume&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's like there is a bug b/c we don't want it to take a snapshot on primary b/c we know it's a read only.&amp;nbsp; We just want it to do a transfer and then take a snapshot.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Am I missing something?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are running OCUM 5.2 p2&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 05:41:47 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Protecting-only-Snapvault-part-of-cascade-is-not-working-with-on-Demand/m-p/32825#M6808</guid>
      <dc:creator>JGPSHNTAP</dc:creator>
      <dc:date>2025-06-05T05:41:47Z</dc:date>
    </item>
    <item>
      <title>Re: Protecting only Snapvault part of cascade is not working with on-Demand</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Protecting-only-Snapvault-part-of-cascade-is-not-working-with-on-Demand/m-p/32830#M6811</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just a friendly bump... anyone experience this or can set this scenario up in their lab&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Mar 2014 13:20:42 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Protecting-only-Snapvault-part-of-cascade-is-not-working-with-on-Demand/m-p/32830#M6811</guid>
      <dc:creator>JGPSHNTAP</dc:creator>
      <dc:date>2014-03-05T13:20:42Z</dc:date>
    </item>
  </channel>
</rss>

