Exchange writer missing out

Question

The Microsoft Exchange Writer has completely disappeared from the vssadmin list writers output. This is preventing us from performing application-aware backups, leaving us with "crash-consistent" snapshots only, which is a major risk for our database integrity.

How can I get it back

Answer 1

Hi, Brooklynn Allen

In Exchange Server (2016/2019/SE), the Exchange VSS writer functionality is hosted in the Microsoft Exchange Replication service, and it requires the Microsoft Exchange Information Store service to be running for the writer to be advertised to VSS requesters (backup software).

That said, if vssadmin list writers shows no writers at all, that points to a broader VSS/COM+ registration problem on Windows (not just Exchange), which can prevent VSS writers from being enumerated entirely.

So, there are two scenarios in this situation, you can check to see if it can help you:

1. If vssadmin list writers returns no writers at all, fix the Windows VSS writer enumeration issue by correcting the Event System registry TypeLib path to %systemroot%\system32\EVENTCLS.DLL and restarting the COM+ Event System and Volume Shadow Copy services, then re-run vssadmin list writers to confirm writers are listed again.
2. If other writers appear but only “Microsoft Exchange Writer” is missing, verify that both the Microsoft Exchange Replication service (writer host) and the Microsoft Exchange Information Store service (required for writer advertisement) are running, then restart the services as needed and re-check vssadmin list writers for the writer to return.

Link references:

https://learn.microsoft.com/en-us/troubleshoot/windows-server/backup-and-storage/no-vss-writers-listed-run-vssadmin-list-writers

https://learn.microsoft.com/en-us/exchange/high-availability/disaster-recovery/disaster-recovery

Hope my answer will help you.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".   

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.  

Answer 2

On Exchange 2013 and later, the Microsoft Exchange Writer is hosted in the Microsoft Exchange Replication service and depends on the Microsoft Exchange Information Store service. If the writer is missing from vssadmin list writers, restore it by ensuring the supported, Exchange-aware VSS stack is in place and both required services are running.

Use these steps:

1. Verify Exchange version and supported backup method
   • Exchange Server supports only Exchange‑aware, VSS‑based backups. The Microsoft Exchange Writer is the VSS writer used by Exchange‑aware applications (Windows Server Backup with the Exchange plug‑in, System Center Data Protection Manager, or third‑party Exchange‑aware VSS backup tools).
   • If using a non‑Exchange‑aware backup tool or a generic VSS snapshot mechanism that does not load the Exchange writer, only crash‑consistent backups will be available.
2. Confirm required Exchange services are running
   • Ensure Microsoft Exchange Replication service is running. In Exchange 2013 and later, the VSS writer functionality resides in this service.
   • Ensure Microsoft Exchange Information Store service is also running. Even though the writer runs in the Replication service, the Information Store service must be running for the Microsoft Exchange Writer to be advertised to VSS. If either service is stopped or disabled, the writer will not appear in vssadmin list writers.
   • After starting both services, re‑run vssadmin list writers and confirm that Microsoft Exchange Writer is listed.
3. Use an Exchange‑aware VSS backup application
   • Make sure the backup application is an Exchange‑aware VSS requester that supports the Microsoft Exchange Writer. Exchange 2013 includes a VSS writer for Windows Server Backup, but that built‑in integration only backs up whole volumes, not individual databases.
   • If more flexibility is required (for example, database‑level backups), use a third‑party Exchange‑aware VSS‑based backup application or implement a custom VSS requester that correctly interacts with the Microsoft Exchange Writer.
4. Avoid backups without writer participation
   • If backups are taken without the Microsoft Exchange Writer participating, VSS will still create shadow copies, but the data will only be in a crash‑consistent state. This is not recommended for Exchange databases because it can lead to instability or integrity issues.
   • Restoring application‑consistent backups requires that the Microsoft Exchange Writer be present and used by the backup application.

If, after confirming that both the Microsoft Exchange Replication and Information Store services are running, the Microsoft Exchange Writer still does not appear in vssadmin list writers, use a supported Exchange‑aware backup solution and standard Exchange recovery methods (for example, server recovery with /m:RecoverServer if a server rebuild is required) to return the environment to a supported state before relying on VSS backups again.

---

References:

• Backup and restore for Exchange
• Backup, restore, and disaster recovery in Exchange Server
• Backup, restore, and disaster recovery
• Build backup and restore applications for Exchange 2013
• Backups without Writer Participation