<?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: SMHV-Always having to restart Snap services to get a sucessful backup in Microsoft Virtualization Discussions</title>
    <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/SMHV-Always-having-to-restart-Snap-services-to-get-a-sucessful-backup/m-p/526#M11</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Further information:&lt;/P&gt;&lt;P&gt;From the netapp backup log:&lt;/P&gt;&lt;P&gt;[3/22/2011 11:07:47 AM, (5)] Error: Vss Requestor - Backup Components failed.The shadow copy provider had an unexpected error while trying to process the specified operation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From the windows event log:&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Data ONTAP VSS hardware provider's AbortSnapshot method is called [SnapshotSetId={e4015ab1-f679-4654-9622-2e065a84625f}]. VSS has failed the current shadow copy session because the previous errors are not continuable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;________ &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Data ONTAP VSS hardware provider failed in CommitSnapshots method [SnapshotSetId={e4015ab1-f679-4654-9622-2e065a84625f}]. SnapDrive failed to create snapshot.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Please check SnapDrive event logs.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The data is the error code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;__________&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {ddd3d232-a96f-4ac5-8f7b-250fd91fd102}. Routine details CommitSnapshots [hr = 0xc00404d1].&lt;/P&gt;&lt;P&gt;Operation:&lt;/P&gt;&lt;P&gt;Executing Asynchronous Operation&lt;/P&gt;&lt;P&gt;Context:&lt;/P&gt;&lt;P&gt;Current State: DoSnapshotSet&lt;/P&gt;&lt;P&gt;---------------------&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Failed to create a consistent Snapshot copy({e4015ab1-f679-4654-9622-2e065a84625f}) of the LUN(s) [\\?\Volume{204d8e86-7802-4def-80d5-3d34ebcd7456}\ \\?\Volume{775e3b08-6918-4dde-b9c7-9f24c6f54038}\ \\?\Volume{b6fc60f8-1d23-4bf4-85ef-3bbd3f2670e8}\ ].&lt;/P&gt;&lt;P&gt;Error code : Unable to create a Snapshot copy. Please check the application event log for more details.&lt;/P&gt;&lt;P&gt;----------------------&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Unable to create a Snapshot copy.&lt;/P&gt;&lt;P&gt;Error message : An operation to create Snapshot copy '{e4015ab1-f679-4654-9622-2e065a84625f}' across multiple volumes failed on the storage system 'DC-FAS03'.&lt;/P&gt;&lt;P&gt;Error code: 135. Error description: No more snapshots available Error volume: CSV_2008_PRODVM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 22 Mar 2011 03:52:34 GMT</pubDate>
    <dc:creator>mtrorydavies</dc:creator>
    <dc:date>2011-03-22T03:52:34Z</dc:date>
    <item>
      <title>SMHV-Always having to restart Snap services to get a sucessful backup</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/SMHV-Always-having-to-restart-Snap-services-to-get-a-sucessful-backup/m-p/512#M8</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why is it that SMHV (Version&amp;nbsp; 1.0.1.1222) and Snapdrive (Version 6.3.0.4718) always have to be restarted before I can get a sucessful guest backup?&lt;/P&gt;&lt;P&gt;Running 4 node HyperV 08R2 cluster with 29 Windows Guests (Windows server 03 &amp;amp; 08).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I run this script on all Cluster nodes prior to running any backup job:&lt;/P&gt;&lt;P&gt;net stop SnapMgrServiceHost&lt;BR /&gt;net stop SDMgmtSvc&lt;BR /&gt;net stop SWSvc&lt;/P&gt;&lt;P&gt;net start SWSvc&lt;BR /&gt;net start SDMgmtSvc&lt;BR /&gt;net start SnapMgrServiceHost&lt;/P&gt;&lt;P&gt;exit&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have also noticed if I live migrate a guest to another node within the cluster backups fail. I run the above script and the backups work.&lt;/P&gt;&lt;P&gt;This also happens if you reboot a cluster node and do not restart the Snap services.&lt;/P&gt;&lt;P&gt;Any ideas will be much appreciated, or is there a newer version of SMHV due for relaese shortly?&lt;/P&gt;&lt;P&gt;We have to babysit this cluster just to ensure it backs up every night!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:58:09 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/SMHV-Always-having-to-restart-Snap-services-to-get-a-sucessful-backup/m-p/512#M8</guid>
      <dc:creator>mtrorydavies</dc:creator>
      <dc:date>2025-06-05T06:58:09Z</dc:date>
    </item>
    <item>
      <title>Re: SMHV-Always having to restart Snap services to get a sucessful backup</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/SMHV-Always-having-to-restart-Snap-services-to-get-a-sucessful-backup/m-p/517#M9</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What's the actual error you are getting for the backup, if you take backup with out restarting SDW services?.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am thinking this issue is happening because of storage foot print for the VM is missing for some reasons when SMHV calls&lt;/P&gt;&lt;P&gt;SDW for VM enumeration just before backup. When you restart the SDW service, SDW is reporting the correct storage foot print.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are these VMs running on CSV?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Vineeth&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Mar 2011 00:56:20 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/SMHV-Always-having-to-restart-Snap-services-to-get-a-sucessful-backup/m-p/517#M9</guid>
      <dc:creator>vkarinta</dc:creator>
      <dc:date>2011-03-22T00:56:20Z</dc:date>
    </item>
    <item>
      <title>Re: SMHV-Always having to restart Snap services to get a sucessful backup</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/SMHV-Always-having-to-restart-Snap-services-to-get-a-sucessful-backup/m-p/521#M10</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your reply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Configuration is a 4 node Hyper V Cluster with 5 x CSV's&lt;/P&gt;&lt;P&gt;We are only backing up the 4 CSV's as the 5th one is a Sandpit for testing purposes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have one job that backs up all VM guests, sometimes it is 100% sucessful, sometimes it failes to backup the contents of one of the CSV's.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am currently checking if it is one CSV in particular that mostly fails and I will get back to you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Im also checking the release notes on 2008 R2 SP1 if there are any fixes for VSS and CSV's.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ill post my findings later in the day.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Mar 2011 02:32:13 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/SMHV-Always-having-to-restart-Snap-services-to-get-a-sucessful-backup/m-p/521#M10</guid>
      <dc:creator>mtrorydavies</dc:creator>
      <dc:date>2011-03-22T02:32:13Z</dc:date>
    </item>
    <item>
      <title>Re: SMHV-Always having to restart Snap services to get a sucessful backup</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/SMHV-Always-having-to-restart-Snap-services-to-get-a-sucessful-backup/m-p/526#M11</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Further information:&lt;/P&gt;&lt;P&gt;From the netapp backup log:&lt;/P&gt;&lt;P&gt;[3/22/2011 11:07:47 AM, (5)] Error: Vss Requestor - Backup Components failed.The shadow copy provider had an unexpected error while trying to process the specified operation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From the windows event log:&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Data ONTAP VSS hardware provider's AbortSnapshot method is called [SnapshotSetId={e4015ab1-f679-4654-9622-2e065a84625f}]. VSS has failed the current shadow copy session because the previous errors are not continuable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;________ &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Data ONTAP VSS hardware provider failed in CommitSnapshots method [SnapshotSetId={e4015ab1-f679-4654-9622-2e065a84625f}]. SnapDrive failed to create snapshot.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Please check SnapDrive event logs.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The data is the error code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;__________&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {ddd3d232-a96f-4ac5-8f7b-250fd91fd102}. Routine details CommitSnapshots [hr = 0xc00404d1].&lt;/P&gt;&lt;P&gt;Operation:&lt;/P&gt;&lt;P&gt;Executing Asynchronous Operation&lt;/P&gt;&lt;P&gt;Context:&lt;/P&gt;&lt;P&gt;Current State: DoSnapshotSet&lt;/P&gt;&lt;P&gt;---------------------&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Failed to create a consistent Snapshot copy({e4015ab1-f679-4654-9622-2e065a84625f}) of the LUN(s) [\\?\Volume{204d8e86-7802-4def-80d5-3d34ebcd7456}\ \\?\Volume{775e3b08-6918-4dde-b9c7-9f24c6f54038}\ \\?\Volume{b6fc60f8-1d23-4bf4-85ef-3bbd3f2670e8}\ ].&lt;/P&gt;&lt;P&gt;Error code : Unable to create a Snapshot copy. Please check the application event log for more details.&lt;/P&gt;&lt;P&gt;----------------------&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Unable to create a Snapshot copy.&lt;/P&gt;&lt;P&gt;Error message : An operation to create Snapshot copy '{e4015ab1-f679-4654-9622-2e065a84625f}' across multiple volumes failed on the storage system 'DC-FAS03'.&lt;/P&gt;&lt;P&gt;Error code: 135. Error description: No more snapshots available Error volume: CSV_2008_PRODVM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Mar 2011 03:52:34 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/SMHV-Always-having-to-restart-Snap-services-to-get-a-sucessful-backup/m-p/526#M11</guid>
      <dc:creator>mtrorydavies</dc:creator>
      <dc:date>2011-03-22T03:52:34Z</dc:date>
    </item>
    <item>
      <title>Re: SMHV-Always having to restart Snap services to get a sucessful backup</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/SMHV-Always-having-to-restart-Snap-services-to-get-a-sucessful-backup/m-p/531#M12</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Looks like SnapDrive is not able to create snapshot copy on one of the volumes because it has already reached the maximum of 255 snapshots:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;No more snapshots available Error volume: CSV_2008_PRODVM. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Storage system is 'DC-FAS03'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may want to delete some older backups to free up snapshots on this volume and then retry the backup.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anagha&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Mar 2011 05:43:13 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/SMHV-Always-having-to-restart-Snap-services-to-get-a-sucessful-backup/m-p/531#M12</guid>
      <dc:creator>barve</dc:creator>
      <dc:date>2011-03-22T05:43:13Z</dc:date>
    </item>
    <item>
      <title>Re: SMHV-Always having to restart Snap services to get a sucessful backup</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/SMHV-Always-having-to-restart-Snap-services-to-get-a-sucessful-backup/m-p/536#M13</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also please check your Hyper-V servers for the following hotfixes recommended for Windows 2008 R2.&lt;/P&gt;&lt;P&gt;You can apply these hotfixes if you are facing any of the issues mentioned in the KB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;OL start="1"&gt;&lt;LI&gt;KB975921&lt;BR /&gt;&lt;/LI&gt;&lt;LI&gt;KB974909&lt;BR /&gt;&lt;/LI&gt;&lt;LI&gt;KB975354 V2&lt;BR /&gt;&lt;/LI&gt;&lt;LI&gt;KB979743 V2&lt;BR /&gt;&lt;/LI&gt;&lt;LI&gt;KB974909 V2&lt;BR /&gt;&lt;/LI&gt;&lt;LI&gt;KB2406705 V2&lt;BR /&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Vineeth&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Mar 2011 06:19:23 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/SMHV-Always-having-to-restart-Snap-services-to-get-a-sucessful-backup/m-p/536#M13</guid>
      <dc:creator>vkarinta</dc:creator>
      <dc:date>2011-03-22T06:19:23Z</dc:date>
    </item>
  </channel>
</rss>

