The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Cannot take a quiesced snapshot of Windows 2008 R2 virtual machine (1031298)
- The snapshot operation fails to complete
- You are unable to create a quiesced snapshot of the virtual machine.
- You are unable to back up the virtual machine.
- Cloning a Windows 2008 R2 virtual machine fails
- The Application section of the Event Viewer in the virtual machine Windows guest operating system may report a VSS error similar to:
Volume Shadow Copy Service error: Unexpected error calling routine IOCTL_DISK_SET_SNAPSHOT_INFO(\\.\PHYSICALDRIVE1) fails with winerror 1168. hr = 0x80070490, Element not found.
- Performing any process that creates a quiesced snapshot fails
- You see the error:
Can not create a quiesced snapshot because the create snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine.
- Backup applications, such as VMware Data Recovery, fails with the error:
Failed to create snapshot for <vmname>, error -3960 (cannot quiesce virtual machine)
This issue occurs due to a known issue with VSS application snapshots and ESXi/ESX 4.1 and later.
To work around this issue, disable VSS application-based snapshots to revert to file system quiesced snapshots.
- Some issues related to Windows 2008 R2 VSS application-based snapshot backups in vSphere Data Protection (VDP) are resolved in VDP 5.1.10. For more information, see the vSphere Data Protection 5.1.10 Release Notes.
- For more information, see Troubleshooting Volume Shadow Copy (VSS) quiesce related issues (1007696) and Disabling specific VSS writers with VMware Tools (1031200).
Disable VSS application quiescing using the vSphere Client:
- Power off the virtual machine.
- Log into vCenter Server or the ESXi/ESX host through the vSphere Client.
- Right-click the virtual machine and click Edit settings.
- Click the Options tab.
- Go to Advanced > General > Configuration Parameters.
- Add or modify the row
disk.EnableUUIDwith the value
- Click OK to save.
- Click OK to exit.
- Reboot the virtual machine for changes to take in effect.
Note: If this change is done via the command line, use
vim-cmdcommand to reload the vmx is enough to see the changes. For more information, see Reloading a vmx file without removing the Virtual machine from inventory (1026043).
- Alternatively, un-register the virtual machine from the vCenter Server inventory. To un-register, right-click the virtual machine and click on Remove from Inventory.
- Re-register the virtual machine back to the inventory. For more information, see Registering or adding a virtual machine to the inventory on vCenter Server or on an ESX/ESXi host (1006160).
disk.EnableUUIDparameter for VMware Data Protection (VDP), see the Resolution section in Backing up a Windows Server 2008 R2 virtual machine using VMware Data Protection 5.1 fails with the error: Execution Error: E10055:Failed to attach disk. (2035736).
Disable VSS application quiescing using VMware Tools:
- Open the
C:\ProgramData\VMware\VMware Tools\Tools.conffile in a text editor, such as Notepad. If the file does not exist, create it.
- Add these lines to the file:
vss.disableAppQuiescing = true
- Save the file.
- Exit the editor.
- Restart the VMware Tools Service for the changes to take effect. Click Start > Run, type
services.msc, and click OK.
- Right-click the VMware Tools Service and click Restart.
- For general treatment of quiesced snapshot issues, see A virtual machine can freeze under load when you take quiesced snapshots or use custom quiescing scripts (5962168).
- For information on quiesced snapshots in VMware Consolidated Backup (VCB), see the Virtual Machine Backup Guide.
- For information on quiesced snapshots in VMware Data Recovery (VDR), see the VMware Data Recovery Administration Guide.
- There is a related known issue with vCenter Server installed on a Windows 2008 or 2008 R2 virtual machine with snapshots and the ADAM or NTDS instance which are used by vCenter Server.
This issue is resolved in ESXi/ESX 4.1 Update 1. For more information, see the Backup section of the VMware ESX 4.1 Update 1 Release Notes.
- In some cases, Windows 2008 R2 patches may update the Microsoft VSS drivers. If this occurs, reinstall VMware Tools so that the VMware VSS drivers can be used again.
Note: To be alerted when this article is updated, click Subscribe to Document in the Actions box.
For translated versions of this article, see:
This Article Replaces
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.