Tag Archives: server

Backup succeeded but some components backed up were inconsistent

One of my clients had issues running a full VSS backup of his Exchange server.  Windows Server Backup reported “Backup succeeded but some components backed up were inconsistent”. This is on a Windows 2012 R2 server with Exchange 2013 SP1 CU9.

Backup inconsistent

The event log showed several errors and warnings related to the failed backup:

Event ID 2227, source MSMQ: Backup failed during event OnPrepareSnapshot. Error 0x80070005: Access is denied.

MSMQ 2227

Event ID 16389, source SPP: Writer MSMQ Writer (MSMQ) experienced retryable error during shadow copy creation. Retrying…  More info: .

On the Details tab, some extra info can be found: “The writer’s timeout expired between the Freeze and Thaw events. (0x800423F2)”

SPP 16389

Event ID 8229, source VSS: A VSS writer has rejected an event with error 0x00000000, The operation completed successfully.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.

Operation: PrepareForSnapshot Event

Execution Context: Writer
Writer Class Id: {7e47b561-971a-46e6-96b9-696eeaa53b2a}
Writer Name: MSMQ Writer (MSMQ)
Writer Instance Name: MSMQ Writer (MSMQ)
Writer Instance ID: {123a679c-0d61-4f0c-bad4-74e39d6ecca0}
Command Line: C:\Windows\system32\mqsvc.exe
Process ID: 1356

VSS 8229

Troubleshooting steps that didn’t help:

  • When running vssadmin list writers, it shows you a list of all available VSS writers. Right after the failed backup, the MSMQ Writer will be in a failed state.
  • Reregistering the VSS writers, as explained on several sites, did not help, and neither did rebooting the server nor restarting the Message Queuing service.
  • Manually extending the VSS timeout, by increasing the value of HKLM\Software\Microsoft\Windows NT\CurrentVersion\SPP\CreateTimeout, had no effect.

The solution: in the log file of the failed backup, it also showed error 0x800423F2 (which means timed out) and a reference to several files in the C:\Windows\System32\msmq folder. MSMQ (the Message Queuing service) is one of the prerequisites of Exchange 2013 so it cannot be removed, and it’s also part of a full Exchange backup so it cannot be skipped.

Turns out that the msmq folder contained a subfolder called config. When browsing to that folder using a domain admin account, I got the message that administrative permissions were needed. Huh?

I took ownership of the folder and added full control for admins. From then on, the backup worked again. And the config subfolder? It was gone after the first successful backup. Go figure…