<?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 with error destination requested snapshots that does not exist in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/SnapVault-with-error-destination-requested-snapshots-that-does-not-exist/m-p/96671#M4651</link>
    <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are using Virtual Storage Console (VSC) in VMware (5.5) for creating the snapshots (backup) on the primary storage. Since we still have 7-mode (no clustered yet) we cannot use SnapVault in VSC (not supported, only in CDOT). For the snapshots on the primary storage everything is working fine.&lt;BR /&gt;&lt;BR /&gt;We have created manually a SnapVault relation ship to the secondary storage. We added a Transfer schedule on the secondary storage. Now we are getting the following error message:&lt;BR /&gt;&lt;BR /&gt;"destination requested snapshot that does not exists on source filer"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But we are creating a snapshot around 10:00 PM on the primary storage system and a SnapVault transfer around 01:00 AM. What's going on here? Please advice.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Basis&lt;/P&gt;</description>
    <pubDate>Thu, 05 Jun 2025 05:24:46 GMT</pubDate>
    <dc:creator>basisinfra</dc:creator>
    <dc:date>2025-06-05T05:24:46Z</dc:date>
    <item>
      <title>SnapVault with error destination requested snapshots that does not exist</title>
      <link>https://community.netapp.com/t5/Data-Protection/SnapVault-with-error-destination-requested-snapshots-that-does-not-exist/m-p/96671#M4651</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are using Virtual Storage Console (VSC) in VMware (5.5) for creating the snapshots (backup) on the primary storage. Since we still have 7-mode (no clustered yet) we cannot use SnapVault in VSC (not supported, only in CDOT). For the snapshots on the primary storage everything is working fine.&lt;BR /&gt;&lt;BR /&gt;We have created manually a SnapVault relation ship to the secondary storage. We added a Transfer schedule on the secondary storage. Now we are getting the following error message:&lt;BR /&gt;&lt;BR /&gt;"destination requested snapshot that does not exists on source filer"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But we are creating a snapshot around 10:00 PM on the primary storage system and a SnapVault transfer around 01:00 AM. What's going on here? Please advice.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Basis&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jun 2025 05:24:46 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SnapVault-with-error-destination-requested-snapshots-that-does-not-exist/m-p/96671#M4651</guid>
      <dc:creator>basisinfra</dc:creator>
      <dc:date>2025-06-05T05:24:46Z</dc:date>
    </item>
    <item>
      <title>Re: SnapVault with error destination requested snapshots that does not exist</title>
      <link>https://community.netapp.com/t5/Data-Protection/SnapVault-with-error-destination-requested-snapshots-that-does-not-exist/m-p/96997#M4652</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sounds as if snapshot autodelete threw away your baseline snapshot. You should always disable snapshot autodelete on the source volumes for SnapVault.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 17 Nov 2014 05:40:23 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SnapVault-with-error-destination-requested-snapshots-that-does-not-exist/m-p/96997#M4652</guid>
      <dc:creator>deepuj</dc:creator>
      <dc:date>2014-11-17T05:40:23Z</dc:date>
    </item>
  </channel>
</rss>

