Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Virtual machines hang during backup

Summary: This article provides information about virtual machines locking up during backups

This article may have been automatically translated. If you have any feedback regarding its quality, please let us know using the form at the bottom of this page.

Article Content


Symptoms

Virtual machines lockup or freeze when performing a backup of the Hyper-V host and virtual machines using Windows Server Backup. The issue can also occur using third-party backup programs. Event ID 27 volsnap and Event ID 3 Microsoft-Windows-FilterManager appear in the System event log. Follow the steps in the solution to resolve this issue.

Cause

.

Resolution

1. Create the following registry key. 

Note: Backup the registry keys prior to adding or deleting entries. For instructions on backing up a registry key click here. 

     a. Press Windows Logo+R, type regedit and press Enter.

         SLN291054_en_US__11396539224036.run regedit


     b. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization.

         SLN291054_en_US__21396539375179.Virt reg 1

     c. Right-click on Virtualization, click New and click DWORD (32-bit) Value.

     d. Type VssRevertTimeout for the Value name

     e. Set the Value data to 360 (decimal).

         SLN291054_en_US__31396539480041.Virt reg 2

2. Create the following registry key and reboot the server.

     a. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SPP.

         SLN291054_en_US__41396539499385.Virt reg 3

     b. Right-click on SPP, click New and click DWORD (32-bit) Value.

     c. Type CreateTimeout for the Value name

     d. Set the Value data to 12000000 (decimal).

         SLN291054_en_US__51396539522151.Virt reg 4


 

Additional Information:

This information applies to Windows Server 2008 R2, Windows Server 2012 and Windows Server 2012 R2.

Hotfix 2182466 may need to be applied to a server running Windows Server 2008 R2.

The hotfix can be found here.

Event ID 27 volsnap is logged in the System event log.

Log Name: System
Source: volsnap
Date: 4/03/2014 9:00:12 AM
Event ID: 27
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: computername.domainname.local
Description:
The shadow copies of volume \\?\Volume{fb409183-e795-11e2-93f8-001018f512c7} were aborted during detection because a critical control file could not be opened.

Event ID 3 Microsoft-Windows-FilterManager is logged in the System event log.

Log Name: System
Source: Microsoft-Windows-FilterManager 
Date: 4/03/2014 9:00:12 AM
Event ID: 3
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: computername.domainname.local
Description:
Filter Manager failed to attach to volume '\Device\HarddiskVolume236'. This volume will be unavailable for filtering until a reboot. The final status was 0xC03A001C.

  

 

Article Properties


Affected Product

Servers, Microsoft Windows 2008 Server R2, Microsoft Windows 2012 Server, Microsoft Windows 2012 Server R2

Last Published Date

03 Nov 2023

Version

6

Article Type

Solution