VSS backup process stops responding when you try to perform a Volume Shadow Copy Service (VSS) backup for Exchange Server 2010 databases


Consider the following scenario:
  • You have a Microsoft Exchange Server 2010 server that is installed with multiple databases.
  • These databases are mounted.
  • You have circular logging for these databases enabled.
  • You disable circular logging for these databases.
  • You try to perform an incremental Volume Shadow Copy Service (VSS) backup for these databases based on a full VSS backup.
In this scenario, some logs are overwritten by new logs caused by enabling and disabling circular logging. Then, when you try to perform the incremental VSS backup, the incremental VSS backup process and the corresponding database crash. At the same time, you find the following two Event errors:


The issue described in the "Symptoms" section occurs because of an internal deadlock in the Exchange Database Engine (ESE).


To resolve this problem, install the following update rollup:
976573 Description of Update Rollup 1 for Exchange Server 2010

Note This update cannot prevent the incremental VSS backup from failing, as some required logs are still missing caused by switching circular logging on and off before you try to perform the incremental VSS backup.

More Information

For more information about Exchange Server 2010 and VSS Backup, visit the following Microsoft Web site:


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Article ID: 977561 - Last Review: Feb 16, 2017 - Revision: 3