<?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: Failed to Rename Snapshot in VMware Solutions Discussions</title>
    <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Failed-to-Rename-Snapshot/m-p/79760#M7742</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well...disregard.&amp;nbsp; Problem solved.&amp;nbsp; Believe it or not, the issue was that our OLD VSC server, which was supposed to be shut off, was &lt;STRONG&gt;restarted&lt;/STRONG&gt; on Friday for patching.&amp;nbsp; It hadn't been fully decommissioned yet.&amp;nbsp; When it restarted, the VSC services on it restarted.&amp;nbsp; So, two different sources were trying to run the VSC backup jobs, and one of them was failing.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 27 Nov 2013 18:14:45 GMT</pubDate>
    <dc:creator>TMADOCTHOMAS</dc:creator>
    <dc:date>2013-11-27T18:14:45Z</dc:date>
    <item>
      <title>Failed to Rename Snapshot</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Failed-to-Rename-Snapshot/m-p/79756#M7741</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We recently installed VSC 4.1 on a brand new 2008 R2 EE server and migrated the database from our old server, which was running VSC 2.1.2.&amp;nbsp; It worked fine for a couple of weeks.&amp;nbsp; Then, during last weekend (which was our weekend for patching servers), we started getting VSC errors.&amp;nbsp; Specifically, the errors indicated failure to rename the most recent snapshot to "snapshotname"_recent.&amp;nbsp; NetApp Support had me manually rename the current snapshots that ended in "_recent" to something else.&amp;nbsp; When I did this, I was able to successfully run the backups.&amp;nbsp; However, when regularly scheduled backups kicked off later that night, I got the same error message.&amp;nbsp; I couldn't manually run them either without renaming the "_recent" snapshot again.&amp;nbsp; Has anyone encountered this and/or found a resolution?&amp;nbsp; I'm about to contact NetApp Support again but wanted to check here as well to see if anyone has a resolution.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 05:48:39 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Failed-to-Rename-Snapshot/m-p/79756#M7741</guid>
      <dc:creator>TMADOCTHOMAS</dc:creator>
      <dc:date>2025-06-05T05:48:39Z</dc:date>
    </item>
    <item>
      <title>Re: Failed to Rename Snapshot</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Failed-to-Rename-Snapshot/m-p/79760#M7742</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well...disregard.&amp;nbsp; Problem solved.&amp;nbsp; Believe it or not, the issue was that our OLD VSC server, which was supposed to be shut off, was &lt;STRONG&gt;restarted&lt;/STRONG&gt; on Friday for patching.&amp;nbsp; It hadn't been fully decommissioned yet.&amp;nbsp; When it restarted, the VSC services on it restarted.&amp;nbsp; So, two different sources were trying to run the VSC backup jobs, and one of them was failing.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Nov 2013 18:14:45 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Failed-to-Rename-Snapshot/m-p/79760#M7742</guid>
      <dc:creator>TMADOCTHOMAS</dc:creator>
      <dc:date>2013-11-27T18:14:45Z</dc:date>
    </item>
  </channel>
</rss>

