Search the VMware Knowledge Base (KB)
View by Article ID
Enabling and disabling Windows 2008 and later application-consistent quiescing on ESXi/ESX (1028881)
- You may receive error code 5 and see errors similar to:
'VssSyncStart' operation failed: Operation aborted (0x80004004) warning"
2012-08-23T16:33:20.647Z [FFA18B90 verbose 'PropertyProvider' opID=CA0E7426-00005219-58] RecordOp ASSIGN: info.error, task-142530
2012-08-23T16:33:20.648Z [FFA18B90 info 'Default' opID=CA0E7426-00005219-58] [VpxLRO] -- FINISH task-142530 -- -- vpxapi.VpxaService.createSnapshot -- 5229b79e-ce92-3d72-81e9-c22f5ec4923d
2012-08-23T16:33:20.648Z [FFA18B90 info 'Default' opID=CA0E7426-00005219-58] [VpxLRO] -- ERROR task-142530 -- -- vpxapi.VpxaService.createSnapshot: vim.fault.ApplicationQuiesceFault:
- You may receive error code 3 when the guest operating system reports an error during quiescing, and in the
vmware.log: file, you see entries similar to:
Error when notifying the sync provider
Quiesce operation aborted
[msg.snapshot.quiesce.vmerr] The guest OS has reported an error during quiescing
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
After quiescing the virtual machine, the hardware snapshot provider creates two
.REDOlogs per virtual machine disk, one for the live (ongoing or upcoming) virtual machine writes, and another for the VSS and Writers in the guest operating system to modify the disks after the snapshot operation is complete.
The snapshot configuration information of the virtual machine reports this second
.REDOlog as part of the snapshot. This
.REDOlog represents the quiesced state of all the applications in the guest.
.REDOlog must be opened using VDDK 1.2 to back it up. VDDK 1.1 fails to open this second
.REDOlog for backup.
Application-consistent quiescing of Windows 2008 and later virtual machines is available when those virtual machines are created in vSphere 4.1, 5.x and 6.0.x. Virtual machines created in vSphere 4.0 can be updated to enable application-consistent quiescing by modifying a virtual machine’s
To enable Windows 2008 and later virtual machine application-consistent quiescing:
- Open the VMware vSphere Client, and log in to vCenter Server.
- Select Virtual Machines and Templates and click the Virtual Machines tab.
- Locate the Windows 2008 or later virtual machine for which you are enabling the disk UUID attribute, and power off the virtual machine.
- After power-off, right-click the virtual machine, and choose Edit Settings.
- Click the Options tab, and select the General entry in the settings column (under the Advanced entry).
- Click Configuration Parameters.
- Click Add Row.
- In the Name column, type
- In the Value column, type
- Click OK and click Save.
- Power on the virtual machine.
TRUE. Use the remaining steps afterward:
You can disable application quiescing without virtual machine downtime by making a configuration change within VMware tools:
- Open a text editor with administrator privileges. Right-click on the text editor and select Run as Administrator
- Open C:\ProgramData\VMware\VMware Tools\Tools.conf file using a text editor. If the file does not exist, create it.
- Add these lines to the file:
vss.disableAppQuiescing = true
- Save and close the Tools.conf file.
- Restart the VMware Tools Service for the changes to take effect:
Restarting of the VMware Tools Service does not reliably stop the vmtoolsd.exe process. Therefore, follow these steps to restart:
- Click Start > Run, type services.msc, and click OK.
- Right-click the VMware Tools Service and click Stop.
- Open Task Manager by doingPress ctrl-shift-esc to open the Task Manager.
- In the Processes tab, search for vmtoolsd.exe file still exists
- Right-click on vmtoolsd.exe and stop the process.
- Return to the services window. Right-click the VMware Tools Service and click Start. Ensure that the vmtoolsd.exe service has restarted in the Processes tab.
Note: In some versions of VMware Tools, this service is named as VMware Tools Service(VMTools).
- For related troubleshooting information, see Cannot take a quiesced snapshot of Windows 2008 R2 virtual machine (1031298).
- For more information about VSS, see the Microsoft TechNet article How Volume Shadow Copy Service Works.
- For more information about the Security Support Provider Interface, see the Microsoft TechNet article The Security Support Provider Interface (SSPI).
- For more information regarding quiecing virtual machines in Windows 2012, see the Windows Backup Implementations section in the vSphere API/SDK Documentation Guide.
Note: The preceding link was correct as of June 24, 2016. If you find the link is broken, provide a feedback and a VMware employee will update the link.
- Creating a quiesced snapshot of a Windows 2008 virtual machine fails with the error: Snapshot 0 failed: Failed to quiesce the virtual machine (2015181)
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.